14 Jul 2009

VMotion functionality limited by Video RAM (VRAM)

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.

More in this category: Improving VMotion Performace »

Comments (2)

  1. k

i got 27MB and same error. It's not way to solve problem, its your lack

  Attachments
 
  1. Rynardt Spies    k

That is probably because you have an underlying problem this is not related to the issue described in this post. The issue described in this post has been tried and tested many times before and I can assure you it's accurate for the versions of...

That is probably because you have an underlying problem this is not related to the issue described in this post. The issue described in this post has been tried and tested many times before and I can assure you it's accurate for the versions of vSphere and Guest Operating systems used at the time of writing, which was in 2009. That's a long time ago.

You've not given any information in your comment about the version of vSphere, the guest OS versions, VM hardware versions, tools versions or anything else for that matter that could help anyone help you.

Do some homework on your own issue. Read logs, test, and test again. Work it out for yourself rather than relying on Google and when the possible solutions don't work for you, don't accuse the authors of the articles covering those issues as being lucky. That is poor form.

I'm not going to amend a post that's stood the test of time for 6 and a half years, simply because it didn't work for one person, who clearly cannot be bothered to do some home work on his own infrastructure issues.

Read More
  Attachments
  Comment was last edited about 3 years ago by Rynardt Spies Rynardt Spies
There are no comments posted here yet

Leave your comments

Posting comment as a guest. Sign up or login to your account.
0 Characters
Attachments (0 / 3)
Share Your Location

RT @julianpopov: The year is 2192. The British Prime Minister visits Brussels to ask for an extension of the Brexit deadline. No one remem…
Follow Rynardt Spies on Twitter