On 1/21/25 13:05, Jiri Denemark wrote: > When a migration is canceled very late once virtual CPUs are already > stopped, QEMU will automatically resume them. If this happens after we > exited a waiting loop in qemuMigrationSrcWaitForCompletion, but before a > loop that tries to make sure CPUs are stopped by waiting for the > appropriate event, we may end up waiting forever because the CPUs are > running (they were resumed by migrate_cancel), but the STOP event is > already gone. > > This is possible because we enter monitor for fetching migration > statistics at which point other APIs can be processed and migration may > change its state. We should recheck the state when we get back from the > monitor code. > > https://issues.redhat.com/browse/RHEL-52493 > > Signed-off-by: Jiri Denemark <jdene...@redhat.com> > --- > src/qemu/qemu_migration.c | 7 +++++++ > 1 file changed, 7 insertions(+) >
Reviewed-by: Michal Privoznik <mpriv...@redhat.com> Michal
