diff options
| author | Fabiano Rosas <farosas@suse.de> | 2025-02-13 14:59:26 -0300 |
|---|---|---|
| committer | Fabiano Rosas <farosas@suse.de> | 2025-02-14 15:19:06 -0300 |
| commit | 538e03d28001a325a93154df2313d215721b2241 (patch) | |
| tree | ae3d469c76b4181a1f24afc9ea945ed4fa7247ff /rust/qemu-api/src | |
| parent | aabb2a5b5d54acde0992d933b647a306e59362b4 (diff) | |
| download | qemu-538e03d28001a325a93154df2313d215721b2241.zip qemu-538e03d28001a325a93154df2313d215721b2241.tar.gz qemu-538e03d28001a325a93154df2313d215721b2241.tar.bz2 | |
tests/qtest/migration: Add a cancel test
The qmp_migrate_cancel() command is poorly tested and code inspection
reveals that there might be concurrency issues with its usage. Add a
test that runs a migration and calls qmp_migrate_cancel() at specific
moments.
In order to make the test more deterministic, instead of calling
qmp_migrate_cancel() at random moments during migration, do it after
the migration status change events are seen.
The expected result is that qmp_migrate_cancel() on the source ends
migration on the source with the "cancelled" state and ends migration
on the destination with the "failed" state. The only exception is that
a failed migration should continue in the failed state.
Cancelling is not allowed during postcopy (no test is added for this
because it's a trivial check in the code).
Reviewed-by: Peter Xu <peterx@redhat.com>
Message-ID: <20250213175927.19642-9-farosas@suse.de>
Signed-off-by: Fabiano Rosas <farosas@suse.de>
Diffstat (limited to 'rust/qemu-api/src')
0 files changed, 0 insertions, 0 deletions