From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:52701) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V4vET-0006bF-KT for qemu-devel@nongnu.org; Thu, 01 Aug 2013 11:56:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1V4vEM-0003B8-T7 for qemu-devel@nongnu.org; Thu, 01 Aug 2013 11:56:05 -0400 Received: from mx1.redhat.com ([209.132.183.28]:43635) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V4ti7-00022R-7R for qemu-devel@nongnu.org; Thu, 01 Aug 2013 10:18:35 -0400 Message-ID: <51FA6E34.5000404@redhat.com> Date: Thu, 01 Aug 2013 16:18:28 +0200 From: Gerd Hoffmann MIME-Version: 1.0 References: <1375362537.4891.28.camel@localhost.localdomain> In-Reply-To: <1375362537.4891.28.camel@localhost.localdomain> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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: Marcel Apfelbaum Cc: Hu Tao , Anthony Liguori , "Michael S. Tsirkin" , qemu-devel@nongnu.org, Markus Armbruster 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 manager > will open a "new device" wizard and the device will appear as an unrecognized device. Only happens when also changing the machine type on upgrade as it is turned off on old machine types. 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. But still I have my doubts that it is a good idea to add it unconditionally ... cheers, Gerd