From: Kevin O'Connor <kevin@koconnor.net>
To: Avi Kivity <avi@redhat.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Gerd Hoffmann <kraxel@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH 0/2] port over extboot from kvm
Date: Sat, 12 Sep 2009 11:03:00 -0400 [thread overview]
Message-ID: <20090912150300.GA31077@morn.localdomain> (raw)
In-Reply-To: <4AA680BB.5020201@redhat.com>
On Tue, Sep 08, 2009 at 07:05:15PM +0300, Avi Kivity wrote:
> On 09/08/2009 05:32 PM, Anthony Liguori wrote:
>> x86 boot is strange. The BIOS boots from the "first hard disk" What
>> extboot allows you do to is redefine to the bios what constitutes the
>> "first hard disk".
>
> It's not just booting - it's the int 0x13 interface. Grub for example
> continues to use it and can boot from the second hard disk if desired.
Some time back, I tried implementing booting from the second hard
drive by passing 0x81 in "dl" during the boot. All the boot loaders I
tested failed to work. I think grub may have worked if I
re-configured it, but I figured it wasn't worth it due to the
confusion it would cause.
So, the experience suggested to me that bootloaders today still
require the boot harddrive to be mapped to 0x80. (Though,
interestingly, cdrom booting is okay with any drive id..)
>> For instance, it would not be possible to define a boot sequence of
>> "first virtio disk, then second virtio disk, then cdrom" because we
>> can't present two disks as the first hard disk.
>>
>> If extboot supported BCV and our bios did, the above would be possible.
FWIW, SeaBIOS does support BCVs. SeaBIOS will find all the drives and
present them on the boot menu - the user can then select which drive
to boot from (either floppy, any number of cdroms, any of the builtin
or external "BCV" hard drives). For floppy and hard drive booting the
selection is implemented by manipulating the drive mappings.
Also, as an aside, it seams likely that USB booting will be added to
SeaBIOS (either directly or as an option rom). I'm not sure if this
has any overlap with extboot.
-Kevin
next prev parent reply other threads:[~2009-09-12 15:03 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-08 9:17 [Qemu-devel] [PATCH 0/2] port over extboot from kvm Gerd Hoffmann
2009-09-08 9:17 ` [Qemu-devel] [PATCH 1/2] extboot: add option rom Gerd Hoffmann
2009-09-08 9:17 ` [Qemu-devel] [PATCH 2/2] extboot: qemu code Gerd Hoffmann
2009-09-08 11:59 ` [Qemu-devel] [PATCH 0/2] port over extboot from kvm Gerd Hoffmann
2009-09-08 13:47 ` [Qemu-devel] " Jan Kiszka
2009-09-08 14:22 ` Gerd Hoffmann
2009-09-08 14:32 ` Anthony Liguori
2009-09-08 16:05 ` Avi Kivity
2009-09-08 17:21 ` Anthony Liguori
2009-09-08 19:11 ` Avi Kivity
2009-09-08 19:46 ` Anthony Liguori
2009-09-08 20:00 ` Avi Kivity
2009-09-08 20:10 ` Anthony Liguori
2009-09-12 15:03 ` Kevin O'Connor [this message]
2009-09-08 14:40 ` Jan Kiszka
2009-09-08 14:52 ` Gerd Hoffmann
2009-09-08 16:15 ` Jan Kiszka
2009-09-08 17:12 ` Anthony Liguori
2009-09-08 19:03 ` Gerd Hoffmann
2009-09-08 19:39 ` Anthony Liguori
2009-09-12 15:43 ` Kevin O'Connor
2009-09-08 14:16 ` [Qemu-devel] " Anthony Liguori
2009-11-09 16:06 ` Paul Brook
2009-11-09 16:31 ` Gerd Hoffmann
2009-11-09 16:40 ` Anthony Liguori
2009-11-11 13:01 ` Hannes Reinecke
2009-11-11 13:25 ` Anthony Liguori
2009-11-11 13:54 ` Paul Brook
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=20090912150300.GA31077@morn.localdomain \
--to=kevin@koconnor.net \
--cc=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kraxel@redhat.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).