From: Kevin O'Connor <kevin@koconnor.net>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org, seabios@seabios.org,
Gleb Natapov <gleb@redhat.com>,
qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCHv2] Support for booting from virtio disks
Date: Wed, 12 May 2010 08:57:57 -0400 [thread overview]
Message-ID: <20100512125757.GA26049@morn.localdomain> (raw)
In-Reply-To: <4BEA5753.1050508@redhat.com>
On Wed, May 12, 2010 at 10:22:59AM +0300, Avi Kivity wrote:
> On 05/11/2010 03:31 PM, Gleb Natapov wrote:
> >Real BIOS can do that because it enumerates all bootable devices,
> >attach name for each one of them and then asks user to configure
> >boot order using names it attached to devices. In our case we
> >want to provide boot order on qemu command line before BIOS
> >enumerated devices, so qemu should be able to pass enough information
> >about boot device so that BIOS can uniquely identify it after it will
> >discover all bootable devices. bus/device pair can be such thing.
>
> Having a BIOS menu is also useful, you don't have to drop to the
> management tool, instead you do everything from the console.
Having a "setup menu" is something real hardware could use as well. I
don't think the setup menu should be in SeaBIOS - instead, SeaBIOS
could launch another program (stored in flash or qemu_fw) dedicated to
doing setup.
> >>Alternatively we can seed the order from the command line (-boot
> >>id1,id2,id3 where id* are some qdev property attached to disks, this
> >>is more flexible than the current syntax I think).
> >>
> >The problem is how to communicate this order to Seabios.
>
> Topology (bus/device/lun).
USB is a pain here. It's posible with BDF (Bus/Dev/Fn) and port
number (which accounts for hubs having ports as well).
-Kevin
prev parent reply other threads:[~2010-05-12 12:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-10 8:11 [Qemu-devel] [PATCHv2] Support for booting from virtio disks Gleb Natapov
2010-05-10 8:25 ` [Qemu-devel] " Stefan Hajnoczi
2010-05-10 8:29 ` Gleb Natapov
2010-05-10 15:48 ` Anthony Liguori
2010-05-10 15:54 ` Gleb Natapov
2010-05-10 15:58 ` Anthony Liguori
2010-05-10 16:09 ` Gleb Natapov
2010-05-13 16:49 ` [Qemu-devel] Re: [SeaBIOS] " Avi Kivity
2010-05-16 8:28 ` Gleb Natapov
2010-05-11 8:19 ` [Qemu-devel] " Avi Kivity
2010-05-11 9:04 ` Stefan Hajnoczi
2010-05-11 12:33 ` Gleb Natapov
2010-05-11 12:45 ` [Qemu-devel] Re: [SeaBIOS] " Kevin O'Connor
2010-05-11 12:47 ` Gleb Natapov
2010-05-12 0:44 ` Kevin O'Connor
2010-05-11 12:31 ` [Qemu-devel] " Gleb Natapov
2010-05-12 7:22 ` Avi Kivity
2010-05-12 7:55 ` Gleb Natapov
2010-05-12 12:57 ` Kevin O'Connor [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100512125757.GA26049@morn.localdomain \
--to=kevin@koconnor.net \
--cc=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=seabios@seabios.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).