From: Peter Xu <peterx@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: qemu-devel@nongnu.org, Andrea Arcangeli <aarcange@redhat.com>,
"Daniel P . Berrange" <berrange@redhat.com>,
Juan Quintela <quintela@redhat.com>,
Alexey Perevalov <a.perevalov@samsung.com>
Subject: Re: [Qemu-devel] [PATCH v7 22/23] migration/qmp: add command migrate-pause
Date: Tue, 13 Mar 2018 16:54:04 +0800 [thread overview]
Message-ID: <20180313085404.GH11787@xz-mi> (raw)
In-Reply-To: <20180312173609.GV3219@work-vm>
On Mon, Mar 12, 2018 at 05:36:09PM +0000, Dr. David Alan Gilbert wrote:
> * Peter Xu (peterx@redhat.com) wrote:
> > It pauses an ongoing migration. Currently it only supports postcopy.
> > Note that this command will work on either side of the migration.
> > Basically when we trigger this on one side, it'll interrupt the other
> > side as well since the other side will get notified on the disconnect
> > event.
> >
> > However, it's still possible that the other side is not notified, for
> > example, when the network is totally broken, or due to some firewall
> > configuration changes. In that case, we will also need to run the same
> > command on the other side so both sides will go into the paused state.
> >
> > Signed-off-by: Peter Xu <peterx@redhat.com>
> > ---
> > migration/migration.c | 27 +++++++++++++++++++++++++++
> > qapi/migration.json | 16 ++++++++++++++++
> > 2 files changed, 43 insertions(+)
> >
> > diff --git a/migration/migration.c b/migration/migration.c
> > index 180552329c..f31fcbb0d5 100644
> > --- a/migration/migration.c
> > +++ b/migration/migration.c
> > @@ -1448,6 +1448,33 @@ void qmp_migrate_recover(const char *uri, Error **errp)
> > qemu_start_incoming_migration(uri, errp);
> > }
> >
> > +void qmp_migrate_pause(Error **errp)
> > +{
> > + MigrationState *ms = migrate_get_current();
> > + MigrationIncomingState *mis = migration_incoming_get_current();
> > + int ret;
> > +
> > + if (ms->state == MIGRATION_STATUS_POSTCOPY_ACTIVE) {
> > + /* Source side, during postcopy */
> > + ret = qemu_file_shutdown(ms->to_dst_file);
>
> How did this fix the race I mentioned last time?
Ah sorry I missed that one. I'll reply there.
--
Peter Xu
next prev parent reply other threads:[~2018-03-13 8:54 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-09 9:15 [Qemu-devel] [PATCH v7 00/23] Migration: postcopy failure recovery Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 01/23] migration: let incoming side use thread context Peter Xu
2018-03-12 17:27 ` Dr. David Alan Gilbert
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 02/23] migration: new postcopy-pause state Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 03/23] migration: implement "postcopy-pause" src logic Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 04/23] migration: allow dst vm pause on postcopy Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 05/23] migration: allow src return path to pause Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 06/23] migration: allow fault thread " Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 07/23] qmp: hmp: add migrate "resume" option Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 08/23] migration: rebuild channel on source Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 09/23] migration: new state "postcopy-recover" Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 10/23] migration: wakeup dst ram-load-thread for recover Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 11/23] migration: new cmd MIG_CMD_RECV_BITMAP Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 12/23] migration: new message MIG_RP_MSG_RECV_BITMAP Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 13/23] migration: new cmd MIG_CMD_POSTCOPY_RESUME Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 14/23] migration: new message MIG_RP_MSG_RESUME_ACK Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 15/23] migration: introduce SaveVMHandlers.resume_prepare Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 16/23] migration: synchronize dirty bitmap for resume Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 17/23] migration: setup ramstate " Peter Xu
2018-03-12 17:29 ` Dr. David Alan Gilbert
2018-03-12 17:30 ` Dr. David Alan Gilbert
2018-03-13 8:36 ` Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 18/23] migration: final handshake for the resume Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 19/23] migration: init dst in migration_object_init too Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 20/23] qmp/migration: new command migrate-recover Peter Xu
2018-03-12 17:33 ` Dr. David Alan Gilbert
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 21/23] hmp/migration: add migrate_recover command Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 22/23] migration/qmp: add command migrate-pause Peter Xu
2018-03-12 17:36 ` Dr. David Alan Gilbert
2018-03-13 8:54 ` Peter Xu [this message]
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 23/23] migration/hmp: add migrate_pause command Peter Xu
2018-03-09 9:47 ` [Qemu-devel] [PATCH v7 00/23] Migration: postcopy failure recovery no-reply
2018-03-09 9:48 ` no-reply
2018-03-09 9:49 ` no-reply
2018-03-09 9:51 ` no-reply
2018-03-09 9:56 ` no-reply
2018-03-09 9:57 ` no-reply
2018-03-09 16:54 ` Eric Blake
2018-03-09 16:59 ` Eric Blake
2018-03-12 4:45 ` Peter Xu
2018-03-15 8:19 ` Fam Zheng
2018-03-15 8:41 ` Peter Xu
2018-03-15 9:04 ` Fam Zheng
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=20180313085404.GH11787@xz-mi \
--to=peterx@redhat.com \
--cc=a.perevalov@samsung.com \
--cc=aarcange@redhat.com \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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).