From: Eric Blake <eblake@redhat.com>
To: Viktor Mihajlovski <mihajlov@linux.vnet.ibm.com>,
Cornelia Huck <cohuck@redhat.com>,
berrange@redhat.com
Cc: qemu-devel@nongnu.org, agraf@suse.de, ehabkost@redhat.com,
armbru@redhat.com, david@redhat.com, dgilbert@redhat.com,
borntraeger@de.ibm.com, qemu-s390x@nongnu.org,
pbonzini@redhat.com, rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCHv2 3/3] qmp: add architecture specific cpu data for query-cpus-fast
Date: Wed, 14 Feb 2018 10:07:57 -0600 [thread overview]
Message-ID: <c5c32795-424f-3dd9-85cf-2beb13696b83@redhat.com> (raw)
In-Reply-To: <b1704559-ae69-8c1c-eae5-3e473e271364@linux.vnet.ibm.com>
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
next prev parent reply other threads:[~2018-02-14 16:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 17:18 [Qemu-devel] [PATCHv2 0/3] add query-cpu-fast and related s390 changes Viktor Mihajlovski
2018-02-13 17:18 ` [Qemu-devel] [PATCHv2 1/3] qmp: expose s390-specific CPU info Viktor Mihajlovski
2018-02-14 9:30 ` Christian Borntraeger
2018-02-14 9:46 ` David Hildenbrand
2018-02-13 17:18 ` [Qemu-devel] [PATCHv2 2/3] qmp: add query-cpus-fast Viktor Mihajlovski
2018-02-14 10:11 ` Cornelia Huck
2018-02-14 19:46 ` Eric Blake
2018-02-13 17:18 ` [Qemu-devel] [PATCHv2 3/3] qmp: add architecture specific cpu data for query-cpus-fast Viktor Mihajlovski
2018-02-14 10:15 ` Cornelia Huck
2018-02-14 15:15 ` Eric Blake
2018-02-14 15:27 ` Cornelia Huck
2018-02-14 15:50 ` Viktor Mihajlovski
2018-02-14 16:07 ` Eric Blake [this message]
2018-02-14 19:56 ` Eric Blake
2018-02-14 10:57 ` [Qemu-devel] [PATCHv2 0/3] add query-cpu-fast and related s390 changes Cornelia Huck
2018-02-14 14:00 ` Viktor Mihajlovski
2018-02-14 15:49 ` Dr. David Alan Gilbert
2018-02-14 15:16 ` Eric Blake
2018-02-14 15:26 ` Cornelia Huck
2018-02-14 20:01 ` Eric Blake
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=c5c32795-424f-3dd9-85cf-2beb13696b83@redhat.com \
--to=eblake@redhat.com \
--cc=agraf@suse.de \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=dgilbert@redhat.com \
--cc=ehabkost@redhat.com \
--cc=mihajlov@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
/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).