On 02/14/2018 09:50 AM, Viktor Mihajlovski wrote:
I'd like to know first what libvirt plans to do -- no sense in starting
deprecation if we're still stuck with it for a while.
FWIW, I'm currently preparing libvirt patches to use query-cpus-fast if
available. I wouldn't see why it would take more than one libvirt
release to get them in.
And libvirt releases more frequently, so that's probably not a limiting
factor for deprecating it now in qemu.
The question might rather be, which combinations of qemu and libvirt are
considered useful. E.g., I didn't upgrade libvirt in a while on my test
system but am using bleeding edge QEMU. But that doesn't necessarily
resemble a valid setup.
In general, new libvirt and old qemu is supported (libvirt tries hard to
make sure it can manage older images gracefully, for as long as older
qemu is still supported by a distro), but old libvirt and new qemu is
unsupported (you often get lucky where it works for a release or two,
because qemu tries hard not to break back-compat without proper
deprecation periods, but there may be features that you NEED a newer
libvirt to properly drive, and this is one of those cases).
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
