1 person found this helpful
The inability to power the VM back on is usually due to one of two things:
1) There's an active lock on the VM, particularly the vswp swapfile.
2) There's an active process on either the origin or destination ESX server (the two servers involved in the VMotion exchange) that's holding the .vmx and/or virtual machine open.
You can usually do a:
vmware-cmd /full/path/to/vmx/file.vmx getstate
vmware-cmd /full/path/to/vmx/file.vmx stop hard
to figure out what's happening.
I figured there was a lock on something which is why I couldn't power it on and that's fine. But, I couldn't kill the migration in progress even after stopping the vm, restarting the vc service and server, restarting the mgmt-vmware service on the esx servers, restarting the vmware-vpxa service, removing the server from vc ...
I only removed one of the servers maybe I should have tried removing them both?
Does anyone know what process handles the vmotion in progress?
A vMotion that gets stuck in the middle could be related to a SCSI Reservation Conflict. YOu will want to review your /var/log/vmkernel and /var/log/vmkwarning files for these types of issues. These can set locks on remote data stores that then need to be cleared up.