On Tue, May 10, 2022 at 17:20:40 +0200, Jiri Denemark wrote: > Migration is a job which takes some time and if it succeeds, there's > nothing to call another migration on. If a migration fails, it might > make sense to rerun it with different arguments, but this would only be > done once the first migration fails rather than while it is still > running. > > If this was not enough, the migration job now stays active even if > post-copy migration fails and anyone possibly retrying the migration > would be waiting for the job timeout just to get a suboptimal error > message. > > So let's special case getting a migration job when another one is > already active. > > Signed-off-by: Jiri Denemark <jdenemar@xxxxxxxxxx> > --- > src/qemu/qemu_migration.c | 23 +++++++++++++++++++++++ > 1 file changed, 23 insertions(+) Reviewed-by: Peter Krempa <pkrempa@xxxxxxxxxx>
