From: Anthony Liguori <anthony@codemonkey.ws>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: "libvir-list@redhat.com" <libvir-list@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Re: [PATCH 0/2] port over extboot from kvm
Date: Tue, 08 Sep 2009 12:12:53 -0500 [thread overview]
Message-ID: <4AA69095.5070200@codemonkey.ws> (raw)
In-Reply-To: <4AA6831F.6070501@siemens.com>
Jan Kiszka wrote:
>>>>> - This is just an implementation detail: Do we really need to implement
>>>>> booting from virtio and scsi via an extension rom? Isn't it possible
>>>>> to merge the corresponding support into the main bios?
>>>>>
>>>> Well. There are quite a few. bochs pcbios, seabios, coreboot ...
>>>>
>>> Ok, but that's only an argument to have extboot as a workaround for
>>> bioses not yet supporting scsi and virtio natively, isn't it? I'm
>>> thinking long-term here, not arguing against a extboot-based short-term
>>> solution.
>>>
>> I think it would be useful. Adding a fw_cfg knob to signal 'please boot
>> via extboot protocol instead of ide disk' should be enougth to allow
>> bioses supporting extboot directly. Additional plus is we can probably
>> code it in C not asm then.
>>
>
> I'm still not convinced we need extboot for all bioses on the long term.
> And I think we should define new interfaces in a way that finally makes
> it obsolete, at least for our "home bios" (whatever it will be).
>
What we won't need long term is the extboot interface (hw/extboot.c).
Ideally, we would rewrite the extboot option rom to have a proper
virtio-blk driver in it. Better yet, to finish up Laurent's work of
adding virtio-blk support to gpxe since it gives us bcv for free. We
woudl then support booting from multiple disks by specifying the bcv
entry index in cmos.
Then we would need a new syntax for boot (like -boot c3 to chose the 3rd
disk device).
Regards,
Anthony Liguori
> Jan
>
>
next prev parent reply other threads:[~2009-09-08 17:13 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
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 [this message]
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=4AA69095.5070200@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=jan.kiszka@siemens.com \
--cc=kraxel@redhat.com \
--cc=libvir-list@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).