From: Michael Tokarev <mjt@tls.msk.ru>
To: Avi Kivity <avi@redhat.com>
Cc: Jan Kiszka <jan.kiszka@web.de>,
Marcelo Tosatti <mtosatti@redhat.com>, kvm <kvm@vger.kernel.org>
Subject: Re: qemu-kvm: Inconsistent vgabios reference
Date: Sun, 15 Jan 2012 17:10:46 +0400 [thread overview]
Message-ID: <4F12D056.2060605@msgid.tls.msk.ru> (raw)
In-Reply-To: <4F12CC59.8090808@redhat.com>
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.
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?
Thanks,
/mjt
next prev parent reply other threads:[~2012-01-15 13:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-15 11:14 qemu-kvm: Inconsistent vgabios reference Jan Kiszka
2012-01-15 12:33 ` Avi Kivity
2012-01-15 12:39 ` Jan Kiszka
2012-01-15 12:42 ` Avi Kivity
2012-01-15 12:44 ` Jan Kiszka
2012-01-15 12:49 ` Avi Kivity
2012-01-15 12:50 ` Jan Kiszka
2012-01-15 12:53 ` Avi Kivity
2012-01-15 12:55 ` Jan Kiszka
2012-01-15 13:02 ` Avi Kivity
2012-01-15 13:10 ` Michael Tokarev [this message]
2012-01-15 13:18 ` Avi Kivity
2012-01-15 13:27 ` Michael Tokarev
2012-01-15 13:36 ` Gleb Natapov
2012-01-15 13:39 ` Avi Kivity
2012-01-15 14:21 ` Jan Kiszka
2012-01-15 14:29 ` Gleb Natapov
2012-01-15 14:39 ` Jan Kiszka
2012-01-16 8:15 ` Gerd Hoffmann
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=4F12D056.2060605@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=avi@redhat.com \
--cc=jan.kiszka@web.de \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.