[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH v2 3/3] iotests: add dirty bitmap migration test
From: |
Kevin Wolf |
Subject: |
Re: [Qemu-devel] [PATCH v2 3/3] iotests: add dirty bitmap migration test |
Date: |
Fri, 22 Dec 2017 14:43:44 +0100 |
User-agent: |
Mutt/1.9.1 (2017-09-22) |
Am 12.12.2017 um 17:04 hat Vladimir Sementsov-Ogievskiy geschrieben:
> The test creates two vms (vm_a, vm_b), create dirty bitmap in
> the first one, do several writes to corresponding device and
> then migrate vm_a to vm_b with dirty bitmaps.
>
> For now, only migration through shared storage for persistent
> bitmaps is available, so it is tested here. Only offline variant
> is tested for now (a kind of suspend-resume), as it is needed
> to test that this case is successfully fixed by recent patch.
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy <address@hidden>
> Reviewed-by: John Snow <address@hidden>
> [...]
> + self.vm_b.launch()
> + self.vm_b.event_wait("RESUME", timeout=10.0)
Wasn't this racy because the RESUME event may be sent before we connect
to the socket?
Kevin
[Qemu-devel] [PATCH v2 1/3] qcow2-bitmap: add qcow2_reopen_bitmaps_rw_hint(), Vladimir Sementsov-Ogievskiy, 2017/12/12
Re: [Qemu-devel] [PATCH v2 0/3] fix bitmaps migration through shared storage, Vladimir Sementsov-Ogievskiy, 2017/12/20