From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MNpFB-00089x-Dw for qemu-devel@nongnu.org; Mon, 06 Jul 2009 10:32:33 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MNpF3-00089C-Gj for qemu-devel@nongnu.org; Mon, 06 Jul 2009 10:32:30 -0400 Received: from [199.232.76.173] (port=52093 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MNpF2-000894-R6 for qemu-devel@nongnu.org; Mon, 06 Jul 2009 10:32:25 -0400 Received: from mx2.redhat.com ([66.187.237.31]:47444) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MNpF2-000354-D2 for qemu-devel@nongnu.org; Mon, 06 Jul 2009 10:32:24 -0400 Date: Mon, 6 Jul 2009 17:31:43 +0300 From: "Michael S. Tsirkin" Subject: Re: [Qemu-devel] Re: [PATCH 0/4] Machine config files Message-ID: <20090706143143.GC12141@redhat.com> 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> <4A520936.5000206@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4A520936.5000206@redhat.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gerd Hoffmann Cc: Jan Kiszka , Markus Armbruster , qemu-devel@nongnu.org On Mon, Jul 06, 2009 at 04:24:54PM +0200, Gerd Hoffmann wrote: > 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. How hard is it to add a fixed size backend id before each device? -- MST