From: Gerd Hoffmann <kraxel@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: libvir-list@redhat.com, Eric Blake <eblake@redhat.com>,
qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>
Subject: Re: [PATCH v2] ui: Make the DisplayType enum entries conditional
Date: Wed, 23 Jun 2021 14:43:18 +0200 [thread overview]
Message-ID: <20210623124318.nrmbawbebptmzn4w@sirius.home.kraxel.org> (raw)
In-Reply-To: <20210615090439.70926-1-thuth@redhat.com>
On Tue, Jun 15, 2021 at 11:04:39AM +0200, Thomas Huth wrote:
> Libvirt's "domcapabilities" command has a way to state whether certain
> graphic frontends are available in QEMU or not. Originally, libvirt
> looked at the "--help" output of the QEMU binary to determine whether
> SDL was available or not (by looking for the "-sdl" parameter in the
> help text), but since libvirt stopped doing this analysis of the help
> text, the detection of SDL is currently broken, see:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1790902
>
> QEMU should provide a way via the QMP interface instead. A simple way,
> without introducing additional commands, is to make the DisplayType
> enum entries conditional, so that the enum only contains the entries if
> the corresponding CONFIG_xxx switches have been set. This of course
> only gives an indication which possibilities have been enabled during
> compile-time of QEMU (and does not take into account whether modules
> are later available or not for example - for this we'd need a separate
> command), but anyway, this should already be good enough for the above
> bug ticket, and it's a good idea anyway to make the QMP interface
> conditional here, so let's simply do it.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
Added to ui queue.
thanks,
Gerd
prev parent reply other threads:[~2021-06-23 12:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 9:04 [PATCH v2] ui: Make the DisplayType enum entries conditional Thomas Huth
2021-06-23 12:43 ` Gerd Hoffmann [this message]
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=20210623124318.nrmbawbebptmzn4w@sirius.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=libvir-list@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.