diff options
| author | Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com> | 2020-06-04 11:33:41 +0300 |
|---|---|---|
| committer | Eric Blake <eblake@redhat.com> | 2020-06-09 17:05:50 -0500 |
| commit | 93d487807bf8fb9a5867d1a0a77d7afbc26e6c5c (patch) | |
| tree | 8723c3c7c3ba0061b4fcecb1e653e0b2dc8b89cf /nbd | |
| parent | 31d321c2b3574dcc74e9f6411af06bca6b5d10f4 (diff) | |
| download | qemu-93d487807bf8fb9a5867d1a0a77d7afbc26e6c5c.zip qemu-93d487807bf8fb9a5867d1a0a77d7afbc26e6c5c.tar.gz qemu-93d487807bf8fb9a5867d1a0a77d7afbc26e6c5c.tar.bz2 | |
iotests: 194: wait for migration completion on target too
It is possible, that shutdown on target occurs earlier than migration
finish. In this case we crash in bdrv_release_dirty_bitmap_locked()
on assertion "assert(!bdrv_dirty_bitmap_busy(bitmap));" as we do have
busy bitmap, as bitmap migration is ongoing.
We'll fix bitmap migration to gracefully cancel on early shutdown soon.
Now let's fix iotest 194 to wait migration completion before shutdown.
Note that in this test dest_vm.shutdown() is called implicitly, as vms
used as context-providers, see __exit__() method of QEMUMachine class.
Actually, not waiting migration finish is a wrong thing, but the test
started to crash after commit ae00aa239847682
"iotests: 194: test also migration of dirty bitmap", which added dirty
bitmaps here. So, Fixes: tag won't hurt.
Fixes: ae00aa2398476824f0eca80461da215e7cdc1c3b
Reported-by: Thomas Huth <thuth@redhat.com>
Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Tested-by: Thomas Huth <thuth@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
[eblake: grammar tweak]
Message-Id: <20200604083341.26978-1-vsementsov@virtuozzo.com>
Signed-off-by: Eric Blake <eblake@redhat.com>
Diffstat (limited to 'nbd')
0 files changed, 0 insertions, 0 deletions