| commit | 28fa97e00698eecc9a7f7eeca43ccbdee3d33b3e | |
| author | Fabiano Rosas <farosas@suse.de> | |
| Wed, 12 Jul 2023 19:07:38 +0000 (12 16:07 -0300) | ||
| committer | Juan Quintela <quintela@redhat.com> | |
| Wed, 11 Oct 2023 09:17:02 +0000 (11 11:17 +0200) | ||
| tree | 6504370b03a9d421ce454b8d360f457ebc33021a | treesnapshot (tar.gz zip) |
| parent | 9d47929034eb8f3e67411926bdd1e8246d2797ed | commitdiff |
tests/qtest: migration: Add migrate_incoming_qmp helper
file-based migration requires the target to initiate its migration after
the source has finished writing out the data in the file. Currently
there's no easy way to initiate 'migrate-incoming', allow this by
introducing migrate_incoming_qmp helper, similarly to migrate_qmp.
Also make sure migration events are enabled and wait for the incoming
migration to start before returning. This avoid a race when querying
the migration status too soon after issuing the command.
Reviewed-by: Peter Xu <peterx@redhat.com>
Reviewed-by: Juan Quintela <quintela@redhat.com>
Signed-off-by: Fabiano Rosas <farosas@suse.de>
Signed-off-by: Juan Quintela <quintela@redhat.com>
Message-ID: <20230712190742.22294-3-farosas@suse.de>
file-based migration requires the target to initiate its migration after
the source has finished writing out the data in the file. Currently
there's no easy way to initiate 'migrate-incoming', allow this by
introducing migrate_incoming_qmp helper, similarly to migrate_qmp.
Also make sure migration events are enabled and wait for the incoming
migration to start before returning. This avoid a race when querying
the migration status too soon after issuing the command.
Reviewed-by: Peter Xu <peterx@redhat.com>
Reviewed-by: Juan Quintela <quintela@redhat.com>
Signed-off-by: Fabiano Rosas <farosas@suse.de>
Signed-off-by: Juan Quintela <quintela@redhat.com>
Message-ID: <20230712190742.22294-3-farosas@suse.de>
| tests/qtest/migration-helpers.c | diffblobblamehistory | |
| tests/qtest/migration-helpers.h | diffblobblamehistory |