qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Larsson <alexl@redhat.com>
To: Gerd Hoffmann <kraxel@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 10:35:00 +0100	[thread overview]
Message-ID: <1353404100.2180.39.camel@fatty> (raw)
In-Reply-To: <50AB4A2B.7060001@redhat.com>

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).

  reply	other threads:[~2012-11-20 10:04 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 [this message]
2012-11-20 10:17         ` Gerd Hoffmann
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=1353404100.2180.39.camel@fatty \
    --to=alexl@redhat.com \
    --cc=alevy@redhat.com \
    --cc=kraxel@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).