Il 07/02/2014 14:07, Andrey Korolyov ha scritto:
Ok, I will do, but looks like libvirt version(1.0.2) in not relevant - it meets criteria set by debian packagers and again, 'broken state' is not relevant to the libvirt state history, it more likely to be qemu/kvm problem.
It is relevant, qemu introduced a new migration status before "active" ("setup") and libvirt doesn't recognize it.
Paolo -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
