From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:41974) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UhwVH-0002YM-IL for qemu-devel@nongnu.org; Thu, 30 May 2013 02:38:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UhwVC-0001sK-SD for qemu-devel@nongnu.org; Thu, 30 May 2013 02:38:27 -0400 Received: from mx1.redhat.com ([209.132.183.28]:8165) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UhwVC-0001sC-JI for qemu-devel@nongnu.org; Thu, 30 May 2013 02:38:22 -0400 Message-ID: <51A6F3C0.8040101@redhat.com> Date: Thu, 30 May 2013 08:37:52 +0200 From: Gerd Hoffmann MIME-Version: 1.0 References: <20130523124132.GA18596@redhat.com> <20130528235309.GA31648@morn.localdomain> <20130529084544.GG4472@redhat.com> <874ndl9355.fsf@codemonkey.ws> In-Reply-To: <874ndl9355.fsf@codemonkey.ws> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] KVM call agenda for 2013-05-28 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: KVM devel mailing list , Juan Quintela , dwmw2@infradead.org, seabios@seabios.org, qemu-devel qemu-devel , Kevin O'Connor , "Michael S. Tsirkin" , ddutile@redhat.com, lersek@redhat.com Hi, > Why should this be true? Shouldn't we be allowed to increase the amount > of memory the guest has across reboots? That's equivalent to adding > another DIMM after power off. poweroff is equivalent to exiting qemu, not to guest reset. > Not generating tables on reset does limit what we can do in a pretty > fundamental way. Even if you can argue it in the short term, I don't > think it's viable in the long term. I don't think so. The procedure for adding/removing non-hotpluggable hardware is: poweroff, plugin/-out hardware (change config in qemu), boot. Hotpluggable hardware doesn't need acpi table updates. cheers, Gerd