From: Laurent Vivier <lvivier@redhat.com>
To: Greg Kurz <gkurz@linux.vnet.ibm.com>,
Juan Quintela <quintela@redhat.com>
Cc: Amit Shah <amit.shah@redhat.com>,
David Gibson <david@gibson.dropbear.id.au>,
qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 0/2] Fix migration of old pseries
Date: Thu, 18 Feb 2016 21:00:38 +0100 [thread overview]
Message-ID: <56C622E6.20909@redhat.com> (raw)
In-Reply-To: <20160218113211.9760.85475.stgit@bahia.huguette.org>
On 18/02/2016 12:32, Greg Kurz wrote:
> QEMU 2.4 broke the migration of old pseries machine with the addition
> of configuration sections, which are sent unconditionally.
>
> We assume that QEMU 2.3 is more deployed than any newer release (based on
> the versions currently shipped by most distros). This v3 series hence
> reverses the logic from v2: it now fully fixes migration of old pseries
> from/to QEMU 2.3 and provides a manual workaround for the QEMU 2.4/2.4.1/2.5
> case.
>
> With this series, I could migrate the same pseries-2.3 instance in a full
> 2.3->2.6->2.5->2.6->2.4->2.6->2.3 cycle.
>
> ---
>
> Greg Kurz (2):
> spapr: skip configuration section during migration of older machines
> migration: allow machine to enforce configuration section migration
>
>
> hw/core/machine.c | 21 +++++++++++++++++++++
> hw/ppc/spapr.c | 1 +
> include/hw/boards.h | 1 +
> migration/savevm.c | 10 ++++++++--
> qemu-options.hx | 3 ++-
> 5 files changed, 33 insertions(+), 3 deletions(-)
For the series
Tested-by: Laurent Vivier <lvivier@redhat.com>
Results of tests:
pseries-2.3
qemu-2.3.0 -> qemu-master: OK
qemu-2.3.1 -> qemu-master: OK
qemu-2.4.0 -> qemu-master: OK with qom-set
qemu-2.4.1 -> qemu-master: OK with qom-set
qemu-2.5.0 -> qemu-master: OK with qom-set
qemu-master -> qemu-2.3.0: OK
qemu-master -> qemu-2.3.1: OK
qemu-master -> qemu-2.4.0: OK with qom-set
qemu-master -> qemu-2.4.1: OK with qom-set
qemu-master -> qemu-2.5.0: OK with qom-set
qemu-master -> qemu-master: OK
pseries-2.4, pseries-2.5 and pseries-2.6 works well with the patch
applied too.
master is "b527c9b qcow2: Write full header on image creation" + this series
Laurent
next prev parent reply other threads:[~2016-02-18 20:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 11:32 [Qemu-devel] [PATCH v3 0/2] Fix migration of old pseries Greg Kurz
2016-02-18 11:32 ` [Qemu-devel] [PATCH v3 1/2] spapr: skip configuration section during migration of older machines Greg Kurz
2016-02-18 19:57 ` Laurent Vivier
2016-02-23 8:23 ` Juan Quintela
2016-02-18 11:32 ` [Qemu-devel] [PATCH v3 2/2] migration: allow machine to enforce configuration section migration Greg Kurz
2016-02-18 19:57 ` Laurent Vivier
2016-02-23 8:24 ` Juan Quintela
2016-02-18 20:00 ` Laurent Vivier [this message]
2016-02-19 6:42 ` [Qemu-devel] [PATCH v3 0/2] Fix migration of old pseries Greg Kurz
2016-02-19 0:11 ` David Gibson
2016-02-19 7:59 ` Greg Kurz
2016-02-22 1:09 ` David Gibson
2016-02-26 10:49 ` [Qemu-devel] [Qemu-ppc] " Greg Kurz
2016-02-26 11:03 ` David Gibson
2016-02-23 8:31 ` [Qemu-devel] " Juan Quintela
2016-02-23 10:01 ` Greg Kurz
2016-02-23 12:27 ` Greg Kurz
2016-02-19 14:41 ` Laurent Vivier
2016-02-19 16:27 ` Greg Kurz
2016-02-23 15:04 ` Greg Kurz
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=56C622E6.20909@redhat.com \
--to=lvivier@redhat.com \
--cc=amit.shah@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=dgilbert@redhat.com \
--cc=gkurz@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).