From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Charles Coffing" Subject: RE: [PATCH] Fix auto-ballooning of dom0 for HVM domains Date: Fri, 19 May 2006 13:59:09 -0600 Message-ID: <446DCFE0.D169.003C.0@novell.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Yunhong Jiang , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org > On Thu, May 18, 2006 at 10:23 PM, in message , "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) Ideally, yes, I would agree. But later, in qemu, another increase_reservation() is called. If I make the suggested change, I suspect that qemu will fail to get its memory. Or is this upper limit not checked when increase_reservation() is called from dom0?