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] xm mem-set issues

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
Subject: RE: [Xen-devel] xm mem-set issues
From: "Puthiyaparambil, Aravindh" <aravindh.puthiyaparambil@xxxxxxxxxx>
Date: Thu, 11 May 2006 17:26:03 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 11 May 2006 14:26:31 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcZ1PrYAPnZ4NcRZT4eIk9h8Y6411QAAdr6A
Thread-topic: [Xen-devel] xm mem-set issues
> Possibly. Perhaps a min-mem parameter in the xend config file or
> something like that.

I see that there is a dom0-min-mem parameter in the xend config file.
But I am able to do "xm mem-set 0 32M" and shoot myself in the foot. :-)
I guess the parameter is having no effect. I will look into this.

> The bug here is that 'xm list' shows the current target allocation for
> the guest (as specified to mem-set) rather than what the guest is
> currently using. It'd be good to fix this.

I thought the balloon driver was going through with the increase. I will
send in a fix for this too.

And for the mem-set to less that 2% of initial memory issue, I am
assuming the check should go in the balloon driver. Am I right?


Xen-devel mailing list

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