From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:53745) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XEvwu-0001WN-7F for qemu-devel@nongnu.org; Wed, 06 Aug 2014 03:47:58 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XEvwl-0007R3-5R for qemu-devel@nongnu.org; Wed, 06 Aug 2014 03:47:52 -0400 Received: from mx1.redhat.com ([209.132.183.28]:59209) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XEvwk-0007Qx-UD for qemu-devel@nongnu.org; Wed, 06 Aug 2014 03:47:43 -0400 Message-ID: <53E1DD98.8070108@redhat.com> Date: Wed, 06 Aug 2014 09:47:36 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <20140805185739.GD2340@work-vm> In-Reply-To: <20140805185739.GD2340@work-vm> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] qemu live migration error from 2.0 to 2.1 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Dr. David Alan Gilbert" , William Dauchy Cc: Igor Mammedov , QEMU Developers Il 05/08/2014 20:57, Dr. David Alan Gilbert ha scritto: > (CC Paolo) > > * William Dauchy (wdauchy@gmail.com) wrote: >> Hello, >> >> For a qemu live migration from 2.0 to 2.1 I'm getting: >> >> qemu-system-x86_64: Length mismatch: /rom@etc/acpi/tables: 3000 in != 20000 >> qemu-system-x86_64: Unknown ramblock "/table-loader", cannot accept migration >> qemu-system-x86_64: Ack, bad migration stream! >> qemu-system-x86_64: Illegal RAM offset f0e2d500f06000 >> qemu: warning: error while loading state for instance 0x0 of device 'ram' >> qemu-system-x86_64: load of migration failed: Invalid argument >> >> I was wondering if it was a bug or if I was supposed to do something >> to avoid this error. > > That should work. > >> I saw the bug report for qemu1.7 but it's not my case. > > Can you confirm this is on the final 2.1 release (there was a fix that > went in just around rc5). > > What's your command line on both ends? I suspect he's using "-M pc" on both. You must use "-M pc-i440fx-2.0" on both if you're migrating from 2.0 to a different version. Paolo