Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm running into a problem on my xen 4.0.1 server (debian squeeze)

My host has 32G of memory, Domain-0 has 2048 M assigned to it. (scaled down with xm mem-set Domain-0 2048) top in Domain-0 confirms this.

I created a virtual machine config file (using xen-tools) with the following options:

memory      = '512'
maxmem      = '2048'

Both host and guest machines are running the standard 2.6.32-5-xen-amd64 debian kernel.

'xm create' creates a virtual machine with 512MB of memory as expected.

Then 'xm mem-set domU 1024' will not expand the memory to 1024MB

running 'xm mem-set domU 400' does set the memory to about 400MB

Then 'xm mem-set domU 1024' will expands the memory back to 512MB

Based on this, you would say that xm ignores the maxmem and silently sets maxmem to 512, but in the output of xm top the MAXMEM column reads 2G. the MEM column will not go over 512M.

The output of xm list tells another story, it shows 1024 when I 'xm mem-set domU 1024'.

I've googled myself all away around the internet for this issue and found that most people don't scale back Domain-0. I know I've seen a bugreport about the issue I'm experiencing, but can't find it anymore.

Does anyone see what I'm doing wrong here?

Hmm.. I just upgraded my kernel to the one provided by debian backports. The issue has gone.

share|improve this question
nice to see, there are other people with same problem. did you solved the problem via backport kernel, or are there any other possibilities? thanks for answer ... ronny – user118205 Apr 20 '12 at 8:19

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.