Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

ESXi 5.0 vmx configuration file and/or snapshot corruption after performing a hot-plug operation followed by a snapshot operation (2005740)

Symptoms

  • Unable to power-on a virtual machine after performing a hot-plug operation followed by a snapshot
  • Snapshots contain data written after the snapshot was taken
  • You see errors similar to:
    • File [] /<vmdkname>.vmdk was not found
    • An unexpected error was received from the ESX host while powering on VM <virtual machine name>.
    • Reason: The system cannot find the file specified.
      Cannot open the disk '<vmdkname>.vmdk' or one of the snapshot disks it depends on.
      VMware ESX cannot find the virtual disk "<vmdkname>.vmdk". Verify the path is valid and try again.

  • In the hostd.log file, you see an entry similar to:

    2011-08-25T10:02:04.312Z [21EF9B90 info 'Libs' opID=C629F9E4-00001115] VMHSVMLoadConfig: Not reading VM's configuration due to migration-related poweroff

Cause

A vmx file can become corrupted when performing a mixture of hot-plug and snapshot operations. The corrupted vmx file may result in further virtual machine corruption.
 
Here are two scenarios:
  • Scenario 1:
    1. You have a powered off virtual machine.
    2. You create a snapshot.
    3. You  power-on the virtual machine.
    4. You add/remove hardware from the virtual machine.
    5. You revert to the snapshot taken in step 1. This takes the powered-on virtual machine to a powered off state.
    6. You add/remove hardware from the virtual machine.
    7. You can no longer power-on the virtual machine.

  • Scenario 2
    1. You have a powered off virtual machine.
    2. You power-on the virtual machine.
    3. You add or remove hardware from the virtual machine.
    4. You power-off the virtual machine.
    5. You create a snapshot.
    6. You update the VM configuration (for example, add or remove hardware).
    7. The VM configuration is now pointing at the pre-snapshot disk files. As a result, the virtual machine is writing to the snapshot file. You do not receive an error. You will only notice a problem  after reverting the snapshot taken in step 5. The disk data will have all of the changes that should have been sent to the delta disk (redo log).

Resolution

This issue is resolved in ESXi 5.0 Patch 01. For more information, see VMware ESXi 5.0 Patch ESXi500-201109401-BG: Updates esx-base (1027808).

Note: A very specific series of steps need to be performed to experience this issue. If you are experiencing an issue with your virtual machine, or virtual machine corruption and you did not perform the steps outlined in this article, contact VMware Technical Support.
 
To avoid vmx file corruption, do not perform hot-plug operations. Perform virtual hardware or virtual device add/remove operations on powered-off virtual machines only.
 
If you already encountered this issue, contact VMware Technical Support. Indicate that you have reviewed this article, and they will work with you in an attempt to restore the virtual machine.

See Also

Update History

09/26/2011 - Added information that the issue is resolved in ESXi 5.0 Patch 01 and added the link to the patch article.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 10 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 10 Ratings
Actions
KB: