From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MGAdc-0003CK-FH for qemu-devel@nongnu.org; Mon, 15 Jun 2009 07:46:08 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MGAdX-00033p-9v for qemu-devel@nongnu.org; Mon, 15 Jun 2009 07:46:07 -0400 Received: from [199.232.76.173] (port=45012 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MGAdX-00033a-5D for qemu-devel@nongnu.org; Mon, 15 Jun 2009 07:46:03 -0400 Received: from mx2.redhat.com ([66.187.237.31]:53621) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MGAdW-0003f7-O3 for qemu-devel@nongnu.org; Mon, 15 Jun 2009 07:46:03 -0400 Message-ID: <4A3633FD.4010208@redhat.com> Date: Mon, 15 Jun 2009 14:43:57 +0300 From: Avi Kivity MIME-Version: 1.0 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> <20090614095016.GA7560@redhat.com> <1245056916.6891.31.camel@blaa> <4A3613EC.6030608@redhat.com> <87ocsp687t.fsf@pike.pond.sub.org> In-Reply-To: <87ocsp687t.fsf@pike.pond.sub.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: Configuration vs. compat hints List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Markus Armbruster Cc: Mark McLoughlin , kvm@vger.kernel.org, "Michael S. Tsirkin" , Glauber Costa , Rusty Russell , qemu-devel , virtualization@lists.linux-foundation.org, Blue Swirl , Christian Borntraeger , Paul Brook , Carsten Otte (adding cc) On 06/15/2009 02:35 PM, Markus Armbruster wrote: > Not really. QEMU gives just the host bridge a fixed slot[*]. All the > other slots are available. > qemu needs to export these two bits of information: the first free slot and the number of slots. More generally, which slots are open. We can assume 1:31, but that's unlovely. > The real problem is devices that get implicitly added, like the SCSI > controller. Those devices get their slots auto-assigned, which can > interfere with slot numbers chosen by the user. We need a way to avoid > that, as you suggested elsewhere in this thread. > Paul/Anthony, can we have -vga pci_addr=, -usb-controller pci_addr=, and -drive pci_addr= (and later, -disk-controller)? Stalling while waiting for the ultimate config file is only generating pain and out-of-tree patches. (I'd be quite happy constructing the entire machine config on the command line, but I realize it's just me) -- error compiling committee.c: too many arguments to function