Libvirt daemon was not completely ready to lose a connection to the client (may
even be source libvirtd) which is controling the migration. We might end up
with dangling migration jobs on both source and destination daemons. More
details about the scenarios this might happen can be found in patches 2/5 and
5/5 which fix the issue using infrastructure set up by the other patches in
this series.
Jiri Denemark (5):
qemu: Add support for domain cleanup callbacks
qemu: Avoid dangling migration-in job on shutoff domains
qemu: Add connection close callbacks
qemu: Make autodestroy utilize connection close callbacks
qemu: Avoid dangling migration-out job when client dies
src/qemu/qemu_conf.c | 172 +++++++++++++++++++++++++++++++++++++++++++++
src/qemu/qemu_conf.h | 30 +++++++-
src/qemu/qemu_domain.c | 75 +++++++++++++++++++-
src/qemu/qemu_domain.h | 17 +++++
src/qemu/qemu_driver.c | 10 ++-
src/qemu/qemu_migration.c | 88 +++++++++++++++++++++++
src/qemu/qemu_migration.h | 4 +
src/qemu/qemu_process.c | 109 +++++++----------------------
8 files changed, 413 insertions(+), 92 deletions(-)
--
1.7.8.5