Update: According to many of the comments, a number of people are finding this post when searching for help with a VM that will not power on.
For example, if your virtual machine was named “Windows XP Professional”, the line would read: scsi0:0Name = “Windows XP Professional.vmdk” Power on the VM.
It should boot normally, but because the snapshot file is missing, the machine will boot to an earlier state.
After moving those files to a new location or deleting a snapshot file, attempting to boot the virtual machine returns the following error message: Cannot open the disk ‘XXXXXX.vmdk’ or one of the snapshot disks it depends on. I’ve found that following the steps below fixes the problem and allows me to boot the virtual machine as it existed at the time of creation.
DO NOT USE these steps if you need to retain any changes made to the virtual machine since the last snapshot: Open the *file in a text editor and find the line that refers to the old snapshot file, which will look something like: scsi0:0Name = “XXXXXX-000002.vmdk” or ide0:0Name = “XXXXXX-000002.vmdk” Change the value to the filename of the ~1kb file (which happens to be the same as the name of the VM).
A blog about VMware virtual infrastructure with howto's, tips, and tools.
The purpose of the blog is to act as an electronic notepad - to get those things noted that one discovers during daily operations - as well as, hopefully, being helpful to others in the community.
But the investigation is before the fix, so let´s start with that first.
Like mentioned before the VM is powered off and the file lock message pops up when trying to delete the snapshots.
Sometimes is needed to power off the VM so that all vmdk locks are free and VM can consolidate all snapshots.
When trying to consolidate (with VM power down) the disks I get: With this message this issue needs further troubleshooting. Note: Since this issue happen in my v Center DB and v Center was down, I had to connect with v Sphere Client to the ESXi host directly where this VM was allocated ( if this issues is in any of your v Center VMs, you should check which ESXi host is the VMS using, before power off the v Center).
Actually when the customer approached us with that situation we thought of a Snapwatcher bug during beta.