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: Mon, 18 Jun 2012 11:22:21 +0000 (UTC) [thread overview]
Message-ID: <20120618112221.E901711FBA4@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-43501-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=43501
--- Comment #5 from Avi Kivity <avi@redhat.com> 2012-06-18 11:22:21 ---
I'm not sure that the vendor string is passed correctly.
Please verify that when starting the guest on an Intel host, /proc/cpuinfo
shows AuthenticAMD for vendor_id.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2012-06-18 11:22 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
2012-06-18 2:52 ` bugzilla-daemon
2012-06-18 11:22 ` bugzilla-daemon [this message]
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=20120618112221.E901711FBA4@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 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.