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).
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
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.
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:
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.
To change the amount of VRAM assigned to a virtual machine running on an ESX host managed by vCenter Server 4.0:
To change the amount of VRAM assigned to a virtual machine running on an ESX host managed by vCenter Server 2.5:
.vmx
) on the ESX host. .vmx
file. .vmx
file for the virtual machine with a tag of svga.vramSize . It
displays the value in bytes. .vmx
file and change the value for svga.vramSize
to 30MB or less.svga.vramSize=31457280
..vmx
file. .vmx
file for the virtual machine, in the path noted at step 2 above. .vmx
file and click Add to Inventory.