Twitter Updates
| ESX 3.5 Update 3 Problem with HA |
|
|
|
| Written by Rynardt Spies | |||
| Tuesday, 09 December 2008 01:00 | |||
|
There is a problem with the with HA in VMware ESX 3.5 Update 3. Virtual Machines may reboot unexpectedly when migrated with VMotion or after a Power On operation. This is only when the Virtual Machine is running on an ESX 3.5 Update 3 Host and the ESX Host has VMware HA enabled with "Virtual Machine Monitoring" option active.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. 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.
Option 2: Set hostd hearbeat delay to 0 1. Disconnect the host from 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.
6. Reconnect the host in VC ( Right click on host in VI Client and select "Connect" )
|
Popular
- Building an iSCSI Openfiler SAN on a USB Stick
- Simple VMware vSphere 4 & 5 License Calculator
- Replace SSL Certificates: Replace vCenter Server SSL Certificates
- Patching ESX 3.5 Using esxupdate
- My experiences with Installing vCenter on Windows Server 2008 R2
- ESX 3i: Host in HA Cluster must have userworld swap enabled
- ESX 3.5 on HP Proliant ML115 G5
- Replacing vSphere SSL Certificates
- VMware ESXi 3.5 on HP Proliant ML110 G5
- Clearing a GUID Partition Table (GPT) in Linux
Support VirtualVCP!
Information and Resources on this site are 100% free, however it costs money to run this site. Please help support this site by giving a donation.









