From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:43951) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V4sdF-0008C8-Ec for qemu-devel@nongnu.org; Thu, 01 Aug 2013 09:09:35 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1V4sd9-0001Ev-F0 for qemu-devel@nongnu.org; Thu, 01 Aug 2013 09:09:29 -0400 Received: from mx1.redhat.com ([209.132.183.28]:32809) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V4sd9-0001En-7Y for qemu-devel@nongnu.org; Thu, 01 Aug 2013 09:09:23 -0400 Message-ID: <1375362537.4891.28.camel@localhost.localdomain> From: Marcel Apfelbaum Date: Thu, 01 Aug 2013 16:08:57 +0300 Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: [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: qemu-devel@nongnu.org Cc: Hu Tao , Anthony Liguori , Markus Armbruster , "Michael S. Tsirkin" 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. Now what will happen on a cluster with hundreds of such VMs? If that cluster has a health monitoring service it may show all the VMs in a "not healthy" state. My point is that a device that requires a driver that is not "inbox", should not be present by default. One possible solution is to add it manually with -device from command line. Any thoughts? Marcel