25.03.2021 12:56, Stefan Hajnoczi wrote:
On Wed, Mar 24, 2021 at 08:42:27PM +0000, Peter Maydell wrote:
On Wed, 24 Mar 2021 at 20:18, Vladimir Sementsov-Ogievskiy
<vsement...@virtuozzo.com> wrote:
24.03.2021 21:05, Peter Maydell wrote:
On Wed, 24 Mar 2021 at 14:52, Stefan Hajnoczi <stefa...@redhat.com> wrote:
Vladimir Sementsov-Ogievskiy (2):
migration/block-dirty-bitmap: make incoming disabled bitmaps busy
migrate-bitmaps-postcopy-test: check that we can't remove in-flight
bitmaps
This failed the 'qsd-jobs' iotest on s390x:
I can't believe it related. My commit modifies bitmap status during bitmaps
migration on target vm. There is no kind of migration in qsd-jobs test.
It's possible it's an intermittent, but it's not one I've seen
before. We still have lots of time this release cycle to figure
out the issue and get this fix in.
Vladimir: I'll get hold of an s390 machine and try to reproduce the
failure. I should have some news by Monday.
Thanks! My path modifies migration/block-dirty-bitmap.c. qsd-jobs runs
block-commit and block-stream jobs and don't start any kind of migration or
snapshot or savevm, so it seems impossible that qsd-jobs runs the code touched
by my patch..
Let's put the pull request on hold for now.
Stefan
--
Best regards,
Vladimir
