From: Paolo Bonzini <pbonzini@redhat.com>
To: Nick Thomas <nick@bytemark.co.uk>,
"Qemu-devel@nongnu.org" <Qemu-devel@nongnu.org>
Cc: kvm@vger.kernel.org
Subject: Re: [Qemu-devel] AMD Opteron 6276 to Intel Xeon E5645 live migration failure
Date: Fri, 28 Feb 2014 13:57:06 +0100 [thread overview]
Message-ID: <531087A2.7070604@redhat.com> (raw)
In-Reply-To: <53107E2E.10201@bytemark.co.uk>
Il 28/02/2014 13:16, Nick Thomas ha scritto:
> I'd love to get this working, but I'm a little ignorant on where to
> begin, or even if it's possible at all. Are these CPUs just too old, or
> is a fixup missing in qemu (or kvm)?
It's the latter (in kvm). Note that for migration to work, especially
for such different models, you have to disable CPU features that aren't
present in both models. In general the way to do this is to add "-cpu".
I'd start debugging with "-cpu kvm64" on both sides.
Paolo
next prev parent reply other threads:[~2014-02-28 12:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 12:16 [Qemu-devel] AMD Opteron 6276 to Intel Xeon E5645 live migration failure Nick Thomas
2014-02-28 12:57 ` Paolo Bonzini [this message]
2014-02-28 13:15 ` Nick Thomas
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=531087A2.7070604@redhat.com \
--to=pbonzini@redhat.com \
--cc=Qemu-devel@nongnu.org \
--cc=kvm@vger.kernel.org \
--cc=nick@bytemark.co.uk \
/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).