When converting old VMware virtual machines to a newer hypervisor, with the free VMware vCenter Converter Standalone client tool , the following error message may appear and thus block the operation: ” Unable to obtain the lock on virtual disks “or” Unable to get lock on virtual disks “according to VMware.
An error that already existed in 2009 when migrating VMware Server 2.0 virtual machines to ESX / ESXi 3.5 but can also happen with newer versions of the VMware hypervisor: VMware Infrastructure 3.5, VMware ESX / ESXi 4, VMware vSphere 5, 5.1, 5.5, 6.0 and 6.5 as of the end of 2017.
This problem may also affect local virtual machines running with VMware Workstation or Player. Whether for local to local, server to server, server to local or local to server conversion. Also, all guest operating systems can experience this “Unable to get the lock on virtual disks” since this is not a guest side error but host side , that is to say on the solution VMware virtualization.
Fortunately, this error is not serious and it is easy to find a solution for successful migration or virtual machine conversion.
Solution against Unable to obtain the lock on virtual disks during a VMware conversion
VMware support offers these tips and fixes:
- Shut down the VM before conversion
- Try the live conversion by Powered-on machine
- The VM was not shut down safely, restart and shut down properly
- Delete all .TMP files associated with the virtual disk
- Delete all .WRITELOCK files associated with the virtual disk
- Delete all .LCK folders associated with the virtual disk
In French, the following actions:
- Stop the VM before conversion (“cold” operation)
- Try to make a hot conversion by choosing “Powered on” at Source type
- The VM may not have been properly shut down: turn it back on to turn it off cleanly
- Delete all .TMP files associated with the virtual disk, in the storage directory of the virtual machine
- Delete all .WRITELOCK files from this VM
- Delete all .LCK (lock) folders associated with VM virtual disk