kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 43501] all 32bit binaries produce "Illegal Instruction" after KVM migration from AMD -> Intel host
Date: Sun, 17 Jun 2012 23:28:25 +0000 (UTC)	[thread overview]
Message-ID: <20120617232825.2EAB211FBA4@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-43501-28872@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=43501





--- Comment #3 from Paul Zimdars <pzimdars@gmail.com>  2012-06-17 23:28:24 ---
Trying the above options results in us being unable to start the guest on the
AMD host in order to test migration. It complains that guest cpu is not
compatible with host CPU.

The only method that works is by creating our own profile and adding it to
cpu-model definition on both the AMD and Intel hosts:

[cpudef]
   name = "cpu64-rhel6-dsio"
   level = "4"
   vendor = "AuthenticAMD"
   family = "6"
   model = "13"
   stepping = "3"
   feature_edx = "sse2 sse fxsr mmx clflush pse36 cmov mca pge mtrr apic cx8
mce pae msr tsc pse de fpu"
   feature_ecx = "cx16"
   extfeature_edx = "lm fxsr mmx nx cmov pge syscall apic cx8 mce pae msr tsc
pse de fpu"
   extfeature_ecx = "lahf_lm"
   xlevel = "0x8000000A"
   model_id = "QEMU Virtual CPU version (cpu64-rhel6)"

We can then migrate the VM but we still encounter the same issue.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

  parent reply	other threads:[~2012-06-17 23:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-17  1:04 [Bug 43501] New: all 32bit binaries produce "Illegal Instruction" after KVM migration from AMD -> Intel host bugzilla-daemon
2012-06-17  9:56 ` [Bug 43501] " bugzilla-daemon
2012-06-17 10:05 ` bugzilla-daemon
2012-06-17 23:28 ` bugzilla-daemon [this message]
2012-06-18  2:52 ` bugzilla-daemon
2012-06-18 11:22 ` bugzilla-daemon
2012-06-18 12:44 ` bugzilla-daemon
2012-08-29 14:22 ` bugzilla-daemon

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=20120617232825.2EAB211FBA4@bugzilla.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=kvm@vger.kernel.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).