From: Paolo Bonzini <pbonzini@redhat.com>
To: Alexandre DERUMIER <aderumier@odiso.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Unable to migrate pc-i440fx-2.4 KVM guest from QEMU 2.5.0 to QEMU 2.4.1
Date: Thu, 18 Feb 2016 19:24:22 +0100 [thread overview]
Message-ID: <56C60C56.3010803@redhat.com> (raw)
In-Reply-To: <1374533797.187583648.1455818058856.JavaMail.zimbra@oxygem.tv>
On 18/02/2016 18:54, Alexandre DERUMIER wrote:
> Hi,
>
> I (and promox users) have same problem than this bugreport
>
> https://bugs.launchpad.net/qemu/+bug/1536487
> https://forum.proxmox.com/threads/cant-live-migrate-after-dist-upgrade.26097/
>
> Migrating from qemu 2.5 with pc-i440fx-2.4 to qemu 2.4.1 don't work.
> qemu-system-x86_64: error while loading state for instance 0x0 of device 'fw_cfg'
While I agree that this is a bug worth fixing, note that in general
migration from new to old versions is _not_ supported. Usually it
works, but not always, and sometimes it's not a bug.
Machine types are only meant to support migration from old versions to new.
Paolo
next prev parent reply other threads:[~2016-02-18 18:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 17:54 [Qemu-devel] Unable to migrate pc-i440fx-2.4 KVM guest from QEMU 2.5.0 to QEMU 2.4.1 Alexandre DERUMIER
2016-02-18 18:13 ` Laszlo Ersek
2016-02-18 18:24 ` Paolo Bonzini [this message]
2016-02-18 19:32 ` Laszlo Ersek
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=56C60C56.3010803@redhat.com \
--to=pbonzini@redhat.com \
--cc=aderumier@odiso.com \
--cc=qemu-devel@nongnu.org \
/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).