qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Alexander Larsson <alexl@redhat.com>
Cc: Alon Levy <alevy@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qxl: Export "mode" as a property
Date: Tue, 20 Nov 2012 11:17:14 +0100	[thread overview]
Message-ID: <50AB58AA.6060303@redhat.com> (raw)
In-Reply-To: <1353404100.2180.39.camel@fatty>

  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

  reply	other threads:[~2012-11-20 10:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-19 13:11 [Qemu-devel] [PATCH] qxl: Export "mode" as a property Alexander Larsson
2012-11-20  7:50 ` Gerd Hoffmann
2012-11-20  9:07   ` Daniel P. Berrange
2012-11-20  9:15     ` Gerd Hoffmann
2012-11-20  9:35       ` Alexander Larsson
2012-11-20 10:17         ` Gerd Hoffmann [this message]
2012-11-20 10:30           ` Alexander Larsson
2012-11-20 10:53             ` Gerd Hoffmann
2012-11-20 11:41               ` Alexander Larsson
2012-11-20  9:49       ` Alon Levy
2012-11-20  9:48   ` Markus Armbruster
2012-11-20  9:51     ` Alexander Larsson
2012-11-20 10:28     ` Gerd Hoffmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50AB58AA.6060303@redhat.com \
    --to=kraxel@redhat.com \
    --cc=alevy@redhat.com \
    --cc=alexl@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).