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


Re: [Xen-devel] [PATCH] Make "xm mem-set" be lower bound on domX-min-mem

To: "Puthiyaparambil, Aravindh" <aravindh.puthiyaparambil@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Make "xm mem-set" be lower bound on domX-min-mem
From: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Date: Fri, 19 May 2006 16:29:23 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 19 May 2006 08:29:44 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <EF8D308BE33AF54D8934DF26520252D3047794C2@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <EF8D308BE33AF54D8934DF26520252D3047794C2@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Fri, May 12, 2006 at 12:16:57PM -0400, Puthiyaparambil, Aravindh wrote:

> This patch causes "xm mem-set" to be lower bound on domX-min-mem option
> in xend-config. Another configuration option called domU-min-mem has
> been introduced, which works similarly to dom0-min-mem. This is prevents
> users from freezing the system when doing "xm mem-set" on very low
> values like 32M.
> Signed-off-by: Aravindh Puthiyaparambil
> <aravindh.puthiyaparambil@xxxxxxxxxx>

I'm not so sure about this one.  We've discussed this issue recently, and
there are a number of people (notably some of the guys at IBM) who don't want
this limit to be imposed by Xend.  If you have one VM that you know to be safe
in 16MB, say, then you either need to set domU-min-mem to 0, defeating the
point of having it, or you need to have a "force" flag to override
domU-min-mem.  The latter option here was disliked, because it was felt that
tools for VM management would just end up using the force flag all the time
because they don't know what the domU-min-mem setting is, and again, this
would defeat the point.

The min-mem value should be a per-VM setting rather than a Xend setting, so
the check belongs with the tool that's managing VMs for you.


Xen-devel mailing list

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