From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=52994 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P5Fg2-0007JJ-CG for qemu-devel@nongnu.org; Mon, 11 Oct 2010 06:32:19 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1P5Fg1-00063l-Az for qemu-devel@nongnu.org; Mon, 11 Oct 2010 06:32:18 -0400 Received: from mx1.redhat.com ([209.132.183.28]:48134) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1P5Fg1-00063d-4s for qemu-devel@nongnu.org; Mon, 11 Oct 2010 06:32:17 -0400 Message-ID: <4CB2E7D0.1010702@redhat.com> Date: Mon, 11 Oct 2010 12:32:48 +0200 From: Kevin Wolf MIME-Version: 1.0 Subject: Re: [Qemu-devel] [RFC] Passing boot order from qemu to seabios References: <20101011101855.GA25030@redhat.com> In-Reply-To: <20101011101855.GA25030@redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gleb Natapov Cc: seabios@seabios.org, qemu-devel@nongnu.org Am 11.10.2010 12:18, schrieb Gleb Natapov: > Currently if VM is started with multiple disks it is almost impossible to > guess which one of them will be used as boot device especially if there > is a mix of ATA/virtio/SCSI devices. Essentially BIOS decides the order > and without looking into the code you can't tell what the order will > be (and in qemu-kvm if boot=on is used it brings even more havoc). We > should allow fine-grained control of boot order from qemu command line, > or as a minimum control what device will be used for booting. > > To do that along with inventing syntax to specify boot order on qemu > command line we need to communicate boot order to seabios via fw_cfg > interface. For that we need to have a way to unambiguously specify a > disk from qemu to seabios. PCI bus address is not enough since not all > devices are PCI (do we care about them?) Floppy? Yes, I think we do. > and since one PCI device may > control more then one disk (ATA slave/master, SCSI LUNs). We can do what > EDD specification does. Describe disk as: > bus type (isa/pci), > address on a bus (16 bit base address for isa, b/s/f for pci) > device type (ATA/SCSI/VIRTIO) > device path (slave/master for ATA, LUN for SCSI, nothing for virtio) If we had a qdev ID for all devices (which I think we should have anyway), would this work or is a string not really handy enough? Kevin