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] domU minimum and maximum memory

To: Mike Williams <mike.williams@xxxxxxxxxx>
Subject: Re: [Xen-users] domU minimum and maximum memory
From: Timo Benk <timo.benk@xxxxxx>
Date: Thu, 22 Jun 2006 17:16:52 +0200
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 22 Jun 2006 08:18:23 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <200606221558.35376.mike.williams@xxxxxxxxxx>
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: <200606221558.35376.mike.williams@xxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: RoundCube Webmail/0.1b
AFAIK the maxmem parameter does not work.

On Thu, 22 Jun 2006 15:58:35 +0100, Mike Williams <mike.williams@xxxxxxxxxx> 
wrote:
> On Thursday 22 June 2006 15:26, Tim Wood wrote:
>> There is no built in mechanism for this, mostly to make sure you aren't
>> overcommitting the total memory you have in the system.  If you want
> this
>> kind of functionality you would have to build a script which monitors
>> memory usage on each VM and uses the mem-set command to adjust as
>> necessary.  But that would be fairly tricky.
> 
> Thanks for that, it's something to think about.
> However, what does the maxmem option do? :) I forced a VM to use up all
> it's 
> alloted memory, with several hundred more megs maxmem, and just like you'd
> 
> expect, the kernel started killing processes.... Xen didn't do anything.
> 
> -- 
> Mike Williams
> System Administration Manager - Comodo
> Office Tel Europe: +44 (0) 161 8747070
> Fax Europe: +44 (0) 161 8771767
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
-- 
Timo Benk - Jabber ID: fry@xxxxxxxxxx - ICQ ID: #241877854
PGP Public Key: http://m28s01.vlinux.de/timo_benk_gpg_key.asc



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>