Re: qemu-kvm: Inconsistent vgabios reference

[Avi Kivity <avi@redhat.com>]

On 01/15/2012 03:10 PM, Michael Tokarev wrote:
> On 15.01.2012 16:53, Avi Kivity wrote:
> > On 01/15/2012 02:50 PM, Jan Kiszka wrote:
> []
> >> extboot is history since 2a06024dc1b1e27b1be0266379af397e61b4a9ad
> > 
> > Yeah, but it isn't history for people running older qemu-kvm's.  We
> > don't need extboot itself, but we do need to keep the boot option (as
> > 2a06 does).  The question is do we need to preserve its meaning too
> > (with the seabios implementation instead of extboot's).
>
> FWIW, I had to patch extboot back in for debian qemu-kvm 1.0, because
> of lack of boot support from scsi (and no alternative), and because
> many people's scripts who used boot= broke.  I thought it is better
> to let users to have a chance to perform a smoother transition than
> to break their stuff.

It's really sad that people have to use lsi scsi.  Luckily qemu 1.1 will
feature virtio-scsi, though of course that doesn't help already
installed guests or non Windows/Linux guests.  Do you know what the use
cases requiring scsi boot are?

> Now, I've a question: what seabios implementation of extboot we're
> talking about?  -option-rom which is impossible to select as a first
> boot device?

seabios has native support for booting from virtio-blk, and will
natively support virtio-scsi as well.

-- 
error compiling committee.c: too many arguments to function