From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:54726) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aTuV3-0002SB-PE for qemu-devel@nongnu.org; Thu, 11 Feb 2016 11:53:50 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aTuUz-00072x-5a for qemu-devel@nongnu.org; Thu, 11 Feb 2016 11:53:49 -0500 Date: Thu, 11 Feb 2016 16:53:40 +0000 From: "Dr. David Alan Gilbert" Message-ID: <20160211165339.GC2529@work-vm> References: <20160208155947.11480.87951.stgit@bahia.huguette.org> <20160210212612.07123ed3@bahia.huguette.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160210212612.07123ed3@bahia.huguette.org> Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH] spapr: skip configuration section during migration of older machines List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Greg Kurz Cc: Juan Quintela , qemu-ppc@nongnu.org, qemu-devel@nongnu.org, David Gibson * Greg Kurz (gkurz@linux.vnet.ibm.com) wrote: > On Mon, 08 Feb 2016 16:59:47 +0100 > Greg Kurz wrote: > > Since QEMU 2.4, we have a configuration section in the migration stream. > > This must be skipped for older machines, like it is already done for x86. > > > > Ouch ! It is more complex than I thought... the migration of pseries-2.3 > machine is already broken between QEMU-2.3 and QEMU-2.4. So this patch > fixes indeed migration of a pseries-2.3 machine from QEMU-2.3, but it > breaks migration of the same machine from QEMU-2.4 and up. > > Not sure how to deal with that... is it reasonable to assume that > pseries-2.3 running with QEMU-2.3 is the common case ? If so, this > patch would bring more help than harm. Unfortunately we can not fix history, so we have to pick something to fix. So unless there is another reason, then I normally say keep it working between the latest versions of qemu; i.e. if someone is running qemu 2.5 with -M 2.3 then dont break it when they try and migrate to 2.6, even though this would fix an older qemu migrating into 2.6. However, as discussed on irc you might be able to fudge it; for example using qemu_peek_byte to test whether or not you have a configuration section, and making it not error for some machine types. This isn't pretty, but if it's important for you to get the coniguration working then it's the type of trick that might work. Dave > > > Fixes: 61964c23e5ddd5a33f15699e45ce126f879e3e33 > > Cc: qemu-stable@nongnu.org > > Signed-off-by: Greg Kurz > > --- > > hw/ppc/spapr.c | 1 + > > 1 file changed, 1 insertion(+) > > > > diff --git a/hw/ppc/spapr.c b/hw/ppc/spapr.c > > index 5bd8fd3ef842..bca7cb8a5d27 100644 > > --- a/hw/ppc/spapr.c > > +++ b/hw/ppc/spapr.c > > @@ -2446,6 +2446,7 @@ static void spapr_machine_2_3_instance_options(MachineState *machine) > > spapr_machine_2_4_instance_options(machine); > > savevm_skip_section_footers(); > > global_state_set_optional(); > > + savevm_skip_configuration(); > > } > > > > static void spapr_machine_2_3_class_options(MachineClass *mc) > > > > > -- Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK