kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Sebastian Herbszt <herbszt@gmx.de>
Cc: Laurent Vivier <Laurent.Vivier@bull.net>,
	bochs-developers@lists.sourceforge.net, kvm@vger.kernel.org
Subject: Re: [Bochs-developers] [PATCH][BIOS] Add BCV option rom in boot menu
Date: Sun, 07 Dec 2008 10:59:54 -0600	[thread overview]
Message-ID: <493C010A.8060406@codemonkey.ws> (raw)
In-Reply-To: <2ED7D7D30FCC4E03A5A30AF6A3DF6F01@FSCPC>

Sebastian Herbszt wrote:
> Laurent Vivier wrote:
>> This patch allows to select and boot from an option ROM
>> with a Boot Connection Vector (BCV) entry.
>>
>> The BIOS detects the BCV option ROM and adds it to the IPL table, and 
>> then
>> you are able to select it to boot.
>>
>> This patch has been tested with Bochs BIOS version from the KVM 
>> source tree
>> and a gPXE ROM modified to be a BCV one.
>
> Any plans to convert extboot into a compatible option rom?

I think the plan is to replace extboot with gPXE, and load it by default 
in QEMU.  Since it supports BCV and BEV, we can rely on passing a boot 
index to choose which device to boot from.

I was thinking about what to do about SCSI boot support.  We could add 
an LSI driver to gPXE too.  That seems like a bit much though.  We could 
add a special virtio transport for gPXE and then reuse virtio-blk to 
boot from arbitrary devices.

Regards,

Anthony Liguori

  reply	other threads:[~2008-12-07 17:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-05 16:19 [PATCH][BIOS] Add BCV option rom in boot menu Laurent Vivier
2008-12-07 16:33 ` [Bochs-developers] " Sebastian Herbszt
2008-12-07 16:59   ` Anthony Liguori [this message]
2008-12-09  3:58     ` Nguyen Anh Quynh
2008-12-12  4:28     ` Michael Brown

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=493C010A.8060406@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=Laurent.Vivier@bull.net \
    --cc=bochs-developers@lists.sourceforge.net \
    --cc=herbszt@gmx.de \
    --cc=kvm@vger.kernel.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).