Virtual machine power off during snapshot consolidation
search cancel

Virtual machine power off during snapshot consolidation


Article ID: 345522


Updated On:




The issue that the virtual machine power off during snapshot consolidation is resolved in ESXi patches ESXi600-201605401 and ESXi550-201608001 respectively.

When Changed Block Tracking (CBT) is enabled and ESXi hosts in the environment are running ESXi 5.1 or later, you experience these symptoms:
  • When attempting a snapshot consolidation, virtual machines running on block storage power off.
  • Virtual machines state that an error occurred during the quiesce process.
  • The vmware.log file for the virtual machine in question reports entries similar to:

    2016-01-27T13:53:31.687Z| vcpu-0| I120: ----------------------------------------
    2016-01-27T13:53:31.703Z| vcpu-0| I120: Msg_Post: Error
    2016-01-27T13:53:31.704Z| vcpu-0| I120: [msg.checkpoint.continuesync.error] An operation required the virtual machine to quiesce and the virtual machine was unable to continue running.
    2016-01-27T13:53:31.704Z| vcpu-0| I120: ----------------------------------------
    2016-01-27T13:53:31.707Z| vcpu-0| I120: Msg_Post: Error
    2016-01-27T13:53:31.707Z| vcpu-0| I120: [msg.poweroff.commitOn] Performing disk cleanup. Cannot power off.
    2016-01-27T13:53:31.707Z| vcpu-0| I120: ----------------------------------------
    2016-01-27T13:53:31.709Z| vcpu-0| I120: [msg.snapshotVMX.consolidate.cptError] An error occurred while consolidating disks. The virtual machine will be powered off.
    2016-01-27T13:53:31.709Z| vcpu-0| I120: ----------------------------------------
    2016-01-27T13:53:31.711Z| vcpu-0| I120: Vix: [4231837 vigorCommands.c:548]: VigorSnapshotManagerConsolidateCallback: snapshotErr = Could not open/create change tracking file

    Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.


The ESXi host which runs a virtual machine is responsible for locking all associated files relating to the virtual machine. During the snapshot process, another host assumes ownership of the Changed Block Tracking (CBT) file. This can occur for various reasons, including an external API-call received by vCenter Server that queries the CBT file information. When this occurs, this loss of file-lock on the CTK file necessitates that the virtual machine be powered-off for data protection and consistency reasons.


This is a known issue affecting ESXi 5.1.

Currently, there is no resolution.

This issue is resolved in:
  • ESXi 6.0, Patch Release ESXi600-201605401.
  • ESXi 5.5, Patch Release ESXi550-201608001.
Available at VMware Patch Downloads. For more information on downloading patches, see How to download patches in Customer Connect (1021623).

Additional Information

To be alerted when this document is updated, click the Subscribe to Article link in the Actions box.. How to download patches in Customer Connect
Enabling or disabling Changed Block Tracking (CBT) on virtual machines
Powering on a virtual machine fails with the error: Could not open/create change tracking file