From: Kevin O'Connor <kevin@koconnor.net>
To: "H. Peter Anvin" <hpa@linux.intel.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Anthony Liguori <anthony@codemonkey.ws>,
Avi Kivity <avi@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>, kvm <kvm@vger.kernel.org>,
Stefan Hajnoczi <stefan.hajnoczi@uk.ibm.com>
Subject: Re: [PATCH 1/2] qemu-kvm: extboot: Keep variables in RAM
Date: Fri, 19 Feb 2010 22:21:45 -0500 [thread overview]
Message-ID: <20100220032145.GA439@morn.localdomain> (raw)
In-Reply-To: <4B7EE860.80103@linux.intel.com>
On Fri, Feb 19, 2010 at 11:37:04AM -0800, H. Peter Anvin wrote:
> On 02/19/2010 10:17 AM, Jan Kiszka wrote:
> >>
> >> Stefan posted a virtio-blk driver for gPXE. I like this approach
> >> because it's generally useful (gPXE can be used with any BIOS).
> >
> > Does it allow a unified boot device selection, one menu for them all, no
> > more "boot=on" workarounds?
> >
>
> Well, it hooks into BBS if the underlying BIOS supports it. Without BBS
> there is no ability to have a unified boot device selection.
SeaBIOS does support BBS (both BEVs and BCVs). Also, under qemu,
SeaBIOS will run option roms with memory writable and then lock the
memory after the POST phase (as is required by the spec).
SeaBIOS also support PMM (both temporary allocations and the PCIv3
extensions for permanent memory).
Finally, I plan to commit a series of patches to SeaBIOS which add
support for booting from USB drives. I imagine adding virtio support
to SeaBIOS would not be difficult if someone wishes to take that on.
-Kevin
next prev parent reply other threads:[~2010-02-20 3:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-18 16:13 [PATCH 1/2] qemu-kvm: extboot: Keep variables in RAM Jan Kiszka
2010-02-18 20:27 ` Anthony Liguori
2010-02-18 22:56 ` H. Peter Anvin
2010-02-19 10:06 ` Jan Kiszka
2010-02-19 16:50 ` H. Peter Anvin
2010-02-19 17:03 ` Jan Kiszka
2010-02-19 17:24 ` H. Peter Anvin
2010-02-19 17:44 ` Jan Kiszka
2010-02-19 18:10 ` Anthony Liguori
2010-02-19 18:17 ` Jan Kiszka
2010-02-19 19:37 ` H. Peter Anvin
2010-02-20 3:21 ` Kevin O'Connor [this message]
2010-02-22 10:03 ` Stefan Hajnoczi
[not found] ` <4B82DE3F.5090306@linux.intel.com>
2010-02-23 9:30 ` Stefan Hajnoczi
2010-02-22 9:40 ` Avi Kivity
2010-02-22 9:59 ` Jan Kiszka
2010-02-22 10:03 ` Jan Kiszka
2010-02-22 11:02 ` Avi Kivity
2010-04-06 8:50 ` Jan Kiszka
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=20100220032145.GA439@morn.localdomain \
--to=kevin@koconnor.net \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=hpa@linux.intel.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=stefan.hajnoczi@uk.ibm.com \
/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