new1234.jpg
Home > VMware > VMware: The checkpoint data length (16384 bytes) or the offset (16776528 bytes) exceeds the maximum checkpoint data length

VMware: The checkpoint data length (16384 bytes) or the offset (16776528 bytes) exceeds the maximum checkpoint data length

Today I was importing some virtual machines (delivered by a 3rd party company) to the new vSphere 5 environment of a customer, the import was successful but after a vMotion I received this warning:

 

Module Migrate power on failed.
vMotion migration [168099940:1334234558581378] failed. The checkpoint data length (16384 bytes) or the offset (16776528 bytes) exceeds the maximum checkpoint data length (16777216 byte).

 

image

Solution:

The owner of the template installed the OS with a 1920 x 1080 resolution, after changing the resolution to 1280 x 1024 the GFX memory usage degraded to normal (under 30 MB).

 

image

After changing the resolution I was able to migrate the virtual machines,

Other possible solutions:

  • Do not upgrade to Virtual Machine Hardware version 8.
  • Increase the base checkpoint cache size. Doubling it from its default 8MB to 16MB (16777216 byte) should be enough for every single display resolution. If you are using two displays at 1600×1200 each, increase the setting to 20MB (20971520 byte).
    To increase the base checkpoint cache size:
    1. Power off the virtual machine.
    2. Click the virtual machine in the Inventory.
    3. On the Summary tab for that virtual machine, click Edit Settings.
    4. In the virtual machine Properties dialog box, click the Options tab.
    5. Under Advanced, select General and click Configuration Parameters.
    6. Click Add Row.
    7. In the new row, add migrate.baseCptCacheSize to the name column and add 16777216 to the value column.
    8. Click OK to save the change.
    9. Note: If you don’t want to power off your virtual machine to change the resolution, you can also appendmigrate.baseCptCacheSize = 16777216 to the /etc/vmware/config file on the target host. This adds the option to every VMX process that is spawning on this host, which happens when vMotion is starting a virtual machine on the server.

 

More information: VMware

sanderdaems

Sander Daems is founder and author of this blog and working as a Lead (Sr.) Consultant by UNICA ICT Solutions. Sander has over 15 years experience in IT, primary focus: virtualization and modern worksplace.

More Posts - Website

Follow Me:
TwitterLinkedIn

  1. tdirys
    April 24th, 2012  (Quote) at 07:58  (Quote) | #1

    Nice, solved for me! Thanks SDaems

    I solved this issue to use the video ram calculator

  1. No trackbacks yet.