A vmotion process died at 29 % - now I have one VM directory at location A and one at location B.
I can not start any of them as the vmdks are locked by owner 000...
How can I kill the process that locks the vmdks ?
The host that was running the VM still has a world-id for the VM but if I try to kill it - it says the process does not exist
Delete .lck files on VM and power ON.
So this was a vMotion with migrating host and storage!?
Restarting the Management Agents on the hosts should kill any processes which lock the files.
André
can you provide the hostd logs of source and destination ESXi host after recreating the issue
I had to do it the hard way ...
I had to kill the management services but that was not enough.So we had to move all other VMs from that host elsewhere and reset the ESXi.
A gentle reboot was impossible