qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>,
	libvir-list@redhat.com, smitterl@redhat.com,
	Markus Armbruster <armbru@redhat.com>,
	qemu-devel@nongnu.org, Eric Blake <eblake@redhat.com>
Subject: Re: [RFC QEMU PATCH] ui: Make the DisplayType enum entries conditional
Date: Wed, 9 Jun 2021 12:29:58 +0100	[thread overview]
Message-ID: <YMCmNrcNByZ+Ozxn@redhat.com> (raw)
In-Reply-To: <20210609112405.pyv62l22g5ympoe4@sirius.home.kraxel.org>

On Wed, Jun 09, 2021 at 01:24:05PM +0200, Gerd Hoffmann wrote:
> On Wed, Jun 09, 2021 at 12:02:40PM +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. The simplest
> > 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.
> 
> Hmm, that'll break for the "dnf remove qemu-ui-sdl" case ...

Note tht libvirt invalidates its cache of QEMU capabilities when it
sees the /usr/lib64/qemu directory timestamp change. So it ought to
pick up changes caused by installing/removing QEMU modules, and apply
this to future queries for domcapabilities, or when starting future
QEMU guests.

Note, however, that capabilities are preserved at the time each
the QEMU process is started.

IOW, if you boot QEMU, then remove a QEMU module, then attempt to
use a feature that implies loading of the removed QEMU module,
libvirt won't know the module has been removed for the running
QEMU.


Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  reply	other threads:[~2021-06-09 11:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-09 10:02 [RFC QEMU PATCH] ui: Make the DisplayType enum entries conditional Thomas Huth
2021-06-09 11:24 ` Gerd Hoffmann
2021-06-09 11:29   ` Daniel P. Berrangé [this message]
2021-06-09 11:49     ` Gerd Hoffmann
2021-06-09 11:53       ` Daniel P. Berrangé
2021-06-09 12:01       ` Thomas Huth
2021-06-09 12:50         ` Gerd Hoffmann
2021-06-10  5:01           ` Markus Armbruster
2021-06-10  5:20           ` Thomas Huth
2021-06-09 13:11   ` Markus Armbruster
2021-06-09 13:16 ` Markus Armbruster
2021-06-09 14:36   ` Thomas Huth

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=YMCmNrcNByZ+Ozxn@redhat.com \
    --to=berrange@redhat.com \
    --cc=armbru@redhat.com \
    --cc=eblake@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=libvir-list@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=smitterl@redhat.com \
    --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 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).