This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-users] dom0-min-mem needed

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] dom0-min-mem needed
From: Jordi Espasa Clofent <jespasac@xxxxxxxxxxxx>
Date: Wed, 26 Nov 2008 10:03:54 +0100
Delivery-date: Wed, 26 Nov 2008 01:04:38 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (X11/20081120)
Hi all,

After an undesirable episode of random rare reboots at dom0 level, I decided to increase the dedicated dom0 memory as following:

xen01:/# cat /etc/xen/xend-config.sxp | grep dom0-min-mem
# dom0-min-mem is the lowest memory level (in MB) dom0 will get down to.
# If dom0-min-mem=0, dom0 will never balloon out.
(dom0-min-mem 0)
xenjocs01:/# cat /boot/grub/menu.lst | grep dom0
kernel          /boot/xen-3.2-1-amd64.gz dom0_mem=1024M

And the dom0 is rock-solid again. I use XEN 3.2.1 and Debian Etch as SO. Before the random reboots I've used only a dedicated 196MB for dom0. The actual "load" of dom0 is:

Name ID Mem VCPUs State Time(s) Domain-0 0 1024 1 r----- 2400.5 xen-game01 22 512 1 -b---- 184.0 xen-game04 1 512 1 -b---- -9176099843.7 xen-game05 2 1024 1 -b---- 401.5 xen-game06 3 512 1 -b---- 397.5 xen-game07 4 256 1 -b---- 1085.7 xen-game09 5 512 1 -b---- 610.1 xen-game11 6 256 1 -b---- 5997.6 xen-game12 7 256 1 -b---- 366.8 xen-game13 8 512 1 -b---- 12316.5 xen-game14 9 512 1 -b---- 71.7

So, the next question is obvious
¿How to calculate the needed dom0 RAM according the domUs total RAM to manage? I'ts clear that only 196MB was not enough to manage the domUs.

PD. ¿Anybody knows what is -9176099843.7 entry (xen-game04 domU) in Time(s) column?
Jordi Espasa Clofent

Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] dom0-min-mem needed, Jordi Espasa Clofent <=