Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

vMotion fails at 80% with a general system error (1011971)

Last Updated: 3/20/2024Categories: TroubleshootingTotal Views: 25443Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

vMotion fails at 80%

If you put the host in maintenance mode, it fails and experiences a purple screen error.

In vCenter Server, an error window appears with a message similar to one of these:

A general system error occurred: Failed to write checkpoint data (offset 33558328, size 16384): Limit exceeded

A general system error occurred: Failed waiting for data. Error bad0007. Bad parameter.

A general system error occurred: failed to initiate VMotion dest (vim.fault.InvalidState).

The <CPDE></CPDE>vmware.log for the virtual machine being migrated has entries similar to:

vmx| Migrate_SetFailure: Now in new log file.
vmx| Migrate_SetFailure: Failed to write checkpoint data (offset 33558528, size 16384): Limit exceeded
vmx| Msg_Post: Error
vmx| [vob.vmotion.write.outofbounds] VMotion [c0a8644e:1243364928717250] failed due to out of bounds write: offset 33558528 or size 16384 is greater than expected
vmx| [msg.checkpoint.migration.openfail] Failed to write checkpoint data (offset 33558528, size 16384): Limit exceeded.
vmx| ----------------------------------------
vmx| MigrateWrite: failed: Limit exceeded

The hostd.log for the source or destination host may contain entries similar to:

[F6512B90 info 'vm:/vmfs/volumes/fff91bd3-41793f11/ITGVMS01-13/ITGVMS01-13.vmx'] Question info: VMotion [a210935:125476923788 2447] failed due to out of bounds write: offset 33562624 or size 16384 is greater than expected
[F66C96D0 verbose 'vm:/vmfs/volumes/fff91bd3-41793f11/ITGVMS01-13/ITGVMS01-13.vmx'] Retrieved current VM state from found ry 5, 2
[F66C96D0 verbose 'vm:/vmfs/volumes/fff91bd3-41793f11/ITGVMS01-13/ITGVMS01-13.vmx'] VMotionLastStatusCb: Failed with error 536870918: Failed waiting for data. Error bad0006. Limit exceeded.
[F66C96D0 info 'VMotionDst (1254769237882447)'] ResolveCb: Failed with fault: (vmodl.fault.SystemError) { dynamicType = <unset>,
faultCause = (vmodl.MethodFault) null,
reason = "Failed waiting for data. Error bad0006. Limit exceeded.

Resolution

This issue is resolved in ESX/ESXi 4.0 Update 1. You can download the latest version of ESX/ESXi 4 from the vSphere download page.

Prior to ESX/ESXi 4.0 Update 1, this issue may occur if Video RAM (VRAM) is greater than 30MB for a virtual machine.

Notes:

Using VMotion to migrate a virtual machine with VRAM greater than 30MB to an ESX/ESXi 4.0 Update 1 host might prevent you from migrating it back to a host that does not have this fix.

When using high resolution monitors, VMware View may change the virtual machine's VRAM to greater than 30 MB.

To work around this issue, if you cannot upgrade to ESX/ESXi 4.0 Update 1, ensure that the amount of VRAM assigned to the virtual machine is 30MB or less.

vCenter Server 4.0

To change the amount of VRAM assigned to a virtual machine running on an ESX host managed by vCenter Server 4.0:

Power off the virtual machine.

Right-click on the virtual machine and click Edit Settings.

Click Hardware > Video card > Enter total video RAM.

Set the value to 30MB or less.

Save the changes.

Power on the virtual machine.

vCenter Server 2.5

To change the amount of VRAM assigned to a virtual machine running on an ESX host managed by vCenter Server 2.5:

Power off the virtual machine.

Record the path to the virtual machine configuration file (extension .vmx) on the ESX host.

Right-click on the virtual machine and click Edit Settings > Options > General Options > Virtual Machine Configuration File.

Log in to the ESX host as root using an SSH client.

Make a backup copy of the .vmx file.

The VRAM size is listed in the .vmx file for the virtual machine with a tag of svga.vramSize . It displays the value in bytes.

Edit the .vmx file and change the value for svga.vramSize to 30MB or less.

Note: When set to 30MB, the entry reads svga.vramSize=31457280.

Save the .vmx file.

Remove the virtual machine from the Inventory in vCenter.

Add the virtual machine to the Inventory in vCenter by browsing the datastore from vCenter to locate the .vmx file for the virtual machine, in the path noted at step 2 above.

Right-click on the .vmx file and click Add to Inventory.

Power on the virtual machine.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware VirtualCenter

VMware vCenter Server

VMware ESX Server

Related Versions:

VMware VirtualCenter 2.5.x

VMware vCenter Server 4.0.x

VMware ESX Server 3.5.x

VMware ESX 4.0.x

Take Our Survey

Support Assistant