karthikt2's Posts

Even we faced this issue on few Virtual Machines in our newly upgraded 6.5 vCenter & ESXi hosts. Called up VMware support and they suggested to find and reboot the host that holds the lock. but c... See more...
Even we faced this issue on few Virtual Machines in our newly upgraded 6.5 vCenter & ESXi hosts. Called up VMware support and they suggested to find and reboot the host that holds the lock. but considering the criticality of the environment, it is not feasible to reboot the host. Hence I performed some steps to find a alternate solution to release the VM lock without rebooting hosts. Perform following steps:- Note down the VM datastore path SSH the host on which the VM is currently sitting and find the host which has created lock SSH to the host on which is locked, run below command to kill the hung task esxcli vm process list (find the VM and note its WorldNumber) esxcli vm process kill -t [soft,hard,force] -w WorldNumber At this stage go to vSphere webclient and note that VM goes into Orphaned stage. Right click and remove VM from inventory SSH to the host on which VM file lock was created Register the VM using cli - vim-cmd solo/registervm /vmfs/volumes/datastore_name/VM_directory/VM_name.vmx – (notedown the vmid) Power on the VM using cli - vim-cmd vmsvc/power.on <vmid> Login to vSphere client and search for the VM à go to Summary à Answer the Virtual Machine Message – ‘I Copied it’ VM gets powered ON let me know if this solution helps.