From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:57785) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tal6f-00012G-K0 for qemu-devel@nongnu.org; Tue, 20 Nov 2012 05:31:11 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Tal6W-0002hk-9F for qemu-devel@nongnu.org; Tue, 20 Nov 2012 05:31:05 -0500 Received: from mx1.redhat.com ([209.132.183.28]:49742) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tal6W-0002he-03 for qemu-devel@nongnu.org; Tue, 20 Nov 2012 05:30:56 -0500 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id qAKAUgP2006318 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 20 Nov 2012 05:30:55 -0500 Message-ID: <1353407424.2180.44.camel@fatty> From: Alexander Larsson Date: Tue, 20 Nov 2012 11:30:24 +0100 In-Reply-To: <50AB58AA.6060303@redhat.com> 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> <50AB58AA.6060303@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 11:17 +0100, Gerd Hoffmann wrote: > 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. I know that, but it would be possible to add code to the driver to register a version string. > 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. Might be useful for qxl developers, but not very useful to e.g. a helpdesk employee trying to solve an issue for a user, as its kinda low-level. Having the version string would be very nice here. > 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. Sure, that would work too, as long as i can enumerate the devices and get the data in a machine parsable format. Properties are already that, although I realize that mixing configuration and monitoring in the same set might be problematic.