This API call sets maximum tolerable time for which the domain is allowed to be
paused at the end of live migration. It's supposed to be called while the
domain is being live-migrated as a reaction to migration progress.
Changes in version 2:
- API renamed to reflect it's maximum downtime
- new flags parameter for the future
- qemu implementation was fixed so that the call is allowed iff the domain is
being migrated
- --downtime parameter of virsh migrate command was removed in favor of new
virsh migrate-setmaxdowntime which can be run independently
- virsh accepts downtime as nanoseconds instead of floating-point seconds
(shells don't deal with floating-point numbers well)
Jiri Denemark (5):
Public virDomainMigrateSetMaxDowntime API
Wire protocol and dispatcher for virDomainMigrateSetMaxDowntime
Implement virDomainMigrateSetMaxDowntime in remote driver
Implement virDomainMigrateSetMaxDowntime in qemu driver
Add migrate-setmaxdowntime command to virsh
daemon/remote.c | 29 ++++++++++
daemon/remote_dispatch_args.h | 1 +
daemon/remote_dispatch_prototypes.h | 8 +++
daemon/remote_dispatch_table.h | 5 ++
include/libvirt/libvirt.h.in | 4 ++
src/libvirt.c | 49 +++++++++++++++++
src/libvirt_public.syms | 5 ++
src/qemu/qemu_driver.c | 70 ++++++++++++++++++++++++-
src/qemu/qemu_monitor.c | 15 +++++
src/qemu/qemu_monitor.h | 3 +
src/qemu/qemu_monitor_json.c | 29 ++++++++++
src/qemu/qemu_monitor_json.h | 3 +
src/qemu/qemu_monitor_text.c | 27 ++++++++++
src/qemu/qemu_monitor_text.h | 3 +
src/remote/remote_driver.c | 32 +++++++++++-
src/remote/remote_protocol.c | 13 +++++
src/remote/remote_protocol.h | 98 +++++++++++++++++++----------------
src/remote/remote_protocol.x | 10 +++-
tools/virsh.c | 66 +++++++++++++++++++++++
tools/virsh.pod | 6 ++
20 files changed, 429 insertions(+), 47 deletions(-)