All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Avi Kivity <avi@redhat.com>
Cc: Michael Tokarev <mjt@tls.msk.ru>,
	Marcelo Tosatti <mtosatti@redhat.com>, kvm <kvm@vger.kernel.org>
Subject: Re: qemu-kvm: Inconsistent vgabios reference
Date: Sun, 15 Jan 2012 15:21:45 +0100	[thread overview]
Message-ID: <4F12E0F9.4030008@web.de> (raw)
In-Reply-To: <4F12D72F.1060001@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1527 bytes --]

On 2012-01-15 14:39, Avi Kivity wrote:
> On 01/15/2012 03:27 PM, Michael Tokarev wrote:
>> On 15.01.2012 17:18, Avi Kivity wrote:
>>> On 01/15/2012 03:10 PM, Michael Tokarev wrote:
>> []
>>>> 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?
>>
>> I've one (not very pleasant) bugreport handy, http://bugs.debian.org/652447
>> and a few private messages asking me for ways to restore booting from scsi,
>> all talking about older/custom systems which worked for years in kvm.
>> As you can see in the bugreport mentioned, I know that scsi is broken
>> and should not be used and so on, and suggested switching from it on
>> every chance.
> 
> Well we don't want to break people's guests.  If the fix Gleb alluded to
> doesn't work, we'll have to restore extboot or something similar.  Let
> us know.

I would vote for proper seabios support or a free option rom. That would
allow us to make progress with obsoleting qemu-kvm instead of making a
step back again.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

  reply	other threads:[~2012-01-15 14:21 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
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 [this message]
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=4F12E0F9.4030008@web.de \
    --to=jan.kiszka@web.de \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mjt@tls.msk.ru \
    --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.