From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:36026) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V4viS-0000rf-LD for qemu-devel@nongnu.org; Thu, 01 Aug 2013 12:27:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1V4viM-0005XH-Eg for qemu-devel@nongnu.org; Thu, 01 Aug 2013 12:27:04 -0400 Received: from mx1.redhat.com ([209.132.183.28]:31638) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V4viL-0005X7-VI for qemu-devel@nongnu.org; Thu, 01 Aug 2013 12:26:58 -0400 Message-ID: <51FA8C4D.70308@redhat.com> Date: Thu, 01 Aug 2013 10:26:53 -0600 From: Eric Blake MIME-Version: 1.0 References: <1375362537.4891.28.camel@localhost.localdomain> <51FA6E34.5000404@redhat.com> In-Reply-To: <51FA6E34.5000404@redhat.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="IqgO8k0x4xwLlub9hP95vh7CXSvPojQbX" Subject: Re: [Qemu-devel] pvpanic device should not be automatically included as an internal device List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gerd Hoffmann Cc: Anthony Liguori , "Michael S. Tsirkin" , "libvir-list@redhat.com" , Hu Tao , Marcel Apfelbaum , qemu-devel@nongnu.org, Markus Armbruster This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --IqgO8k0x4xwLlub9hP95vh7CXSvPojQbX Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 08/01/2013 08:18 AM, Gerd Hoffmann wrote: > On 08/01/13 15:08, Marcel Apfelbaum wrote: >> Hi, >> >> The problem with pvpanic being an internal device is that VMs running >> operating systems without a driver for this device will have problems >> when qemu will be upgraded (from qemu without this pvpanic). >> >> The outcome may be, for example: in Windows(let's say XP) the Device m= anager >> will open a "new device" wizard and the device will appear as an unrec= ognized device. >=20 > Only happens when also changing the machine type on upgrade as it is > turned off on old machine types. >=20 > But, yes, pvpanic will show up as "Unknown device" without driver and > with the funky yellow exclamation mark in device manager in windows > guests. Newer windows versions don't kick the "new device" wizard. Bu= t > still I have my doubts that it is a good idea to add it unconditionally= ... Automatic devices with no command line argument have proven to be a nightmare for libvirt as well. Although the just-released libvirt 1.1.1 now supports the element for controlling the command line parameters of qemu related to how qemu will behave when the pvpanic device is triggered, I would also welcome having the ability to control whether the guest even has a pvpanic device exposed, just as we can control whether a guest has a memballoon device exposed. --=20 Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org --IqgO8k0x4xwLlub9hP95vh7CXSvPojQbX Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (GNU/Linux) Comment: Public key at http://people.redhat.com/eblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJR+oxNAAoJEKeha0olJ0Nq+V0H/1cFvphnveernFRzPvT7SInM h3R/edvrqFB9FIE3P/vKdZ67k7GrAZM4aalD6ZX7n9MJmWwwkt77QOiig5rD0rFK W6baOJvLK+XwF112iVUUPi0xJTs+2gTXN5jKwxD5QricL1Ls8FSeQJtzhX4ub04N ouGglnNyVrB71WyMGYFGUSYsY15h2uQF+/hI9HB/AKQVtqy70jhsV1rNRDiMIEdG 2potRbEdSxiWeD7Fqx2BJTblQ0+trn2xN76SW3v7xG31U6msN6EiIejo54xt0nHj rl0iDgdFe8tftPBqrRywm1x374nuxD58n1SFCKbPO4UpK9N5BoEX0T1h70DefuU= =7Ub2 -----END PGP SIGNATURE----- --IqgO8k0x4xwLlub9hP95vh7CXSvPojQbX--