On Tue, May 10, 2022 at 17:21:01 +0200, Jiri Denemark wrote: > So far migration could only be completed while a migration API was > running and waiting for the migration to finish. In case such API could > not be called (the connection that initiated the migration is broken) > the migration would just be aborted or left in a "don't know what to do" > state. But this will change soon and we will be able to successfully > complete such migration once we get the corresponding event from QEMU. > This is specific to post-copy migration when vCPUs are already running > on the destination and we're only waiting for all memory pages to be > transferred. Such post-copy migration (which no-one is actively > watching) is called unattended migration. > > Signed-off-by: Jiri Denemark <jdenemar@xxxxxxxxxx> > --- > src/qemu/qemu_domain.c | 1 + > src/qemu/qemu_domain.h | 1 + > src/qemu/qemu_driver.c | 5 +++++ > src/qemu/qemu_migration.c | 43 +++++++++++++++++++++++++++++++++++++-- > src/qemu/qemu_migration.h | 6 ++++++ > src/qemu/qemu_process.c | 18 ++++++++++++++++ > 6 files changed, 72 insertions(+), 2 deletions(-) Reviewed-by: Peter Krempa <pkrempa@xxxxxxxxxx>
