[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] Weird xl mem-set behavior

  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Claudiu CurcÄ <alexstrasza2@xxxxxxxxx>
  • Date: Wed, 18 May 2011 18:22:32 +0300
  • Delivery-date: Wed, 18 May 2011 08:24:10 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=YP+4KBH/F+8MQL3IC+QlaFjCDZtejg2ueexMT1jYvmNk1bJkc2ZDTE6BXslNQdOUTF AqyTxX9bIT3c416C6zkPI3H4OWEIDJt5dUER+LsS+sll75pRYnwEvKAsuqgTd35mBAd2 fS1AkOBC83ckuJRVSxCHQR4H88MLUpobBVrwk=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>


I'm struggling to handle the amount of memory that dom0 gets on some system.

It's a system with 8GB of RAM, running 2.6.38-6 with pv_ops and Xen 4.1
If I want to set the amount of memory for dom0, I get very bogus
results. See here: http://pastebin.com/gRgY9ERN If I use the M
notation (xl mem-set 0 4096M) the outcome is similarily unpredictable,
and sometimes I get the memory set to something like 200-300MB and in
rare cases a kernel panic.

Also, if I set the "dom0_mem=X" kernel parameter, the amount of memory
Xen gives to dom0 is fairly random... sometimes 2GB, sometimes 6GB,
sometimes ~500MB, regrardless of what value I use or the unit I use (M
or no unit, for the default KB).

Anyone else has experienced this in Xen 4.1? Thanks!

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.