VmWare Failed to lock the file

Community Support
#1

I am using OpenNebula 5.2
I have attach one xx GB disk image to one vCenter VM its attach as secondary VMDK disk as expected, but when i power OFF the vm and Power it ON vm is not power it ON back, in backed vCenter console again try to attach same disk and failed to Power ON .

I have no snapshot for VM.

vCenter Error :- An error was received from the ESX host while powering on VM xxx.
Failed to start the virtual machine.
Module DiskEarly power on failed.
Cannot open the disk ‘/vmfs/volumes/58c/xxx.vmdk’ or one of the snapshot disks it depends on.
Failed to lock the file

#2

Please look attach screenshot .

open disk 1.JPG941×209 18.3 KB
open disk 2.JPG918×93 13.2 KB

#3

Hi Ranveer,
could you paste the output of the following commands?:

  • oneimage show IMAGE_ID -x, where IMAGE_ID is the identifier of the persistent image that you’re having problems with.
  • onedatastore show DATASTORE_ID -x, where DATASTORE_ID is the identifier of the datastore where the previous image is stored.
  • onevm show VMID -x, where VMID is the id of the VM that you’re managing with OpenNebula.

Also are you’re running 5.2.0 or 5.2.1 version?

Cheers!

Open Nebula : After attaching a disk to a VM, getting "failed to lock the file" When I am starting the machine
#4

Sanal, has confirmed me that this a duplicate of this post so visit that post for more information.

#5

Thank you Very Much for your support,.

#6

Thank you for your feedback!

#7

For those who are getting VMWare lock file issues on Windows platform, I have managed to solve the issue with this VMWare lock file Windows post