From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: qemu-kvm: Inconsistent vgabios reference Date: Sun, 15 Jan 2012 15:21:45 +0100 Message-ID: <4F12E0F9.4030008@web.de> References: <4F12B500.90705@web.de> <4F12C79E.8060902@redhat.com> <4F12C907.3070702@web.de> <4F12C9BF.7040406@redhat.com> <4F12CA17.9010604@web.de> <4F12CB51.4040502@redhat.com> <4F12CB9C.9010006@web.de> <4F12CC59.8090808@redhat.com> <4F12D056.2060605@msgid.tls.msk.ru> <4F12D226.803@redhat.com> <4F12D44B.2040208@msgid.tls.msk.ru> <4F12D72F.1060001@redhat.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigE0762E1C4AA9479F73D1EE62" Cc: Michael Tokarev , Marcelo Tosatti , kvm To: Avi Kivity Return-path: Received: from fmmailgate02.web.de ([217.72.192.227]:35490 "EHLO fmmailgate02.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752860Ab2AOOV7 (ORCPT ); Sun, 15 Jan 2012 09:21:59 -0500 Received: from moweb001.kundenserver.de (moweb001.kundenserver.de [172.19.20.114]) by fmmailgate02.web.de (Postfix) with ESMTP id CBC7C1BFC811D for ; Sun, 15 Jan 2012 15:21:46 +0100 (CET) In-Reply-To: <4F12D72F.1060001@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigE0762E1C4AA9479F73D1EE62 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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, becaus= e >>>> of lack of boot support from scsi (and no alternative), and because >>>> many people's scripts who used boot=3D broke. I thought it is bette= r >>>> 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 w= ill >>> feature virtio-scsi, though of course that doesn't help already >>> installed guests or non Windows/Linux guests. Do you know what the u= se >>> cases requiring scsi boot are? >> >> I've one (not very pleasant) bugreport handy, http://bugs.debian.org/6= 52447 >> 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. >=20 > Well we don't want to break people's guests. If the fix Gleb alluded t= o > 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 --------------enigE0762E1C4AA9479F73D1EE62 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8S4PkACgkQitSsb3rl5xTrcgCfYWUw5MXpexc9omA5HnBu6AEU ddEAoOecOn4+nrg09TeIiZiAgIQsI+4o =rtAx -----END PGP SIGNATURE----- --------------enigE0762E1C4AA9479F73D1EE62--