I have seen other topics on this but none seem to match my scenario.
I have an older W2k3 server that is being upgraded to newer hardware and software.
In order for the software to be converted it has to be run on a non-production system.
I am trying to use VMware Converter to build a virtual machine for this case.
I successfully did this 2 years ago but for reasons beyond my control the project was put on hold
and has been picked up again this year. Unfortunately the VM I created 2 years ago is now grossly
out of date and must be rebuilt. Which is now failing.
I have already run into issues trying to do P2V to my vCenter environment so I am trying now
to run it into a VMware Workstation environment. While I can get farther using this method I cannot
get past the stop at 1%.
What I am seeing is on the destination share is a folder is created with two files in it a test.vmdk and test.vmx
along with a folder test.lck. The job status will say something along the lines of 'It'll be 1hour 30 minutes', after about 30 seconds
passes it says the job time will be 1 minute. At this point it deletes all the files it has placed on the share drive and kicks a job
failed. Reason is 'Unable to obtain the lock on virtual disks.'
I have tried 3 versions of Converter 4/5/6 disabled firewalls etc. Any ideas appreciated.
***UPDATE*** I may be on to something. I told it to pre-allocate the disk and now I am up to 3%. Fingers crossed.
**UPDATE 2** Ooof. Got to 94% and then failed with same error message. WTF?
**UPDATE 3** Managed to get it to run to 98% without error. Finally failed with Could not reconfigure VM at the end.
However it did NOT delete the files this time. Unfortunately the VM will not open. It launches but just sits at a black screen.
Trying to work through the .vmx file and see if I can spot a problem. Very odd.
Hi,
in this post have solved a problem similar to yours.
vCenter Converter Standallone Client 6.22: FAILED: Unable to obtain the lock on virtual disks.
ARomeo
I saw that thread but it was not helpful in my case. The winning solution ended up being
to use Converter 4.01 and to pre-allocate the disks. FWIW, on another topic I read where others were unable
to write to a NAS disk while converting. I had no issues with 4.01 and NAS running Windows Storage Server.
Great! thank you for informing me.
ARomeo