From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:39669) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Takgd-0003bz-MU for qemu-devel@nongnu.org; Tue, 20 Nov 2012 05:04:17 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Takgc-0001JZ-F5 for qemu-devel@nongnu.org; Tue, 20 Nov 2012 05:04:11 -0500 Received: from mx1.redhat.com ([209.132.183.28]:3257) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Takgc-0001IG-7l for qemu-devel@nongnu.org; Tue, 20 Nov 2012 05:04:10 -0500 Received: from int-mx12.intmail.prod.int.phx2.redhat.com (int-mx12.intmail.prod.int.phx2.redhat.com [10.5.11.25]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id qAKA48rd032253 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 20 Nov 2012 05:04:09 -0500 Message-ID: <1353404100.2180.39.camel@fatty> From: Alexander Larsson Date: Tue, 20 Nov 2012 10:35:00 +0100 In-Reply-To: <50AB4A2B.7060001@redhat.com> References: <1353330711-20207-1-git-send-email-alexl@redhat.com> <50AB3631.2080000@redhat.com> <20121120090736.GA3461@redhat.com> <50AB4A2B.7060001@redhat.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] qxl: Export "mode" as a property List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gerd Hoffmann Cc: Alon Levy , qemu-devel@nongnu.org On tis, 2012-11-20 at 10:15 +0100, Gerd Hoffmann wrote: > On 11/20/12 10:07, Daniel P. Berrange wrote: > > On Tue, Nov 20, 2012 at 08:50:09AM +0100, Gerd Hoffmann wrote: > >> On 11/19/12 14:11, Alexander Larsson wrote: > >>> This way you can easily tell from qemu if the guest is using > >>> a qxl driver or not. > >> > >> Device properties are for configuration, not inspection. > > > > Sounds like we need to expose something via the monitor to let admin > > apps discover if QXL has been enabled with SPICE vs plain VGA compat > > mode only. This is useful for apps to know, so that they can tell > > the user that something is wrong performance wise, if the OS is > > expected to have QXL present but does not. > > Adding this to "info spice" is an option. This has been discussed in > the past. IIRC we didn't actually implement it as there was not clear > whenever this is actually needed or whenever management will handle this > using the guest agent anyway. Alon? I'm working on a kind of "troubleshooting log" option for gnome-boxes which wants to record all these kinds of data so that a helpdesk or a developer can help figuring out a problem with a guest. Knowing if a qxl driver is in use is an important piece of information. Additionally it would be very nice if the driver could report a version string that I could query (same for virtio driver, etc).