From: Paolo Bonzini <pbonzini@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>,
William Dauchy <wdauchy@gmail.com>
Cc: Igor Mammedov <imammedo@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] qemu live migration error from 2.0 to 2.1
Date: Wed, 06 Aug 2014 09:47:36 +0200 [thread overview]
Message-ID: <53E1DD98.8070108@redhat.com> (raw)
In-Reply-To: <20140805185739.GD2340@work-vm>
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
next prev parent reply other threads:[~2014-08-06 7:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 17:36 [Qemu-devel] qemu live migration error from 2.0 to 2.1 William Dauchy
2014-08-05 18:57 ` Dr. David Alan Gilbert
2014-08-05 19:39 ` William Dauchy
2014-08-06 6:16 ` Markus Armbruster
2014-08-06 7:49 ` Paolo Bonzini
2014-08-06 9:09 ` William Dauchy
2014-08-06 7:47 ` Paolo Bonzini [this message]
2014-08-06 9:06 ` William Dauchy
2014-08-06 9:17 ` Dr. David Alan Gilbert
2014-08-06 9:27 ` William Dauchy
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=53E1DD98.8070108@redhat.com \
--to=pbonzini@redhat.com \
--cc=dgilbert@redhat.com \
--cc=imammedo@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wdauchy@gmail.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).