From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:40882)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <william@gandi.net>) id 1Xykgm-0007eP-Ja
	for qemu-devel@nongnu.org; Wed, 10 Dec 2014 12:04:44 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <william@gandi.net>) id 1Xykge-0004RE-Cs
	for qemu-devel@nongnu.org; Wed, 10 Dec 2014 12:04:36 -0500
Received: from mail4.gandi.net ([217.70.183.210]:46644)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <william@gandi.net>) id 1Xykge-0004Qp-6w
	for qemu-devel@nongnu.org; Wed, 10 Dec 2014 12:04:28 -0500
Date: Wed, 10 Dec 2014 18:04:25 +0100
From: William Dauchy <william@gandi.net>
Message-ID: <20141210170425.GQ14440@gandi.net>
References: <20141209183701.GI14440@gandi.net> <20141209185517.GH5272@work-vm>
	<20141209232546.GM14440@gandi.net> <20141210085852.GA2311@work-vm>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="7a4X6VOqfbl9xMrG"
Content-Disposition: inline
In-Reply-To: <20141210085852.GA2311@work-vm>
Subject: Re: [Qemu-devel] migration from qemu2.1.2 to qemu2.2
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>


--7a4X6VOqfbl9xMrG
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Dec10 08:58, Dr. David Alan Gilbert wrote:
> Yes, you've got to keep the same machine type to do a live migration;
> think of it like keeping the same motherboard/cpu combination in a real
> machine - we can't squash the state from one shape machine into
> a different shape machine without the guest getting very confused.

I now have done some other tests:

with source -M pc-i440fx-2.1
and target -M pc-i440fx-2.1

still getting:

Unknown combination of migration flags: 0
warning: error while loading state section id 2

--=20
William

--7a4X6VOqfbl9xMrG
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iEYEARECAAYFAlSIfRkACgkQ1I6eqOUidQFlxwCfej3wS5baaW8XAolMympsn3eP
CVwAoIfTZQNCql+5lcxxgILwXPrNyU+j
=4M3X
-----END PGP SIGNATURE-----

--7a4X6VOqfbl9xMrG--