From: "Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>
To: qemu-devel@nongnu.org, kwolf@redhat.com, jdenemar@redhat.com,
wangjie88@huawei.com, quintela@redhat.com, peterx@redhat.com,
mreitz@redhat.com
Cc: berrange@redhat.com, eblake@redhat.com, fuweiwei2@huawei.com
Subject: [Qemu-devel] [PATCH v4 0/7] migration: pause-before-switchover
Date: Fri, 20 Oct 2017 10:05:49 +0100 [thread overview]
Message-ID: <20171020090556.18631-1-dgilbert@redhat.com> (raw)
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Hi,
This set attempts to make a race condition between migration and
drive-mirror (and other block users) soluble by allowing the migration
to be paused after the source qemu releases the block devices but
before the serialisation of the device state.
The symptom of this failure, as reported by Wangjie, is a:
_co_do_pwritev: Assertion `!(bs->open_flags & 0x0800)' failed
and the source qemu dieing; so the problem is pretty nasty.
This has only been seen on 2.9 onwards, but the theory is that
prior to 2.9 it might have been happening anyway and we were
perhaps getting unreported corruptions (lost writes); so this
really needs fixing.
This flow came from discussions between Kevin and me, and we can't
see a way of fixing it without exposing a new state to the management
layer.
The flow is now:
(qemu) migrate_set_capability pause-before-switchover on
(qemu) migrate -d ...
(qemu) info migrate
...
Migration status: pre-switchover
...
<< issue commands to clean up any block jobs>>
(qemu) migrate_continue pre-switchover
(qemu) info migrate
...
Migration status: completed
This has been tested with Jiri's libvirt at:
https://gitlab.com/jirkade/libvirt.git migration-pause
with:
migrate --live --copy-storage-all --verbose
The precopy flow is:
active->pre-switchover->device->completed
The postcopy flow is:
active->pre-switchover->postcopy-active->completed
Although the behaviour with postcopy only gets interesting when
we add something like Max's active-sync.
Dave
--
v4
Comment fix in 'migrate-continue' example (thanks Jiri)
v3
A couple of FIXUPs that had escaped v2's merge
v2
Pause *before* block inactivation (thanks Peter)
Rename state and capability to Dan+KWolf's combined suggestion
Dr. David Alan Gilbert (7):
migration: Add 'pause-before-switchover' capability
migration: Add 'pre-switchover' and 'device' statuses
migration: Wait for semaphore before completing migration
migration: migrate-continue
migrate: HMP migate_continue
migration: allow cancel to unpause
migration: pause-before-switchover for postcopy
hmp-commands.hx | 12 +++++++
hmp.c | 13 ++++++++
hmp.h | 1 +
migration/migration.c | 88 +++++++++++++++++++++++++++++++++++++++++++++++++--
migration/migration.h | 4 +++
qapi/migration.json | 30 ++++++++++++++++--
6 files changed, 144 insertions(+), 4 deletions(-)
--
2.13.6
next reply other threads:[~2017-10-20 9:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 9:05 Dr. David Alan Gilbert (git) [this message]
2017-10-20 9:05 ` [Qemu-devel] [PATCH v4 1/7] migration: Add 'pause-before-switchover' capability Dr. David Alan Gilbert (git)
2017-10-23 10:55 ` Juan Quintela
2017-10-20 9:05 ` [Qemu-devel] [PATCH v4 2/7] migration: Add 'pre-switchover' and 'device' statuses Dr. David Alan Gilbert (git)
2017-10-23 10:55 ` Juan Quintela
2017-10-20 9:05 ` [Qemu-devel] [PATCH v4 3/7] migration: Wait for semaphore before completing migration Dr. David Alan Gilbert (git)
2017-10-23 11:02 ` Juan Quintela
2017-10-20 9:05 ` [Qemu-devel] [PATCH v4 4/7] migration: migrate-continue Dr. David Alan Gilbert (git)
2017-10-23 11:03 ` Juan Quintela
2017-10-20 9:05 ` [Qemu-devel] [PATCH v4 5/7] migrate: HMP migate_continue Dr. David Alan Gilbert (git)
2017-10-23 11:03 ` Juan Quintela
2017-10-20 9:05 ` [Qemu-devel] [PATCH v4 6/7] migration: allow cancel to unpause Dr. David Alan Gilbert (git)
2017-10-23 11:04 ` Juan Quintela
2017-10-20 9:05 ` [Qemu-devel] [PATCH v4 7/7] migration: pause-before-switchover for postcopy Dr. David Alan Gilbert (git)
2017-10-23 11:05 ` Juan Quintela
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=20171020090556.18631-1-dgilbert@redhat.com \
--to=dgilbert@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=fuweiwei2@huawei.com \
--cc=jdenemar@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=wangjie88@huawei.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).