From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MNp7y-0006z0-Da for qemu-devel@nongnu.org; Mon, 06 Jul 2009 10:25:06 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MNp7t-0006wO-3A for qemu-devel@nongnu.org; Mon, 06 Jul 2009 10:25:05 -0400 Received: from [199.232.76.173] (port=51004 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MNp7s-0006w4-LR for qemu-devel@nongnu.org; Mon, 06 Jul 2009 10:25:00 -0400 Received: from mx2.redhat.com ([66.187.237.31]:59749) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MNp7s-0001v7-3f for qemu-devel@nongnu.org; Mon, 06 Jul 2009 10:25:00 -0400 Message-ID: <4A520936.5000206@redhat.com> Date: Mon, 06 Jul 2009 16:24:54 +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> <4A51FF7B.4000602@redhat.com> <20090706135616.GA12141@redhat.com> In-Reply-To: <20090706135616.GA12141@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 15:56, Michael S. Tsirkin wrote: > On Mon, Jul 06, 2009 at 03:43:23PM +0200, Gerd Hoffmann wrote: >> 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. > > Actually at least for pci devices you have the devid/vendor id > register - from this you can know which devices are present. Doesn't help you. You can't easily pull out that information from the savevm file. And even it you could you still don't know which backend actually drives that piece of hardware. cheers, Gerd