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

Re: [Xen-users] settinjg dom0 memory, where did I go wrong?


  • To: xen-users@xxxxxxxxxxxxx
  • From: "Michael Egglestone" <mike@xxxxxxxxx>
  • Date: Fri, 03 Aug 2012 10:40:07 -0700
  • Delivery-date: Fri, 03 Aug 2012 17:41:15 +0000
  • List-id: Xen user discussion <xen-users.lists.xen.org>

Alexandre Kouznetsov <alk@xxxxxxxxxx> writes:
El 02/08/12 23:48, Michael Egglestone escribiÃ:
> Here is my /etc/default/grub
>
> /GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=4096M dom0_vcpus_pin"/
> [...]
> I've updated grub to populate /boot/grub/grub.cfg and then rebooted.
This two stepas are the only relevant ones to achieve the Dom0 memory
restriction.

While booting, you should have interacted with Grub, checking if the
parameter dom0_mem is really present in the right place. There you would
probably find that it is not.

The variable used to set Dom0 memory is slightly different:
GRUB_CMDLINE_XEN="dom0_mem=4032"

It appears my system could fall into this link:


If I set my system to around 2G or lower, it appears correct, but if I start going above 2G, even
up into the teens of Gigabytes, I see lost RAM.
So, until Wheezy becomes stable, I'll stick with Dom0 at 2G.
Thanks!

Cheers,
Mike
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users

 


Rackspace

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