From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Michael S. Tsirkin" Subject: Re: Configuration vs. compat hints [was Re: [Qemu-devel] [PATCHv3 03/13] qemu: add routines to manage PCI capabilities] Date: Sun, 14 Jun 2009 12:50:16 +0300 Message-ID: <20090614095016.GA7560@redhat.com> References: <20090610150129.GC28601@redhat.com> <200906101624.30659.paul@codesourcery.com> <20090610174301.GC7416@shareable.org> <20090610182227.GN28601@redhat.com> <20090610192702.GH7416@shareable.org> <1244796209.16425.20.camel@blaa> <4A326B5C.5010501@codemonkey.ws> <1244821292.30522.56.camel@blaa> <4A327E4A.7010300@codemonkey.ws> <1244825303.26769.19.camel@blaa> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Anthony Liguori , Jamie Lokier , Carsten Otte , kvm@vger.kernel.org, Glauber Costa , Rusty Russell , qemu-devel@nongnu.org, virtualization@lists.linux-foundation.org, Blue Swirl , Christian Borntraeger , Paul Brook , Avi Kivity To: Mark McLoughlin Return-path: Received: from mx2.redhat.com ([66.187.237.31]:58167 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750933AbZFNJwh (ORCPT ); Sun, 14 Jun 2009 05:52:37 -0400 Content-Disposition: inline In-Reply-To: <1244825303.26769.19.camel@blaa> Sender: kvm-owner@vger.kernel.org List-ID: On Fri, Jun 12, 2009 at 05:48:23PM +0100, Mark McLoughlin wrote: > However, in order to retain compat for that SCSI device (e.g. ensuring > the PCI address doesn't change as other devices are added an removed), > we're back to the same problem ... either: > > 1) Use '-drive file=foo.img,if=scsi,pci_addr=foo'; in order to figure > out what address to use, libvirt would need to query qemu for what > address was originally allocated to device or it would do all the > PCI address allocation itself ... This last option makes sense to me: in a real world the user has control over where he places the device on the bus, so why not with qemu? -- MST