From: Kevin O'Connor <kevin@koconnor.net>
To: Gleb Natapov <gleb@redhat.com>
Cc: Gerhard Wiesinger <lists@wiesinger.com>,
Gerd Hoffmann <kraxel@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Boot order problem and disable iPXE/gPXE
Date: Fri, 6 Jan 2012 20:53:02 -0500 [thread overview]
Message-ID: <20120107015302.GA10181@morn.localdomain> (raw)
In-Reply-To: <20120106052725.GA3105@redhat.com>
On Fri, Jan 06, 2012 at 07:27:25AM +0200, Gleb Natapov wrote:
> On Thu, Jan 05, 2012 at 09:05:39PM -0500, Kevin O'Connor wrote:
> > SeaBIOS could probably fall back to the harddrive priority if it finds
> > a BCV without an explicit bootindex priority.
> The same option rom probably will register bcv for SCSI CD/DVD too. Also
> are you sure pxe roms do not register bcv for network booting?
BCV is just for drives - network cards would use a BEV. The BBS spec
isn't clear on whether BCV is just for harddrives (as opposed to
floppy/cd), but it seems to imply that.
I'm not sure what a SCSI rom would do with a CD drive. My guess is
that it wouldn't map it to a BIOS visible drive id at all, as there's
no way to select an id with any assurance that it wont conflict with
one chosen by the BIOS or another rom. If QEMU can simulate this (and
someone knows the command-line to do such) it would be an interesting
test to see what the rom does.
-Kevin
next prev parent reply other threads:[~2012-01-07 1:53 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 18:02 [Qemu-devel] Boot order problem and disable iPXE/gPXE Gerhard Wiesinger
2012-01-05 3:03 ` Kevin O'Connor
2012-01-05 7:39 ` Gerhard Wiesinger
2012-01-06 1:42 ` Kevin O'Connor
2012-01-06 8:20 ` Gerhard Wiesinger
2012-01-06 8:59 ` Gerd Hoffmann
2012-01-05 7:50 ` Gleb Natapov
2012-01-05 7:58 ` Gerd Hoffmann
2012-01-05 8:23 ` Gerhard Wiesinger
2012-01-05 8:32 ` Gleb Natapov
2012-01-05 9:09 ` Gerhard Wiesinger
2012-01-05 9:20 ` Gleb Natapov
2012-01-05 9:27 ` Gerhard Wiesinger
2012-01-05 9:29 ` Gleb Natapov
2012-01-05 9:36 ` Gerhard Wiesinger
2012-01-05 9:42 ` Gleb Natapov
2012-01-05 9:56 ` Gerhard Wiesinger
2012-01-05 10:00 ` Gleb Natapov
2012-01-05 9:42 ` Gerd Hoffmann
2012-01-06 2:05 ` Kevin O'Connor
2012-01-06 5:27 ` Gleb Natapov
2012-01-07 1:53 ` Kevin O'Connor [this message]
2012-01-07 9:00 ` Gerhard Wiesinger
2012-01-07 16:28 ` Kevin O'Connor
2012-01-07 22:47 ` Gerhard Wiesinger
2012-01-07 22:53 ` Kevin O'Connor
2012-01-08 8:31 ` Gleb Natapov
2012-01-08 14:58 ` Kevin O'Connor
2012-01-08 15:17 ` Gleb Natapov
2012-01-08 15:47 ` Kevin O'Connor
2012-01-25 20:30 ` Gerhard Wiesinger
2012-01-09 9:10 ` Gerd Hoffmann
2012-01-07 8:35 ` Gerhard Wiesinger
2012-01-07 16:20 ` Kevin O'Connor
2012-01-07 22:46 ` Gerhard Wiesinger
2012-01-07 22:59 ` Gerhard Wiesinger
2012-01-08 11:59 ` Gerhard Wiesinger
2012-01-05 8:57 ` Gerd Hoffmann
2012-01-05 9:24 ` Gerhard Wiesinger
2012-01-05 9:53 ` Gerd Hoffmann
2012-01-05 10:08 ` Gerhard Wiesinger
2012-01-05 10:13 ` Gerd Hoffmann
2012-01-05 11:13 ` Gerhard Wiesinger
2012-01-05 11:16 ` Gleb Natapov
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=20120107015302.GA10181@morn.localdomain \
--to=kevin@koconnor.net \
--cc=gleb@redhat.com \
--cc=kraxel@redhat.com \
--cc=lists@wiesinger.com \
--cc=qemu-devel@nongnu.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).