An I/O error occurred while saving the checkpoint: 0 (Resource temporarily unavailable) Failed to write checkpoint data (offset 42876928, size 16384): Failed to resume VM. Module Migrate power on failed. vMotion migration failed. The checkpoint data length (16384 bytes) or the offset (41943040 bytes) exceeds the maximum checkpoint data length (41943040 byte)

This error appear when we do vmotion on host.
This case happen on esxi 5.0 but solve on 5.0 update 1. You should do this action as below :

This issue has been resolved in ESXi 5.0 Update 1.

To work around this issue on ESXi 5.0, use one of these options:

• Change the resolution to a single screen of 1280 x 1024 or smaller before using vMotion for migration.
• Do not upgrade to Virtual Machine Hardware version 8.
• Increase the base checkpoint cache size. Doubling this value from its default of 8 MB to 16 MB (16777216 bytes) should be enough for any display resolution. If you are using two displays at 1600 x 1200 each, increase the setting to 20 MB (20971520 bytes).

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.

Note: If you don’t want to power off your virtual machine to change the resolution, you can also append migrate.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.
• Set mks.enable3d = TRUE for the virtual machine:
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 mks.enable3d to the name column and add True to the value column.
8. Click OK to save the change.

Caution: This workaround increases the overhead memory reservation by 256 MB. As such, it may have a negative impact on HA Clusters with strict Admission Control. However, this memory is only used if the 3D application is active. If, for example, Aero Basic and not Aero Glass is used as a window theme, most of the reservation is not used and the memory could be kept available for the ESXi host. The reservation still affects HA Admission Control if large multi-monitor setups are used for the virtual machine and if the CPU is older than a Nehalem processor and does not have the SSE 4.1 instruction set. In this case, VMware does not recommend using 3D. The maximum recommended resolution for using 3D, regardless of CPU type and SSE 4.1 support, is 1920 x 1200 with dual screens.

Reference :

KB vmware

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2005741

Hopely this help your problem.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s