diff options
author | Max Reitz <mreitz@redhat.com> | 2018-12-21 19:42:26 +0100 |
---|---|---|
committer | Kevin Wolf <kwolf@redhat.com> | 2019-02-01 13:46:44 +0100 |
commit | 9a378495c3cde80aba9299ceab55338d7e78691d (patch) | |
tree | ec5a81efb08554d033ae1a5a0f15238edfa450f8 /block/vmdk.c | |
parent | 4720cbeea1f42fd905fc69338fd42b191e58b412 (diff) |
iotests: Make 234 stable
This test waits for a MIGRATION event with status=completed on the
source VM before querying the migration status on both source and
destination. However, just because the source says migration has
completed does not mean the destination thinks the same. Therefore, in
some cases, the destination VM may still report "active" instead of
"completed" when asked for its migration status.
Fix this by enabling migration events on both VMs and waiting until both
source and destination emit a status=completed MIGRATION event.
Signed-off-by: Max Reitz <mreitz@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Diffstat (limited to 'block/vmdk.c')
0 files changed, 0 insertions, 0 deletions