From: Olaf Hering <olaf@aepfle.de>
To: elahe shekuhi <e.shekuhi@gmail.com>
Cc: xen-devel@lists.xen.org
Subject: Re: xen live migration falied
Date: Thu, 7 Jun 2012 23:44:27 +0200 [thread overview]
Message-ID: <20120607214427.GA30772@aepfle.de> (raw)
In-Reply-To: <CAFuBCagmHxWteZk8DnXCWfTMaPLs7rxYkpBD=nSADjzKvbTNsA@mail.gmail.com>
On Wed, Jun 06, elahe shekuhi wrote:
> (One machine has core i7 processor while another is core 2 quad system).
>
>
> I have searched the net and this list and found a few posts mentioning this
> error, but no solution, not even a hint
> on the source of the problem.
As mentioned by others, for migration (or save/restore) either both
systems have to have identical cpus or the guests view of the cpu has to
be adjusted with the cpuid= config option in the vm config file. In
other words, the "least common denominator" of cpu features has to be
configured.
See my recent post which tries to explain the cpuid= config option:
http://lists.xen.org/archives/html/xen-devel/2012-06/msg00303.html
There is an example in there for xend, and also a link to wikipedia
which has a good list of cpu features. I suggest to boot both systems
with a native kernel and compare the cpu features. Perhaps with
something like this:
grep -wm1 ^flags /proc/cpuinfo | xargs -n1 | sort > /share_dir/core2.txt
grep -wm1 ^flags /proc/cpuinfo | xargs -n1 | sort > /share_dir/i7.txt
diff -u /share_dir/core2.txt /share_dir/i7.txt
I think most of the lines starting with '+' are features which exist
only in i7, which can be hidden with the cpuid= option.
Make sure to install the xen packages from the 12.1 update repository
since they contain two fixes for your environment: an xsave related bug
was fixed, and also guests with a cpuid= option were not restored at all
during system startup.
Olaf
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2012-06-07 21:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-06 7:00 xen live migration falied elahe shekuhi
2012-06-06 7:41 ` Jan Beulich
2012-06-06 8:52 ` Ian Campbell
2012-06-06 18:15 ` elahe shekuhi
2012-06-07 6:42 ` Mark Dokter
2012-06-07 7:57 ` elahe shekuhi
2012-06-07 11:33 ` elahe shekuhi
2012-06-07 18:59 ` Jan Beulich
2012-06-09 8:29 ` elahe shekuhi
2012-06-09 8:47 ` Olaf Hering
2012-06-09 9:54 ` elahe shekuhi
2012-06-07 21:44 ` Olaf Hering [this message]
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=20120607214427.GA30772@aepfle.de \
--to=olaf@aepfle.de \
--cc=e.shekuhi@gmail.com \
--cc=xen-devel@lists.xen.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).