From: Gleb Natapov <gleb@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Kevin Wolf <kwolf@redhat.com>,
seabios@seabios.org, Gerd Hoffmann <kraxel@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [SeaBIOS] [Qemu-devel] [RFC] Passing boot order from qemu to seabios
Date: Mon, 11 Oct 2010 22:36:53 +0200 [thread overview]
Message-ID: <20101011203653.GC5218@redhat.com> (raw)
In-Reply-To: <4CB373DD.50307@codemonkey.ws>
On Mon, Oct 11, 2010 at 03:30:21PM -0500, Anthony Liguori wrote:
> On 10/11/2010 02:59 PM, Gleb Natapov wrote:
> >No boot rom should do that. extboot wreaks havoc when it is used.
> >And since virtio is now supported by bios there is no reason to use it.
>
> You don't really have a choice. You could be doing hardware
> passthrough and the ROM on the card may hijack int19.
>
Then this particular HW would be broken on real HW too and will not
respect BIOS settings. But the code we provide should work properly.
> >Whoever needs scsi boot should add it to seabios too.
>
> I don't disagree.
>
> I think the best thing to do is to let SeaBIOS create a boot order
> table that contains descriptive information and then advertise that
> to QEMU.
>
What for? Why this step is needed?
> QEMU can then try to associate the list of bootable devices with
> it's own set of devices and select a preferred order that it can
> then give back to SeaBIOS. SeaBIOS can then present that list to
> the user for additional refinement.
>
Why not skip your first step and let QEMU create boot order list and
pass it into Seabios. If menu=on option is present user will be able to
override the default from Seabios.
--
Gleb.
next prev parent reply other threads:[~2010-10-11 20:36 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-11 10:18 [Qemu-devel] [RFC] Passing boot order from qemu to seabios Gleb Natapov
2010-10-11 10:32 ` Kevin Wolf
2010-10-11 10:43 ` Gleb Natapov
2010-10-11 11:01 ` Kevin Wolf
2010-10-11 12:07 ` Gerd Hoffmann
2010-10-11 12:16 ` Gleb Natapov
2010-10-11 19:48 ` [SeaBIOS] " Anthony Liguori
2010-10-11 19:59 ` Gleb Natapov
2010-10-11 20:30 ` Anthony Liguori
2010-10-11 20:36 ` Gleb Natapov [this message]
2010-10-11 20:50 ` Anthony Liguori
2010-10-11 21:14 ` Gleb Natapov
2010-10-11 21:15 ` H. Peter Anvin
2010-10-11 21:41 ` Sebastian Herbszt
2010-10-11 21:51 ` H. Peter Anvin
2010-10-12 8:01 ` Gleb Natapov
2010-10-12 16:33 ` H. Peter Anvin
2010-10-12 16:56 ` Gleb Natapov
2010-10-12 17:35 ` H. Peter Anvin
2010-10-12 17:41 ` Gleb Natapov
2010-10-12 17:45 ` H. Peter Anvin
2010-10-12 19:06 ` Gleb Natapov
2010-10-13 19:17 ` H. Peter Anvin
2010-10-13 20:00 ` H. Peter Anvin
2010-10-13 20:22 ` H. Peter Anvin
2010-10-11 19:51 ` Anthony Liguori
2010-10-11 20:02 ` Gleb Natapov
2010-10-11 20:18 ` [SeaBIOS] " H. Peter Anvin
2010-10-11 11:16 ` Bernhard Kohl
2010-10-11 12:08 ` Gleb Natapov
2010-10-11 23:33 ` [SeaBIOS] " Kevin O'Connor
2010-10-11 12:48 ` Stefan Hajnoczi
2010-10-11 14:29 ` Gleb Natapov
2010-10-11 15:52 ` Stefan Hajnoczi
2010-10-11 16:04 ` Gleb Natapov
2010-10-11 17:01 ` Anthony Liguori
2010-10-11 17:04 ` Gleb Natapov
2010-10-11 23:16 ` [SeaBIOS] " Kevin O'Connor
2010-10-12 8:44 ` Stefan Hajnoczi
2010-10-11 15:09 ` [Qemu-devel] Re: [SeaBIOS] " Avi Kivity
2010-10-11 15:39 ` Gleb Natapov
2010-10-11 15:42 ` Avi Kivity
2010-10-11 15:52 ` Gleb Natapov
2010-10-12 0:08 ` Kevin O'Connor
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=20101011203653.GC5218@redhat.com \
--to=gleb@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=kraxel@redhat.com \
--cc=kwolf@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.