From: Stefan Hajnoczi <stefanha@gmail.com>
To: Max Reitz <mreitz@redhat.com>
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
qemu-devel@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH] qemu-iotests: fix 203 migration completion race
Date: Tue, 6 Mar 2018 16:18:12 +0000 [thread overview]
Message-ID: <20180306161812.GO31045@stefanha-x1.localdomain> (raw)
In-Reply-To: <ca82253e-0a7b-067b-59f5-e365d9b835f0@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2491 bytes --]
On Mon, Mar 05, 2018 at 05:04:52PM +0100, Max Reitz wrote:
> 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"...
It was still a pain to debug :).
I put a ring buffer into the QMP monitor input/output code. Then it was
possible to figure out the issue via GDB on a hung QEMU:
(gdb) p current_run_state
RUN_STATE_POSTMIGRATE
(gdb) p current_migration->status
MIGRATION_STATUS_COMPLETED
(gdb) p monitor_out_ring
...'STOP' event...
(gdb) p monitor_in_ring
...query-migrate... <-- okay, the test checked if migration finished
Then looking at the code:
static void migration_completion(MigrationState *s)
{
...
if (s->state == MIGRATION_STATUS_ACTIVE) {
qemu_mutex_lock_iothread();
s->downtime_start = qemu_clock_get_ms(QEMU_CLOCK_REALTIME);
qemu_system_wakeup_request(QEMU_WAKEUP_REASON_OTHER);
s->vm_was_running = runstate_is_running();
ret = global_state_store();
if (!ret) {
bool inactivate = !migrate_colo_enabled();
v---- The stop event comes from here
ret = vm_stop_force_state(RUN_STATE_FINISH_MIGRATE);
...
}
qemu_mutex_unlock_iothread(); <--- oh, no!
...
if (!migrate_colo_enabled()) {
migrate_set_state(&s->state, current_active_state,
MIGRATION_STATUS_COMPLETED); <-- too late!
}
return;
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2018-03-06 16:18 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
2018-03-06 16:18 ` Stefan Hajnoczi [this message]
2018-03-07 18:01 ` [Qemu-devel] [Qemu-block] " 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=20180306161812.GO31045@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=kwolf@redhat.com \
--cc=mreitz@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).