This Just dropped into my Mail Box. So I thought I would post it.
Dear ESX 3.5 customer,
Our records indicate you recently downloaded VMware® ESX Version 3.5 U3 from our product download site. This email is to alert you that an issue with that product version could adversely effect your environment. This email provides steps you can take to correct any issues that you may currently have or prevent you from encountering the issue.
A Virtual Machine may unexpectedly reboot when using VMware HA with Virtual Machine Monitoring on ESX 3.5 Update 3
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 the VMware HA feature with Virtual Machine Monitoring is active.
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 the “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, the 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.
Note: Before you begin please refer to KB 1003490 for important information on restarting the mgmt-vmware service.
To work around this problem:
Option 1: Disable Virtual Machine Monitoring
1. 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).
2. In the Cluster Settings dialog box, select VMware HA in the left column.
3. Un-Check the Enable virtual machine monitoring check box.
4. Click OK.
1. Disconnect the host form VC (Right click on host in VI Client and select “Disconnect” )
2. Login as root to the ESX Server with SSH.
3. Using a text editor such as nano or vi, edit the file /etc/vmware/hostd/config.xml
4. Set the “heartbeatDelayInSecs” tag under “vmsvc” to 0 seconds as shown here:
5. Restart the management agents for this change to take effect. See Restarting the Management agents on an ESX Server (KB 1003490).
6. Reconnect the host in VC ( Right click on host in VI Client and select “Connect” )
Please consult KB 1007899 for further details on managing packages already registered.
Please consult your local support center if you require further information or assistance. We apologize in advance for any inconvenience this issue may cause you. Your satisfaction is our number one goal
I thought it important enough to post.