qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org
Cc: Juan Quintela <quintela@redhat.com>,
	"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
	Laurent Vivier <lvivier@redhat.com>
Subject: Re: [Qemu-devel] [PATCH RFC 0/6] migration: enable return-path for precopy
Date: Fri, 19 May 2017 14:48:19 +0800	[thread overview]
Message-ID: <20170519064819.GA14679@pxdev.xzpeter.org> (raw)
In-Reply-To: <1495176212-14446-1-git-send-email-peterx@redhat.com>

On Fri, May 19, 2017 at 02:43:26PM +0800, Peter Xu wrote:
> This idea derives from the bug reported:
> 
>   https://bugzilla.redhat.com/show_bug.cgi?id=1439147
> 
> It is not a extremely critical bug, since as long as the user uses
> libvirt to migrate, we won't have such an issue at all (we'll have
> identical command line parameters for QEMU). However it can be an
> severe one, since it caused data loss (source VM will quit assuming
> that destination VM is good, while it is not). So it would be good we
> fix it. Meanwhile, imho the return path may be used for other things
> as well in the future.
> 
> This series proposed a solution for the bug - let's enable return path
> even for precopy when possible, then source can know whether dest is
> good or not, then it can decide to do something better than quit.
> 
> The series is marked as RFC for two reasons:
> 
> One point for RFC is the idea in general that whether we would like to
> enable return path for precopy. I see it okay since after all it's
> optional (so it greatly reduces the chance that QEMU command line user
> will lose the data, and this feature will be automatically off when we
> are using e.g. "exec:" to migrate to a file).
> 
> The other one point is that I converted MigrationState into a QObject
> (actually a QDevice) to let migration codes benefits from some general
> framework advantages.
> 
> I got at least one positive feedback on each of the RFC elements
> mentioned above, so dare I post this to public. Though I guess some
> migration reviewers may be on PTO recently (I just know it :), I still
> decided to post this out for a broader rfc review.
> 
> Smoke test done, and of course I verified this series to fix the bug
> mentioned.
> 
> Please review. Thanks.
> 
> Peter Xu (6):
>   io: only allow return path for socket typed
>   migration: isolate return path on src
>   migration: fix leak of src file on dst
>   migration: shut src return path unconditionally
>   migration: let MigrationState be an QObject
>   migration: enable return path for precopy
> 
>  include/hw/compat.h           |   4 ++
>  include/io/channel.h          |   1 +
>  include/migration/migration.h |  27 ++++++++-
>  include/qemu/typedefs.h       |   1 -
>  io/channel-socket.c           |   1 +
>  migration/migration.c         | 133 +++++++++++++++++++++++++++++++-----------
>  migration/postcopy-ram.c      |   1 -
>  migration/qemu-file-channel.c |   9 +++
>  migration/trace-events        |   4 +-
>  9 files changed, 140 insertions(+), 41 deletions(-)
> 
> -- 
> 2.7.4
> 

CC Laurent as well. Sorry!

-- 
Peter Xu

      parent reply	other threads:[~2017-05-19  6:48 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-19  6:43 [Qemu-devel] [PATCH RFC 0/6] migration: enable return-path for precopy Peter Xu
2017-05-19  6:43 ` [Qemu-devel] [PATCH RFC 1/6] io: only allow return path for socket typed Peter Xu
2017-05-19  8:25   ` Daniel P. Berrange
2017-05-19  8:30     ` Daniel P. Berrange
2017-05-19  9:55       ` Peter Xu
2017-05-19 12:54       ` Dr. David Alan Gilbert
2017-05-19  9:51     ` Peter Xu
2017-05-19 10:03       ` Daniel P. Berrange
2017-05-19 12:51     ` Dr. David Alan Gilbert
2017-05-19 12:56       ` Daniel P. Berrange
2017-05-19 13:02         ` Dr. David Alan Gilbert
2017-05-19 13:13           ` Daniel P. Berrange
2017-05-19 14:33             ` Dr. David Alan Gilbert
2017-05-19 14:51               ` Daniel P. Berrange
2017-05-19 18:41                 ` Dr. David Alan Gilbert
2017-05-22  8:26                   ` Daniel P. Berrange
2017-05-19  6:43 ` [Qemu-devel] [PATCH RFC 2/6] migration: isolate return path on src Peter Xu
2017-05-30 13:31   ` Juan Quintela
2017-05-19  6:43 ` [Qemu-devel] [PATCH RFC 3/6] migration: fix leak of src file on dst Peter Xu
2017-05-30 15:49   ` Juan Quintela
2017-05-31  9:51   ` Juan Quintela
2017-05-19  6:43 ` [Qemu-devel] [PATCH RFC 4/6] migration: shut src return path unconditionally Peter Xu
2017-05-19 19:28   ` Dr. David Alan Gilbert
2017-05-30 15:50   ` Juan Quintela
2017-05-31  7:31     ` Peter Xu
2017-05-31  7:36       ` Juan Quintela
2017-05-30 15:59   ` Juan Quintela
2017-06-05 20:22   ` Eric Blake
2017-06-06  2:00     ` Peter Xu
2017-05-19  6:43 ` [Qemu-devel] [PATCH RFC 5/6] migration: let MigrationState be an QObject Peter Xu
2017-05-30 15:57   ` Juan Quintela
2017-05-31  7:33     ` Peter Xu
2017-05-19  6:43 ` [Qemu-devel] [PATCH RFC 6/6] migration: enable return path for precopy Peter Xu
2017-05-30 15:59   ` Juan Quintela
2017-05-31  7:38     ` Peter Xu
2017-05-31  7:43       ` Juan Quintela
2017-05-31  8:04         ` Peter Xu
2017-05-31  8:12           ` Juan Quintela
2017-05-19  6:48 ` Peter Xu [this message]

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=20170519064819.GA14679@pxdev.xzpeter.org \
    --to=peterx@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).