VIrtual Machines Issues1) Unable to power on an ESX/ESXi virtual
machine that was powered on previously.
a) check that there is sufficient free disk space. For more
information,Use this general formula to calculate the disk space
required:
(Size of virtual machine's hard disk(s)) + (size of RAM for
virtual machine) + (100MB for log files per virtual machine) is the
minimum space needed for each virtual machine.
b) Check that the virtual machine files and directory are
accessible Determining the location of all your virtual machine
files
The image below shows how you can obtain the location of
the.vmdkfiles:
From this screen it is also possible to find the location of the
configuration file and the working directory of the virtual
machine. By selecting theOptionstab, a screen similar to the one
below is shown:
Verifying that you can access the location of the virtual
machine files
Log into the VMware ESX/ESXi host as the root user.Use
thelscommand to navigate to the relevant locations.For example:ls
/vmfs/volumes/46b2f3eb-ced4c7d8-c1d2-111122223333/vm1/If the files
associated with your virtual machine (vmdk, vmx, nvram) are listed
you are able to access the storage hosting your virtual machine c)
Check that there are sufficient permissions for you to power on the
virtual machine Permissions can be set in vCenter
Server/VirtualCenterto control Power On operations with virtual
machine.To check if there are sufficient permissions set invCenter
Server/VirtualCenter:1. Connect to thevCenter
Server/VirtualCenterusing vSphere Client/Virtual Infrastructure
Client.2. Log in as an user with administrator privileges.3. Select
the Datacenter and clickPermissions.4. Check if the user
accountused to log in has at least read-only rights at this
level.5. Click on the ESX/ESXi host where the virtual machine
residesand click thePermissionstab.6. Check if the user account
used to log in hasVirtual Machine userrights at that level.7. Check
to make sure that the user is not part of a group that has been
assigned a restrictive role. This could limit privileges in parts
of the inventory hierarchy.
d) Check that there are sufficient resources Not enough
resources to Power On the virtual machine.To verify the virtual
machine is configured with enough resources:1. Connect to the
ESX/ESXihost directly using VMware Infrastructure/vSphere Client.2.
Log inas a userwith administrator privileges.3. Right-click the
virtual machine from the Inventory panel and clickEdit settings.4.
ClicktheResourcestab.5. Check if the Memory and CPUreservations are
set correctly.6. ClickOKto save changes and try Powering On the
virtual machine.If the virtual machine is part of a Cluster and
Resource Pool configuration:1. Connect to the ESX/ESXi host
directly using VI/vSphere Client.2. Log inas userwith administrator
privileges.3. Right-click onthe Resource Pool where the virtual
machine isand clickEdit settings.4. Check if bothCPU Resources and
Memory Resources are set to the appropriate level to accommodate
all the virtual machines.2) POWER ON VIRTUAL MACHINE FAILS
VMFSHEAPSIZEThe error message was not telling me what the problem
is. A figure is attached below.
VMFS HEAPSIZEThe ESXi server in this environment is 5.0 with
Update 1, the default allowed active VMDK storage per ESXi is 8TB
with the default heap size 80MB. This means that if a single ESXi
server has virtual machines with more than 8TB of active VMDKs, the
ESXiwill refuse to power-on more virtual machines.
A) The solution is quite simple, vMotioned the virtual machine
to ESXiB which has the lowest VMDK size and it was happy.
