From: Jan Kiszka <jan.kiszka@siemens.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: libvir-list@redhat.com, "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [PATCH 0/2] port over extboot from kvm
Date: Tue, 08 Sep 2009 16:40:15 +0200 [thread overview]
Message-ID: <4AA66CCF.3040302@siemens.com> (raw)
In-Reply-To: <4AA668A2.1080801@redhat.com>
Gerd Hoffmann wrote:
> On 09/08/09 15:47, Jan Kiszka wrote:
>
>> Before setting this definitely useful feature in stone, I have two
>> questions though:
>>
>> - -drive ...,boot=on is logically in conflict with -boot. Yes, -boot
>> for x86 currently cannot differentiate between multiple disks, only
>> between boot media types. Still, this two-stage configuration is
>> rather unintuitive and looks like a patchwork. Given that we have
>> full control over all components, is it really the preferred
>> approach? I already thought about, e.g., -boot c2 to select the
>> second disk. Not that nice, but I would rather vote for a consistent
>> configuration than a scattered one.
>
> Disk numbers are bad. Define "second hard disk". Especially for a
> system with different kinds of disks (say one scsi and one virtio).
One could use the specification order, but I agree it's not very handy.
>
> Drives have names though which can be used to reference the disks, so we
> could use that instead. -boot cmd line syntax becomes a bit tricky then
> though, we somehow have to figure whenever the user gave us names or
> old-style letters. Something like this ...
>
> -drive if=virtio,id=sys,file=/path/to/disk.img
> -cdrom /path/to/install.iso
> -boot order=[sys],once=d,menu=off
Yes, this looks powerful and clean. One could even still define probe
orders like "-boot order=[sys][backup]d".
>
> ... might work out nicely. I suspect the libvirt folks will hate us for
> that though.
Does anyone from libvirt want to comment on this?
>
>> - 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.
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2009-09-08 14:42 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 [this message]
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=4AA66CCF.3040302@siemens.com \
--to=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).