From: Max Reitz <mreitz@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, Kevin Wolf <kwolf@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] qemu-iotests: fix 203 migration completion race
Date: Mon, 5 Mar 2018 17:04:52 +0100 [thread overview]
Message-ID: <ca82253e-0a7b-067b-59f5-e365d9b835f0@redhat.com> (raw)
In-Reply-To: <20180305155926.25858-1-stefanha@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1093 bytes --]
On 2018-03-05 16:59, Stefan Hajnoczi wrote:
> 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>
> ---
> tests/qemu-iotests/203 | 15 +++++++++++----
> tests/qemu-iotests/203.out | 5 +++++
> 2 files changed, 16 insertions(+), 4 deletions(-)
So much for "the ppoll() dungeon"...
Thanks!
Reviewed-by: Max Reitz <mreitz@redhat.com>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 512 bytes --]
next prev parent reply other threads:[~2018-03-05 16:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 15:59 [Qemu-devel] [PATCH] qemu-iotests: fix 203 migration completion race Stefan Hajnoczi
2018-03-05 16:04 ` Max Reitz [this message]
2018-03-06 16:18 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2018-03-07 18:01 ` Max Reitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ca82253e-0a7b-067b-59f5-e365d9b835f0@redhat.com \
--to=mreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).