This issue occurs if the virtual machine has a snapshot and if a parent disk has been modified. When you boot a virtual machine, it tries to boots from the snapshot. Modifying the parent virtual disk invalidates the snapshot and causes the virtual machine to stop functioning.
Note: A snapshot is neither a backup nor a full virtual disk. It only maintains a record of incremental changes since the time it is created. Any changes made to a parent disk or to an earlier snapshot indicates that the changes recorded in this snapshot are no longer valid. This leads to loss of data created or modified after the snapshot was taken. For general information about snapshots, see
Understanding Snapshots and AutoProtect in VMware Fusion (1014509).
To resolve this issue, you must either restore the virtual machine partially or fully from a backup or remove the snapshot.
To restore the virtual machine from a backup or to remove the snapshots, try one or more of the following options:
Notes:
- Restore the parent virtual disk files from a backup that was taken when the virtual machine was functional. To identify the parent virtual disk files, see Contents of the virtual machine bundle in Fusion (1021016).
- Restore all virtual machine files from a backup that was taken when the virtual machine was functional.
Note: Restoring virtual machine files results in loss of data modified after the backup was taken.
- Remove the snapshot from the virtual machine.
Note: Removing the snapshot results in loss of data modified after the snapshot was taken.
To remove the snapshot and to restore the virtual machine to working order: -
- Delete all files and folders with the following extensions from the virtual machine bundle:
- Delete all snapshot virtual disk files from the virtual machine bundle. For details on snapshot virtual disk files, see Contents of the virtual machine bundle in Fusion (1021016).
- Edit the virtual machine's configuration (.vmx) file and change all references to snapshot disks to the parent disk. Specifically, look for entries that include 00000<x>.vmdk, where <x> is a number, and delete 00000<x>.vmdk. Leave the rest of the entry intact. For details, see Editing the .vmx file for your Fusion virtual machine (1014782).
- Save the .vmx file. The virtual machine powers on using only the parent virtual disk.