Symptoms
- ESX is not behaving correctly.
- ESX could appear disconnected or not responding in VirtualCenter
- VMotions to/from the ESX host may fail
- The VMware High Availability agent generates an error
- Cannot configure VMware HA
Purpose
Resolution
Check the hostd (/var/log/vmware/hostd.log ) logfile for entries similar to:
[2008-10-29 10:59:10.297 'TaskManager' 22391728 info] Task Created : haTask-pool43-vim.ResourcePool.updateChildResourceConfiguration-30596
[2008-10-29 10:59:10.297 'vm:/vmfs/volumes/49634845-7762a9c4-6528-00625741238/myVM/myVM.vmx' 22391728 info] State Transition (VM_STATE_ON -> VM_STATE_RECONFIGURING)
[2008-10-29 10:59:10.601 'vm:/vmfs/volumes/49634845-7762a9c4-6528-00625741238/myVM/myVM.vmx' 22391728 info] State Transition (VM_STATE_RECONFIGURING -> VM_STATE_ON)
[2008-10-29 10:59:10.665 'TaskManager' 22391728 info] Task Completed : haTask-pool43-vim.ResourcePool.updateChildResourceConfiguration-30596
When you see many repetitions of updateChildResourceConfiguration , this indicates the resource pools are out of sync between VirtualCenter and the ESX host.
The problem is corrected in VirtualCenter 2.5 Update 3 and ESX 3.5 Update 3. The release notes can be found here.
To workaround this problem:
- Disconnect the ESX host from VirtualCenter. Right-click the managed host icon in the inventory panel and chooseDisconnect.
- Log in as root to the ESX host with an SSH Client.
- Run these commands:
# service vmware-vpxa stop
# service mgmt-vmware stop
# rm -f /etc/vmware/hostd/pools.xml
# service mgmt-vmware start
wait ~30 sec
# service vmware-vpxa start - Verify that the VirtualCenter agents are running
- Reconnect the ESX host to VirtualCenter. Right-click the managed host icon in the inventory panel and choose Connect.
Based on VMware KB 1007469
