WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Why limit dom0's memory?

To: "Gastón Keller" <gastonkeller@xxxxxxxxx>
Subject: Re: [Xen-users] Why limit dom0's memory?
From: "Todd Deshane" <deshantm@xxxxxxxxx>
Date: Sat, 14 Jun 2008 12:09:30 -0400
Cc: "Sandor W. Sklar" <ssklar@xxxxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sat, 14 Jun 2008 09:10:05 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to :to:subject:cc:in-reply-to:mime-version:content-type:references; bh=jh6AMURfekLPMZY/lY11iYGvUF8oM7g5O5ObVoY67hc=; b=gkRfrOZXDK+kB7URM2G+9t0De37CAzAdpeZ28GPWHvGkEwYgl5mTYBdlAnEmHyjVTZ WMYeouZbtGIYPLMC8ShPPoUAe/I/Ik+KM8sA/OOvXZd81dxwDSNenl9jxCSQLO0iD9yi EmriG6wBnOTWe4WeUk0LTaZ4Kt+j36atGrnFY=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:cc:in-reply-to :mime-version:content-type:references; b=jENVaPj5n86wrQKuFk52gZ+Yn2kMVXzWlldhaZtc0pe1V2+X61Z2jEvrmyiPBdJ95o bdAOSlyhRAadvljBx565+Cu7KFKWd1bHQXBmfjw0uZZBb4PctwAkZSEKuAw0FpGc3Uk+ pceXYB6DDPZIZiP526AvliGkdYkZ1cqHJh3aM=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <bd6e1f920806140858m25fc4812p378db14ee4c51745@xxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <B32A2735-4BBC-4A2B-B83C-F49AA4745C26@xxxxxxxxxxxx> <bd6e1f920806140534s1bc2c406k871149cdc077eee8@xxxxxxxxxxxxxx> <bd6e1f920806140535v359ac4c0vaf6c79b94c86928c@xxxxxxxxxxxxxx> <FDAD39ED-5462-463D-9E2C-615AE8F2C05D@xxxxxxxxxxxx> <bd6e1f920806140858m25fc4812p378db14ee4c51745@xxxxxxxxxxxxxx>
Reply-to: deshantm@xxxxxxxxx
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx


On Sat, Jun 14, 2008 at 11:58 AM, Gastón Keller <gastonkeller@xxxxxxxxx> wrote:
On Sat, Jun 14, 2008 at 11:47 AM, Sandor W. Sklar <ssklar@xxxxxxxxxxxx> wrote:
>
> On Jun 14, 2008, at 5:35 AM, Gastón Keller wrote:
>
>>>  I have this wrong, or am I not understanding something?
>>
>> AFAIK what some people is doing is setting a level of memory for Dom0
>> for it to never go down that level (giving memory to the guests). That
>> is, if you set the memory to 1 GB, Dom0 will allocate all your memory
>> except for that 1 GB. It's a way of ensuring that Dom0 will never run
>> out of memory.
>
> Ah, thanks!  That makes sense.  Is there some formula for determining how
> much memory a dom0 might need, given a system with X amount of RAM, and X
> number of guests?

I wouldn't know what to tell you. Sorry! =)

I don't think there is a magic formula like that anyway.

It will depend on what you are using the system for. You should try to minimize what
is run in dom0. You should make sure that your guests have sufficient memory so
that they are not thrashing the disk. All this depends on the load your system is
going to take on. Bottom line is that not running out of memory on Dom0 is first
priority, then guests. Always try to give some wiggle room if possible and do lots
of testing if you can.

For more information on Xen in book format, take a look at "Running Xen: A Hands-on
Guide to the Art of Virtualization" (http://runningxen.com)
 
Cheers,
Todd
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users