We have encountered an issue where a virtual machine was actually bouncing to every single ESX host within our cluster. The virtual machine would actually show its state as powered off while it was bouncing until it actually reached the host that is was power up on then its state would change to powered on. via vmware-cmd we where able to power the guest down although it had to be run more than once "like there was multiple instances running". Has anyone ever seen this issue? What could cause this? Please let me know if there is anything else that I can provide?
root@mdsvavh03 root--# vmware-cmd /vmfs/volumes/452bed0c-37c715a7-f4b0-00132164cb33/vmdsxawo05/vmdsxawo05.vmx getstate
getstate() = on
root@mdsvavh03 root# vmware-cmd /vmfs/volumes/452bed0c-37c715a7-f4b0-00132164cb33/vmdsxawo05/vmdsxawo05.vmx stop
stop() = 1
root@mdsvavh03 root# vmware-cmd /vmfs/volumes/452bed0c-37c715a7-f4b0-00132164cb33/vmdsxawo05/vmdsxawo05.vmx getstate
getstate() = on
root@mdsvavh03 root# vmware-cmd /vmfs/volumes/452bed0c-37c715a7-f4b0-00132164cb33/vmdsxawo05/vmdsxawo05.vmx start
VMControl error -999: Unknown error: SoapError: ServerFaultCode(0) : (The attempted operation cannot be performed in the current state (Powered On).)
root@mdsvavh03 root# vmware-cmd /vmfs/volumes/452bed0c-37c715a7-f4b0-00132164cb33/vmdsxawo05/vmdsxawo05.vmx stop
stop() = 1
root@mdsvavh03 root# vmware-cmd /vmfs/volumes/452bed0c-37c715a7-f4b0-00132164cb33/vmdsxawo05/vmdsxawo05.vmx stop
I heard of people having issues after upgrading from VC 2.0 to 2.5 with VMotion set to full automated where guest started constantly migrating between hosts.
We are at VC 2.0.2 up2
It's like there was a lock on a file from the VMs original destination not allowing the server to migrate, although a migration was not issued manually.
DRS set to agresive will shunt your vms around.. is it one Vm or all of them that are doing this?
Drop your DRS setting from Aggressive (one Star) to Moderately aggressive (two Stars) or Mid-point (Three Stars).
Tom Howarth
VMware Communities User Moderator
All of our DRS settings are set to manual, therefore elliminating the thought of DRS causing the bouncing. I have sent logs to VMware and will be updating this post ASAP.