I have a VM which won't power off or be killed by the normal methods. I have tried:
The Power Off GUI button which times out
vm-support -X <vmid> - which hangs at 'Snapping0: 300 seconds left' (and is still hanging)
vmware-cmd <cfg> stop hard - which does nothing and I end up killing that process
ps -auxwww | grep <vm name>, followed by kill -9 PID, which killed the process, but the VM is still stuck
/usr/lib/vmware/bin/vmkload_app –k 9 groupid - failed to forward signal 9 to cartel 1202: 0xbad0061
Any other ideas?
ps -auxwww | grep <vm name>, followed by kill -9 PID, which killed the process, but the VM is still stuck
What do you mean exactly with the VM is still stuck?
Are you sure you killed the right process? When the process is killed the VM is gone afaik.
-Arnim van Lieshout
-
Blogging: http://www.van-lieshout.com
If you find this information useful, please award points for "correct" or "helpful".
one other thought.
I've seen VM processes running on 2 different ESX hosts after a failed vmotion in the past.
Perhaps you have the same problem. Check all your hosts in the cluster for this VM's process.
And kill the process on all hosts where you find it.
-Arnim van Lieshout
-
Blogging: http://www.van-lieshout.com
If you find this information useful, please award points for "correct" or "helpful".
'Still stuck', i.e. powered on, trying to boot, not able to power off.
Yes, I am sure I killed the right process, I checked the process before and after for the correct VM and it was still in the stuck state.
In the last five minutes we got a warning for the host the VM lives on that it was not responding in VC, had to kill vmware-hosd and restart mgmt-vmware to get it back. Around the same time, the vm-support -X suddenly completed and the VM was powered off. Its now in a workable state, thanks for your help anyway.
Glad to hear it's working again.
Arnim
I had the same problem, I just restarted the mgmt-vmware service and the VM powered off instantly. It seems the VC locks the VM somehow
Regards,
Mike