From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MNoTo-0004Px-9q for qemu-devel@nongnu.org; Mon, 06 Jul 2009 09:43:36 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MNoTj-0004OB-Ko for qemu-devel@nongnu.org; Mon, 06 Jul 2009 09:43:35 -0400 Received: from [199.232.76.173] (port=51165 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MNoTj-0004O4-Al for qemu-devel@nongnu.org; Mon, 06 Jul 2009 09:43:31 -0400 Received: from mx2.redhat.com ([66.187.237.31]:34178) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MNoTi-0006SZ-MC for qemu-devel@nongnu.org; Mon, 06 Jul 2009 09:43:31 -0400 Message-ID: <4A51FF7B.4000602@redhat.com> Date: Mon, 06 Jul 2009 15:43:23 +0200 From: Gerd Hoffmann MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: [PATCH 0/4] Machine config files References: <20090610173803.4674.82538.stgit@wren.home> <878wjx374h.fsf@pike.pond.sub.org> <4A3269C3.3050307@redhat.com> <4A327E2C.1060207@siemens.com> <20090706124928.GB11998@redhat.com> In-Reply-To: <20090706124928.GB11998@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael S. Tsirkin" Cc: Jan Kiszka , Markus Armbruster , qemu-devel@nongnu.org On 07/06/09 14:49, Michael S. Tsirkin wrote: > On Fri, Jun 12, 2009 at 06:11:24PM +0200, Jan Kiszka wrote: > Can't we extend loadvm/savevm format to support machine config? It is > already supported by all devices, it seems that we just need to add some > detail such as pci addresses, and qemu flags to save/load this config. > No? No. Adding some info to the devices doesn't cut it as you also need to know which devices are present in the first place. Current savevm doesn't do that, thats why you have to start the virtual machine with the complete set of command line arguments even when resuming / migrating. Once we have a working device tree implementation we can fix that too though. Rough plan is: (1) convert drivers to qdev. (2) create qdev device tree from config file (probably fdt). With this in place it is just a little step to also carry this in the savevm format: We just need a to do a qdev->fdt conversion, then we can send the device tree as one savevm section and rebuild the vm from that. cheers, Gerd