Twitter Updates
| VMotion functionality limited by Video RAM (VRAM) |
|
|
|
| Written by Rynardt Spies | |
| Tuesday, 14 July 2009 16:41 | |
|
Today I was planning on testing the new 16 patches released by VMware for vSphere 4. I wanted to place these on my 2nd ESX host. I normally place my ESX hosts in maintenance mode before I remedaite updates. As I placed esx2 in maintenance mode, the VMs, as expected, started to migrate over to the other hosts in the cluster with VMotion. The VMotion migration of two of my VMs running Windows XP, failed with the following error message: A general system error occurred: Failed to write checkpoint data (offset 33558328, size 16384): Limit exceeded It turns out that a VM must have less than 30MB Video RAM or VRAM assigned in order to be compatible with VMotion. As I normally run these two VMs at 1680 x 1050 resolution, I went all out an assigned the maximum amount of memory allowed, which is 128MB as VRAM, hence the reason for the VMotion failure.
|
Popular
- Building an iSCSI Openfiler SAN on a USB Stick
- Simple VMware vSphere 4 & 5 License Calculator
- Replace SSL Certificates: Replace vCenter Server SSL Certificates
- Patching ESX 3.5 Using esxupdate
- My experiences with Installing vCenter on Windows Server 2008 R2
- ESX 3i: Host in HA Cluster must have userworld swap enabled
- ESX 3.5 on HP Proliant ML115 G5
- Replacing vSphere SSL Certificates
- VMware ESXi 3.5 on HP Proliant ML110 G5
- Clearing a GUID Partition Table (GPT) in Linux
Support VirtualVCP!
Information and Resources on this site are 100% free, however it costs money to run this site. Please help support this site by giving a donation.









