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] Fix auto-ballooning of dom0 for HVM domains

To: "Ewan Mellor" <ewan@xxxxxxxxxxxxx>
Subject: RE: [Xen-devel] [PATCH] Fix auto-ballooning of dom0 for HVM domains
From: "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>
Date: Sat, 20 May 2006 00:29:55 +0800
Cc: Charles Coffing <ccoffing@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 19 May 2006 09:31:29 -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: AcZ7VwZA7iYvZqu7RnmDFS4gSlgq7wACk/Jg
Thread-topic: [Xen-devel] [PATCH] Fix auto-ballooning of dom0 for HVM domains
        Thanks for your explaination very much !

Yunhong Jiang 

>-----Original Message-----
>From: Ewan Mellor [mailto:ewan@xxxxxxxxxxxxx] 
>Sent: Friday, May 19, 2006 11:15 PM
>To: Jiang, Yunhong
>Cc: Charles Coffing; xen-devel@xxxxxxxxxxxxxxxxxxx
>Subject: Re: [Xen-devel] [PATCH] Fix auto-ballooning of dom0 
>for HVM domains
>On Fri, May 19, 2006 at 12:23:59PM +0800, Jiang, Yunhong wrote:
>> Hi, Charles
>>      Just one suggestion, for  xen-hvm-auto-balloon.diff, how about
>> change 
>>              xc.domain_setmaxmem(self.domid, m)
>> to 
>>              xc.domain_setmaxmem(self.domid, 
>self.info['memory'] * 1024)
>> The maxmem would be used to check when guest try to increase memory.
>> Also, does anyone know the what the BALLOON_OUT_SLACK on
>> tools/python/xen/xend/balloon.py stands for? The comments said it is
>> "physinfo details are rounded".
>When you get the free memory from xc.physinfo(), it may report 
>(for example)
>100MB free when actually there are 99.9MB free.  It rounds up 
>because you
>are often just a few pages short of the value you expect, 
>because there are
>pages being used for the I/O shared rings, for example.  This 
>means that when
>deciding how much memory to balloon, we need to subtract 1MB.

Xen-devel mailing list