diff options
| author | Stefan Hajnoczi <stefanha@redhat.com> | 2018-03-05 15:59:26 +0000 |
|---|---|---|
| committer | Max Reitz <mreitz@redhat.com> | 2018-03-09 15:40:07 +0100 |
| commit | 21794244d4e9c5f81132e4574e5bd10ef5066715 (patch) | |
| tree | 7952b5184f08ee1bb0b1fa72d3643d08db1641ea /replay | |
| parent | 39eaefcedb9af9131543e6b35386627780ac3f41 (diff) | |
| download | qemu-21794244d4e9c5f81132e4574e5bd10ef5066715.zip | |
qemu-iotests: fix 203 migration completion race
There is a race between the test's 'query-migrate' QMP command after the
QMP 'STOP' event and completing the migration:
The test case invokes 'query-migrate' upon receiving 'STOP'. At this
point the migration thread may still be in the process of completing.
Therefore 'query-migrate' can return 'status': 'active' for a brief
window of time instead of 'status': 'completed'. This results in
qemu-iotests 203 hanging.
Solve the race by enabling the 'events' migration capability, which
causes QEMU to emit migration-specific QMP events that do not suffer
from this race condition. Wait for the QMP 'MIGRATION' event with
'status': 'completed'.
Reported-by: Max Reitz <mreitz@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Message-id: 20180305155926.25858-1-stefanha@redhat.com
Reviewed-by: Max Reitz <mreitz@redhat.com>
Signed-off-by: Max Reitz <mreitz@redhat.com>
Diffstat (limited to 'replay')
0 files changed, 0 insertions, 0 deletions