From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gleb Natapov Subject: Re: [SeaBIOS] [PATCHv2] Support for booting from virtio disks Date: Tue, 11 May 2010 15:47:40 +0300 Message-ID: <20100511124740.GN2504@redhat.com> References: <20100510081118.GI24787@redhat.com> <4BE82ADA.6000302@codemonkey.ws> <4BE912FB.9030702@redhat.com> <20100511124529.GA14189@morn.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Stefan Hajnoczi , Avi Kivity , kvm@vger.kernel.org, seabios@seabios.org, qemu-devel@nongnu.org To: "Kevin O'Connor" Return-path: Received: from mx1.redhat.com ([209.132.183.28]:36783 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756447Ab0EKMr5 (ORCPT ); Tue, 11 May 2010 08:47:57 -0400 Content-Disposition: inline In-Reply-To: <20100511124529.GA14189@morn.localdomain> Sender: kvm-owner@vger.kernel.org List-ID: On Tue, May 11, 2010 at 08:45:29AM -0400, Kevin O'Connor wrote: > On Tue, May 11, 2010 at 10:04:25AM +0100, Stefan Hajnoczi wrote: > > From what I can tell SeaBIOS is reading CMOS_BIOS_BOOTFLAG1 and > > CMOS_BIOS_BOOTFLAG2 from non-volatile memory. The values index into > > bev[], which contains IPL entries (the drives). > > > > Is the order of bev[] entries well-defined? Is there a way for QEMU > > command-line to know that the first virtio-blk device corresponds to x > > and the IDE CD-ROM corresponds to y? > > SeaBIOS arranges for bev[0] = floppy, bev[1] = hd, bev[2] = cdrom, and > bev[3] to be the first network card - it does this so that the boot > order can be read from qemu. However, it's a pain to force this > order. > What if there are more then one disk? -- Gleb.