From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:39088) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V51Zg-0007JJ-Rb for qemu-devel@nongnu.org; Thu, 01 Aug 2013 18:42:29 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1V51Zb-0007Nn-48 for qemu-devel@nongnu.org; Thu, 01 Aug 2013 18:42:24 -0400 Received: from mx1.redhat.com ([209.132.183.28]:23996) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V51Za-0007NU-RG for qemu-devel@nongnu.org; Thu, 01 Aug 2013 18:42:19 -0400 Message-ID: <51FAE445.3020607@redhat.com> Date: Thu, 01 Aug 2013 16:42:13 -0600 From: Eric Blake MIME-Version: 1.0 References: <1375362537.4891.28.camel@localhost.localdomain> <51FA6E34.5000404@redhat.com> <51FA8C4D.70308@redhat.com> <51FADFEB.1080804@redhat.com> In-Reply-To: <51FADFEB.1080804@redhat.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="SVOplFOGRcNKEduGoIdkivUtwp3c9IgAk" 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: Paolo Bonzini Cc: aliguori@us.ibm.com, marcel.a@redhat.com, libvir-list@redhat.com, hutao@cn.fujitsu.com, mst@redhat.com, qemu-devel@nongnu.org, kraxel@redhat.com This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --SVOplFOGRcNKEduGoIdkivUtwp3c9IgAk Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 08/01/2013 04:23 PM, Paolo Bonzini wrote: >> Automatic devices with no command line argument have proven to be a >> nightmare for libvirt as well. Although the just-released libvirt 1.1= =2E1 >> 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 contro= l >> whether the guest even has a pvpanic device exposed, just as we can >> control whether a guest has a memballoon device exposed. >=20 > This is quite different from memballoon. >=20 > pvpanic is a single I/O port, it doesn't use up a PCI slot (thus > causing conflicts with other devices at the same address). >=20 > Perhaps this issue is simply fixed by making the _STA method > return 0x0B instead of 0x0F (i.e. turning off the "show in user > interface" bit). That may "fix" the issue of a windows guest showing the yellow ! mark, but what if, down the road, someone writes an actual windows driver that is aware of that port and how to make a windows BSOD write a panic notification to the port? How does a user go about installing such a driver if the device is not exposed in the user interface list of devices= ? --=20 Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org --SVOplFOGRcNKEduGoIdkivUtwp3c9IgAk 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+uRFAAoJEKeha0olJ0NqwAIH/jC/yjmx9Vrzmw2I8ly/EoIi oJiTcTI0ns06SrLDvwvNNi3EMhP6YN4DKJu5Y3+rdZfZiiam9C8R+nNVdK9gSICG qClRyrgl7SFTt44jSyJgO+akd4zjEKLUm9G2+HMwLNCcDhID86GbH1EQUF9D62nN VGLuT89czg7DxRjnxk3S7KP34iOVbIogVNNB+fnflcJaUCQf2WbJn5fOxDxRJZIY Wk0sWvpWnJ+Jrm5coGZHClRQQWGmeRGIKqJ8muTLs/Y7f+zr4icn8q7w05kKjJwd HBwz/9ccM3o6QdI4mLJWSgYZ7OH6/1st5vVYXs5PymGZT6WqoRkoOnXFh7ez+GU= =bHCn -----END PGP SIGNATURE----- --SVOplFOGRcNKEduGoIdkivUtwp3c9IgAk--