qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Daniel P . Berrange" <berrange@redhat.com>,
	Laurent Vivier <lvivier@redhat.com>,
	Juan Quintela <quintela@redhat.com>,
	"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
	peterx@redhat.com
Subject: [Qemu-devel] [RFC 0/6] migration: re-use migrate_incoming for postcopy recovery
Date: Tue, 15 Aug 2017 14:17:01 +0800	[thread overview]
Message-ID: <1502777827-18874-1-git-send-email-peterx@redhat.com> (raw)

This series is based on the postcopy failure recovery series. It
sololy tries to provide a new way to allow the destination to have a
new incoming channel.

One use case is when we are doing postcopy migration using a fd on
destination side. When network failure is detected, destination QEMU
will switch to postcopy-pause state for a recovery. However since the
old fd is disconnected and not valid any more, there is no way to do a
reconnection without a new reconfiguration.

With this series, we can specify the new listening channel by using
"migrate_incoming xxx:xxx" command. It was used only for "-incoming
defer" to defer an incoming migration. This series extended its usage
for paused postcopy as well.

Please review, thanks.

Peter Xu (6):
  migration: free SocketAddress where allocated
  migration: return incoming task tag for sockets
  migration: return incoming task tag for exec
  migration: return incoming task tag for fd
  migration: store listen task tag
  migration: allow migrate_incoming for paused VM

 migration/exec.c      | 18 ++++++++++-------
 migration/exec.h      |  2 +-
 migration/fd.c        | 18 ++++++++++-------
 migration/fd.h        |  2 +-
 migration/migration.c | 56 +++++++++++++++++++++++++++++++++++++++++----------
 migration/migration.h |  2 ++
 migration/socket.c    | 40 +++++++++++++++++++++++-------------
 migration/socket.h    |  4 ++--
 8 files changed, 99 insertions(+), 43 deletions(-)

-- 
2.7.4

             reply	other threads:[~2017-08-15  6:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-15  6:17 Peter Xu [this message]
2017-08-15  6:17 ` [Qemu-devel] [RFC 1/6] migration: free SocketAddress where allocated Peter Xu
2017-08-15  6:17 ` [Qemu-devel] [RFC 2/6] migration: return incoming task tag for sockets Peter Xu
2017-08-15  6:17 ` [Qemu-devel] [RFC 3/6] migration: return incoming task tag for exec Peter Xu
2017-08-15  6:17 ` [Qemu-devel] [RFC 4/6] migration: return incoming task tag for fd Peter Xu
2017-08-15  6:17 ` [Qemu-devel] [RFC 5/6] migration: store listen task tag Peter Xu
2017-08-15  8:37   ` Daniel P. Berrange
2017-08-15  8:50     ` Peter Xu
2017-08-15  9:27       ` Daniel P. Berrange
2017-08-15  9:47         ` Peter Xu
2017-08-16  9:47           ` Peter Xu
2017-08-29 10:38             ` Daniel P. Berrange
2017-08-30  7:38               ` Peter Xu
2017-08-15  6:17 ` [Qemu-devel] [RFC 6/6] migration: allow migrate_incoming for paused VM Peter Xu

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=1502777827-18874-1-git-send-email-peterx@redhat.com \
    --to=peterx@redhat.com \
    --cc=berrange@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=lvivier@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).