Knowledge Base

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

When Changed Block Tracking is enabled, backing up the virtual machine fails (2114076)

Symptoms

  • Backing up a virtual machine with Change Block Tracking (CBT) enabled fails after upgrading to VMware ESXi 6.0.x on host
  • Backing up a virtual machine with Change Block Tracking (CBT) enabled fails after installing VMware ESXi 6.0.x on host
  • Powering on the virtual machines fails.
  • Expanding the size of a virtual disk fails.
  • Taking virtual machine quiesced snapshots fails.
  • The vSphere Client displays the error similar to:

    An error occurred while taking a snapshot: msg.snapshot.error-QUIESCINGERROR

    Note: This error may or may not be present
  • In the /var/log/vmkernel.log file on the ESXi host where the affected virtual machine is running, you see the error similar to:

    <YYYY-MM-DD>T<TIME>.623Z cpu5:809536)WARNING: CBT: 191: No memory available! Called from 0x4180219af50e
    <YYYY-MM-DD>T<TIME>.637Z cpu5:809536)WARNING: CBT: 191: No memory available! Called from 0x4180219af50e
    <YYYY-MM-DD>T<TIME>.648Z cpu5:809536)WARNING: CBT: 191: No memory available! Called from 0x4180219af50e


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

  • In the vmware.log file of the affected virtual machine, you see an entry similar to:

    vcpu-0| I120: DISKLIB-CBT : Creating cbt node 92b78c-cbt failed with error Cannot allocate memory (0xbad0014, Out of memory)

Cause

This issue occurs due to heap exhaustion. It can occur when attempting to enable Change Block Tracking (CBT). If a virtual machine with a large number of virtual disks reached an upper threshold, enabling CBT fails because of heap exhaustion. This issue also occurs with multiple virtual machines with CBT enabled. In case of Windows virtual machines with VSS enabled, taking a quiesced snapshot creates double the amount of memory overhead. Finally, if the heap is close to exhaustion, performing a vMotion can also cause this issue as that process involves taking snapshots as well.

Note: The virtual disks can be spread across virtual machines or can be in a single virtual machine.

Resolution

This issue is resolved in VMware ESXi 6.0 Build 2715440, available at VMware Downloads. For more information, see VMware ESXi 6.0, Patch Release ESXi600-201505001 (2116125).

Additional Information

For more information on enabling and disabling CBT, see Enabling Changed Block Tracking (CBT) on virtual machines (1031873).

See Also

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

  • 25 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)




Please enter the Captcha code before clicking Submit.
  • 25 Ratings
Actions
KB: