On 03/13/2015 06:28 AM, Dr. David Alan Gilbert wrote:
>
> It simplifies qemu's job of reporting migration status information (qemu
> is no longer maintaining one set of states internally and a different
> set of states externally), and I already have the libvirt counterpart
> patch ready to go to gracefully accept the new state name.
Yes, it does make life simpler in the long run.
(It does worry me a bit what happens to new qemu on old libvirt)
In the past, we've already stated that it is okay for new qemu to
require new libvirt. What is not okay is for new libvirt to require new
qemu. This change is okay given those rules.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library
http://libvirt.org