qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony PERARD <anthony.perard@citrix.com>
To: QEMU-devel <qemu-devel@nongnu.org>
Cc: Amit Shah <amit.shah@redhat.com>,
	Juan Quintela <quintela@redhat.com>,
	Stefano Stabellini <stefano.stabellini@citrix.com>,
	Xen Devel <xen-devel@lists.xen.org>
Subject: Re: [Qemu-devel] [PATCH for-2.4 0/3] Migration regressions with Xen.
Date: Wed, 29 Jul 2015 18:54:16 +0100	[thread overview]
Message-ID: <20150729175416.GN1379@perard.uk.xensource.com> (raw)
In-Reply-To: <1438098885-4339-1-git-send-email-anthony.perard@citrix.com>

This is a critical issue for Xen as migration either with the same version
of QEMU, or from a previous version of QEMU is broken.

Any suggestion on how to move forward?

On Tue, Jul 28, 2015 at 04:54:42PM +0100, Anthony PERARD wrote:
> Hi,
> 
> We've spotted several regression which prevent migration with Xen using the
> same version of QEMU or from a previous version of QEMU (tryied with 2.2).
> 
> Regression have been introduce by at least:
> - df4b1024526cae3479da3492d6371fd4a7324a03
>   migration: create new section to store global state
> - 61964c23e5ddd5a33f15699e45ce126f879e3e33
>   migration: Add configuration section
> 
> The first patch would fix the default case when we use the machine 'xenfv'.
> 
> But we can also use the machine 'pc' and I don't know how to fix this case.
> The second and third patches are a step in the direction of fixing
> migration with the machine 'pc'.
> 
> I have not look at save/restore for PV guest yet.
> 
> Thanks,
> 
> Anthony PERARD (3):
>   migration: Fix regretion for xenfv machine.
>   migration: Fix global state with Xen.
>   migration: Add configuration section to vmstate with xen.
> 
>  hw/i386/pc_piix.c             | 3 +++
>  include/migration/migration.h | 1 +
>  migration/migration.c         | 7 +++++++
>  migration/savevm.c            | 6 ++++++
>  4 files changed, 17 insertions(+)

-- 
Anthony PERARD

  parent reply	other threads:[~2015-07-29 17:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-28 15:54 [Qemu-devel] [PATCH RFC 0/3] Migration regressions with Xen Anthony PERARD
2015-07-28 15:54 ` [Qemu-devel] [PATCH RFC 1/3] migration: Fix regretion for xenfv machine Anthony PERARD
2015-07-28 15:54 ` [Qemu-devel] [PATCH RFC 2/3] migration: Fix global state with Xen Anthony PERARD
2015-07-28 15:54 ` [Qemu-devel] [PATCH RFC 3/3] migration: Add configuration section to vmstate with xen Anthony PERARD
2015-07-29 17:54 ` Anthony PERARD [this message]
2015-07-30 11:06   ` [Qemu-devel] [PATCH for-2.4 0/3] Migration regressions with Xen Juan Quintela
2015-07-30 11:24     ` Stefano Stabellini
2015-07-31  9:59       ` Stefano Stabellini
2015-08-03  5:44         ` Amit Shah
2015-08-03  8:36           ` Dr. David Alan Gilbert
2015-08-03  9:37           ` Stefano Stabellini
2015-08-03 12:45             ` Amit Shah

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=20150729175416.GN1379@perard.uk.xensource.com \
    --to=anthony.perard@citrix.com \
    --cc=amit.shah@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=stefano.stabellini@citrix.com \
    --cc=xen-devel@lists.xen.org \
    /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).