From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "Kevin Wolf" <kwolf@redhat.com>, "Thomas Huth" <thuth@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Markus Armbruster" <armbru@redhat.com>,
qemu-devel@nongnu.org,
"Alistair Francis" <alistair.francis@wdc.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
dirty.ice.hu@gmail.com, "Robert Hoo" <robert.hu@linux.intel.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: Let's remove some deprecated stuff
Date: Thu, 29 Apr 2021 11:24:35 +0100 [thread overview]
Message-ID: <YIqJY1Z4jqruCu17@redhat.com> (raw)
In-Reply-To: <20210429101842.hupkajdlkttq6l4v@sirius.home.kraxel.org>
On Thu, Apr 29, 2021 at 12:18:42PM +0200, Gerd Hoffmann wrote:
> Hi,
>
> > ``QEMU_AUDIO_`` environment variables and ``-audio-help`` (since 4.0)
> > Creating sound card devices and vnc without ``audiodev=`` property (since 4.2)
> > Creating sound card devices using ``-soundhw`` (since 5.1)
>
> I think these three should be dropped together, to minimize disruption.
>
> Where do we strand in terms of libvirt support? IIRC audiodev= support
> in libvirt is rather recent (merged this year). I'd tend to wait a bit
> longer because of that.
>
> Daniel?
Libvirt added supoort for -audio in 7.2.0, release April 4th, so only
one month ago.
If we drop the features in QEMU in this dev cycle though, this won't
impact most users until QEMU 6.1 releases in mid August. I'm perfectly
ok with people who use unreleased QEMU git master needing to update
their libvirt. The final release date is far enough away that distros
will have had new enough libvirt for a good while.
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 :|
next prev parent reply other threads:[~2021-04-29 10:27 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 9:59 Let's remove some deprecated stuff Markus Armbruster
2021-04-29 10:18 ` Gerd Hoffmann
2021-04-29 10:24 ` Daniel P. Berrangé [this message]
2021-04-29 10:29 ` Peter Maydell
2021-04-29 10:35 ` Daniel P. Berrangé
2021-04-29 10:55 ` Gerd Hoffmann
2021-04-30 10:47 ` Markus Armbruster
2021-04-29 11:07 ` Paolo Bonzini
2021-04-29 10:25 ` Peter Maydell
2021-04-29 10:32 ` Daniel P. Berrangé
2021-04-30 6:47 ` Markus Armbruster
2021-04-29 11:06 ` Paolo Bonzini
2021-04-29 12:40 ` Gerd Hoffmann
2021-04-29 13:12 ` Kevin Wolf
2021-04-29 13:46 ` Gerd Hoffmann
2021-04-29 15:05 ` Philippe Mathieu-Daudé
2021-04-30 7:01 ` Markus Armbruster
2021-04-30 7:01 ` Gerd Hoffmann
2021-05-03 15:10 ` Paolo Bonzini
2021-04-29 11:17 ` Thomas Huth
2021-04-29 11:24 ` Peter Maydell
2021-05-03 10:39 ` Markus Armbruster
2021-04-29 14:49 ` Stefan Hajnoczi
2021-04-29 16:32 ` Eduardo Habkost
2021-04-30 3:22 ` Robert Hoo
2021-05-03 1:41 ` Alistair Francis
2021-05-03 4:49 ` Thomas Huth
2021-05-03 7:12 ` Alistair Francis
2021-05-03 15:13 ` Paolo Bonzini
2021-05-03 22:57 ` Alistair Francis
2021-05-03 13:14 ` Philippe Mathieu-Daudé
2021-05-03 18:21 ` Eric Blake
2021-05-04 13:59 ` Peter Krempa
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=YIqJY1Z4jqruCu17@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=alistair.francis@wdc.com \
--cc=armbru@redhat.com \
--cc=dirty.ice.hu@gmail.com \
--cc=kraxel@redhat.com \
--cc=kwolf@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=robert.hu@linux.intel.com \
--cc=stefanha@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).