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:39:04 +0100 Message-ID: <4F12E508.9060809@web.de> References: <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> <4F12E0F9.4030008@web.de> <20120115142934.GH2167@redhat.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig40C639DADF8632ADB71D3ACE" Cc: Avi Kivity , Michael Tokarev , Marcelo Tosatti , kvm To: Gleb Natapov Return-path: Received: from fmmailgate03.web.de ([217.72.192.234]:59640 "EHLO fmmailgate03.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753171Ab2AOOjQ (ORCPT ); Sun, 15 Jan 2012 09:39:16 -0500 Received: from moweb001.kundenserver.de (moweb001.kundenserver.de [172.19.20.114]) by fmmailgate03.web.de (Postfix) with ESMTP id 43BAB1AFB3FF3 for ; Sun, 15 Jan 2012 15:39:05 +0100 (CET) In-Reply-To: <20120115142934.GH2167@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig40C639DADF8632ADB71D3ACE Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 2012-01-15 15:29, Gleb Natapov wrote: > On Sun, Jan 15, 2012 at 03:21:45PM +0100, Jan Kiszka wrote: >> 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, beca= use >>>>>> of lack of boot support from scsi (and no alternative), and becaus= e >>>>>> many people's scripts who used boot=3D broke. I thought it is bet= ter >>>>>> to let users to have a chance to perform a smoother transition tha= n >>>>>> 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 fro= m scsi, >>>> all talking about older/custom systems which worked for years in kvm= =2E >>>> As you can see in the bugreport mentioned, I know that scsi is broke= n >>>> 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. Le= t >>> us know. >> >> I would vote for proper seabios support or a free option rom. That wou= ld >> allow us to make progress with obsoleting qemu-kvm instead of making a= >> step back again. >> > It is not enough to vote, somebody has to send patches :) And it seams > there are two kind of people: those who can make such a patch, but don'= t > because they know enough to avoid qemu lsi emulation and those who can'= t > make it and use lsi qemu emulation. I'm pretty sure there is also a set of people who need to use LSI and can write the proper support. Jan --------------enig40C639DADF8632ADB71D3ACE 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/ iEYEARECAAYFAk8S5QgACgkQitSsb3rl5xRcQQCeJ85sXlA/nE47wcZGkSxW2Mbk rA8AoNF33AkXfqqwnuJFyT5I/fl8SiGQ =oq/T -----END PGP SIGNATURE----- --------------enig40C639DADF8632ADB71D3ACE--