From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:34144) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RYzA2-0002mV-T9 for qemu-devel@nongnu.org; Fri, 09 Dec 2011 07:02:44 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RYz9y-0001cE-8y for qemu-devel@nongnu.org; Fri, 09 Dec 2011 07:02:42 -0500 Received: from mx1.redhat.com ([209.132.183.28]:37714) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RYz9y-0001c8-1e for qemu-devel@nongnu.org; Fri, 09 Dec 2011 07:02:38 -0500 Received: from int-mx12.intmail.prod.int.phx2.redhat.com (int-mx12.intmail.prod.int.phx2.redhat.com [10.5.11.25]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id pB9C2boX017022 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 9 Dec 2011 07:02:37 -0500 Date: Fri, 9 Dec 2011 17:32:33 +0530 From: Amit Shah Message-ID: <20111209120233.GD2464@amit-x200.redhat.com> References: <20111209115521.GB25940@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20111209115521.GB25940@redhat.com> Subject: Re: [Qemu-devel] [PATCH 0/3] balloon: error if guest driver is not initialised List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Daniel P. Berrange" Cc: Luiz Capitulino , qemu list , Markus Armbruster On (Fri) 09 Dec 2011 [11:55:21], Daniel P. Berrange wrote: > On Fri, Dec 09, 2011 at 05:19:35PM +0530, Amit Shah wrote: > > Hello, > > > > These patches make qemu generate an error on failure in setting a > > balloon value: > > > > (qemu) balloon 400 > > Device 'balloon' has not been activated > > > > This can happen when the guest hasn't yet loaded a balloon driver. > > This is a pretty significant change in behaviour/semantics of the > balloon driver interface. > > eg, when libvirt starts a guest, it launches QEMU paused, and > immediately sets a balloon target, which may be lower than the > memory limit, and then starts CPUS to let the guest boot. The > guest will utilize this target when it loads the balloon driver > during bootup. > > With this proposed change, libvirt will immediately get > an error, and have to guess when the balloon driver might be > loaded by the guest, in order to set the limit post-boot. > > > Previously, such a ballooning attempt didn't produce an error, but the > > virtio-balloon driver remembered the value nevertheless, causing a > > module load in the guest using the attempted balloon value > > originally. This may not be the desired course of action. > > This is *exactly* desired behaviour. Please don't change this. OK, thanks. I'll retract this patch series. Amit