Virtual Machines may unexpectedly reboot after a VMotion migration to an ESX 3.5 Update 3 Host OR after a Power On operation on an ESX 3.5 Update 3 Host, when VMware HA feature with Virtual Machine Monitoring is active.
To stay up to date on this VMware KB, please visit their website; VMware KB 1007899
A virtual machine may reboot itself when the following conditions exist:
Virtual Machine is running on ESX 3.5 Update 3 Host, either by virtue of VMotion or a Power On operation, and
- Host has VMware HA enabled with “Virtual Machine Monitoring” option active.
Virtual Machine monitoring is dependent on VMware tools heartbeats to determine the state of the Virtual Machines.
With ESX Server 3.5 Update 3 after a VMotion or Power On operation, host agent running on the ESX server may delay sending the heartbeat state of the Virtual Machine to the Host. VMware HA detects this as a failure of the Virtual Machine and attempts to restart the Virtual Machine
To work around this problem:
Select the VMware HA cluster and choose Edit Settings from the right-click menu (note that this feature can also be enabled for a new cluster on the VMware HA page of the New Cluster wizard).
In the Cluster Settings dialog box, select VMware HA in the left column.
Un-Check the Enable virtual machine monitoring check box.
Disconnect the host from VC (Right click on host in VI Client and select “Disconnect” )
Login as root to the ESX Server with SSH.
Using a text editor such as nano or vi, edit the file /etc/vmware/hostd/config.xml
Set the “heartbeatDelayInSecs” tag under “vmsvc” to 0 seconds as shown here:
Restart the management agents for this change to take effect. See Restarting the Management agents on an ESX Server
Reconnect the host in VC ( Right click on host in VI Client and select “Connect” )