From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:33894) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TaktN-0001wQ-6P for qemu-devel@nongnu.org; Tue, 20 Nov 2012 05:17:26 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TaktK-0006Xq-QQ for qemu-devel@nongnu.org; Tue, 20 Nov 2012 05:17:21 -0500 Received: from mx1.redhat.com ([209.132.183.28]:32987) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TaktK-0006XU-Iw for qemu-devel@nongnu.org; Tue, 20 Nov 2012 05:17:18 -0500 Received: from int-mx02.intmail.prod.int.phx2.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id qAKAHHoN016779 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 20 Nov 2012 05:17:17 -0500 Message-ID: <50AB58AA.6060303@redhat.com> Date: Tue, 20 Nov 2012 11:17:14 +0100 From: Gerd Hoffmann MIME-Version: 1.0 References: <1353330711-20207-1-git-send-email-alexl@redhat.com> <50AB3631.2080000@redhat.com> <20121120090736.GA3461@redhat.com> <50AB4A2B.7060001@redhat.com> <1353404100.2180.39.camel@fatty> In-Reply-To: <1353404100.2180.39.camel@fatty> Content-Type: text/plain; charset=UTF-8 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: Alexander Larsson Cc: Alon Levy , qemu-devel@nongnu.org Hi, > 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. Understood. > 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). Guest driver version information isn't available. For QXL we could track which features are in use by the driver (i.e. whenever it uses sync/async io ports, ...) which might be good enougth for trouble shooting. For virtio it should be likewise easy to figure which device features the guest has activated. If you also wanna have this for non-qxl devices (which makes sense indeed) going the "info spice" route doesn't make that much sense though. It is probably more useful to add an (optional) "report device state" callback to devices which then returns this info in some useful format (qdict?), then wind this up as monitor command. cheers, Gerd