Symptoms
- Cannot power on the virtual machine
- Powering on the virtual machine fails
- You see the error:
An unexpected error was received from the ESX host while powering on VM VM_name.
Reason: ReasonCannot open the disk disk_name or one of the snapshot disks it depends on.
Where Reason is one of these:- Reason: Failed to lock the file.
- Reason: The file specified is not a virtual disk.
- Reason: The parent virtual disk has been modified since the child was created.
Resolution
- The error Failed to lock the file means that another process is opening the file and the process you are using cannot open the file properly.
This typically occurs if you:- Start two copies of the .vmx file
- Power on a virtual machine with mounted disks (via the vmware-mount utility)
- Try to turn on a virtual machine through the user interface during a snapshot operation
- Try to add the same virtual disk to the machine twice.
To resolve this issue, see Investigating virtual machine file locks in ESX/ESXi (10051).
- The error The file specified is not a virtual disk can occur if the file you are pointing at is not a virtual machine.
To resolve this issue, remove the disk from the virtual machine and re-add it. When you re-add it, you can use the datastore browser to locate the disk on one of your datastores. - The error The parent virtual disk has been modified since the child was created occurs when snapshots are in a bad state, either through manual intervention or through a system failure.
To resolve this issue, see Resolving the CID mismatch error: The parent virtual disk has been modified since the child was created (1007969).
Source:-
No comments:
Post a Comment