From: David Gibson <david@gibson.dropbear.id.au>
To: Greg Kurz <gkurz@linux.vnet.ibm.com>
Cc: Laurent Vivier <lvivier@redhat.com>,
Juan Quintela <quintela@redhat.com>,
qemu-devel@nongnu.org,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
qemu-ppc@nongnu.org, Amit Shah <amit.shah@redhat.com>
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH v3 0/2] Fix migration of old pseries
Date: Fri, 26 Feb 2016 22:03:02 +1100 [thread overview]
Message-ID: <20160226110302.GB24457@voom.redhat.com> (raw)
In-Reply-To: <20160226114956.7e08af4d@bahia.huguette.org>
[-- Attachment #1: Type: text/plain, Size: 2450 bytes --]
On Fri, Feb 26, 2016 at 11:49:56AM +0100, Greg Kurz wrote:
> On Mon, 22 Feb 2016 12:09:12 +1100
> David Gibson <david@gibson.dropbear.id.au> wrote:
>
> > On Fri, Feb 19, 2016 at 08:59:44AM +0100, Greg Kurz wrote:
> > > On Fri, 19 Feb 2016 11:11:47 +1100
> > > David Gibson <david@gibson.dropbear.id.au> wrote:
> > >
> > > > On Thu, Feb 18, 2016 at 12:32:11PM +0100, 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.
> > > >
> > > > Sorry, I've lost track slightly here. Does this series apply on top
> > > > of, or instead of your earlier series that peeks for the config
> > > > section?
> > > >
> > >
> > > This v3 series applies instead of the v2 that peeks for the config section.
> >
> > Ok, thanks for the clarification.
> >
> > > It was suggested by Laurent during review, and motivated by your decision
> > > to favor fixing 2.3 over 2.4.
> > >
> > > As shown in Laurent's detailed test report, migration from/to 2.3.x now works
> > > out of the box and 2.4.x/2.5 requires qom-set.
> > >
> > > I was also feeling a bit uncomfortable with all these machine properties to
> > > disable the configuration section, which was explicitly coded to be non-optional
> > > according to the changelog of commit 61964c23. The logic inversion in v3 seem
> > > to be friendlier with the configuration section design.
> > >
> > > Juan, could you share your thoughts ?
> >
> > With an ack from Juan I'll be happy to merge this to ppc-for-2.6.
> >
>
> And the patches even got reviewed by Juan ! Please merge ! :)
Ugh, sorry. Thought I already had. Merged now.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-02-26 11:31 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 ` [Qemu-devel] [PATCH v3 0/2] Fix migration of old pseries Laurent Vivier
2016-02-19 6:42 ` 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 [this message]
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=20160226110302.GB24457@voom.redhat.com \
--to=david@gibson.dropbear.id.au \
--cc=amit.shah@redhat.com \
--cc=dgilbert@redhat.com \
--cc=gkurz@linux.vnet.ibm.com \
--cc=lvivier@redhat.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).