From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: William Dauchy <wdauchy@gmail.com>
Cc: Igor Mammedov <imammedo@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
pbonzini@redhat.com
Subject: Re: [Qemu-devel] qemu live migration error from 2.0 to 2.1
Date: Tue, 5 Aug 2014 19:57:39 +0100 [thread overview]
Message-ID: <20140805185739.GD2340@work-vm> (raw)
In-Reply-To: <CAJ75kXa+3--DrRuHUM5LFMhLyjc7DG9shZ7KTC+msjSvZ7EoPg@mail.gmail.com>
(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?
Dave
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2014-08-05 18:57 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 [this message]
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
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=20140805185739.GD2340@work-vm \
--to=dgilbert@redhat.com \
--cc=imammedo@redhat.com \
--cc=pbonzini@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.