From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 117301] New: Could not insert kvm_intel on dual Xeon X5355
Date: Wed, 27 Apr 2016 11:05:10 +0000 [thread overview]
Message-ID: <bug-117301-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=117301
Bug ID: 117301
Summary: Could not insert kvm_intel on dual Xeon X5355
Product: Virtualization
Version: unspecified
Kernel Version: 3.10.0-327.13.1.el7.x86_64
Hardware: Intel
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: kvm
Assignee: virtualization_kvm@kernel-bugs.osdl.org
Reporter: piotr.pejas@gmail.com
Regression: No
Created attachment 214541
--> https://bugzilla.kernel.org/attachment.cgi?id=214541&action=edit
cpuinfo dmesg
Hi,
I did fresh install of Centos7 on dual socket machine (Xeon X5355) to serve as
kvm host. System is updated. kvm_intel is not loaded on boot.
# dmesg | grep kvm
[ 11.149589] kvm: CPU 0 feature inconsistency!
[ 11.159752] kvm: CPU 3 feature inconsistency!
[ 11.168591] kvm: CPU 3 feature inconsistency!
[ 11.180506] kvm: CPU 3 feature inconsistency!
[ 11.186351] kvm: CPU 3 feature inconsistency!
when I try to load it with modprobe I get:
# modprobe kvm_intel
modprobe: ERROR: could not insert 'kvm_intel': Input/output error
# lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 8
On-line CPU(s) list: 0-7
Thread(s) per core: 1
Core(s) per socket: 4
Socket(s): 2
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 15
Model name: Intel(R) Xeon(R) CPU X5355 @ 2.66GHz
Stepping: 11
CPU MHz: 2659.993
BogoMIPS: 5320.04
Virtualization: VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache: 4096K
NUMA node0 CPU(s): 0-7
# grep 'model name' /proc/cpuinfo
model name : Intel(R) Xeon(R) CPU X5355 @ 2.66GHz
model name : Intel(R) Xeon(R) CPU X5355 @ 2.66GHz
model name : Intel(R) Xeon(R) CPU X5355 @ 2.66GHz
model name : Intel(R) Xeon(R) CPU X5355 @ 2.66GHz
model name : Intel(R) Xeon(R) CPU X5355 @ 2.66GHz
model name : Intel(R) Xeon(R) CPU X5355 @ 2.66GHz
model name : Intel(R) Xeon(R) CPU X5355 @ 2.66GHz
model name : Intel(R) Xeon(R) CPU X5355 @ 2.66GHz
# dmesg | grep microcode
[ 0.000000] CPU0 microcode updated early to revision 0x6b, date = 2010-10-02
[ 0.056027] CPU1 microcode updated early to revision 0x6b, date = 2010-10-02
[ 0.068268] CPU2 microcode updated early to revision 0x6b, date = 2010-10-02
[ 0.165019] CPU5 microcode updated early to revision 0x6b, date = 2010-10-02
[ 0.692463] microcode: CPU0 sig=0x6f7, pf=0x40, revision=0x6b
[ 0.692468] microcode: CPU1 sig=0x6f7, pf=0x40, revision=0x6b
[ 0.692487] microcode: CPU2 sig=0x6f7, pf=0x40, revision=0x6b
[ 0.692510] microcode: CPU3 sig=0x6fb, pf=0x40, revision=0x0
[ 0.692521] microcode: CPU4 sig=0x6fb, pf=0x40, revision=0x0
[ 0.692540] microcode: CPU5 sig=0x6f7, pf=0x40, revision=0x6b
[ 0.692564] microcode: CPU6 sig=0x6fb, pf=0x40, revision=0x0
[ 0.692575] microcode: CPU7 sig=0x6fb, pf=0x40, revision=0x0
[ 0.692675] microcode: Microcode Update Driver: v2.00
<tigran@aivazian.fsnet.co.uk>, Peter Oruba
[ 16.138622] microcode: CPU3 sig=0x6fb, pf=0x40, revision=0x0
[ 16.139616] microcode: CPU3 updated to revision 0xbc, date = 2010-10-03
[ 16.145359] microcode: CPU4 sig=0x6fb, pf=0x40, revision=0x0
[ 16.146348] microcode: CPU4 updated to revision 0xbc, date = 2010-10-03
[ 16.150525] microcode: CPU6 sig=0x6fb, pf=0x40, revision=0x0
[ 16.151520] microcode: CPU6 updated to revision 0xbc, date = 2010-10-03
[ 16.155627] microcode: CPU7 sig=0x6fb, pf=0x40, revision=0x0
[ 16.156622] microcode: CPU7 updated to revision 0xbc, date = 2010-10-03
Please let me know how I can be of more help
Best Regards
Piotr Pejas
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2016-04-27 11:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 11:05 bugzilla-daemon [this message]
2016-04-27 11:55 ` [Bug 117301] Could not insert kvm_intel on dual Xeon X5355 bugzilla-daemon
2016-04-28 16:51 ` bugzilla-daemon
2016-04-29 13:30 ` 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=bug-117301-28872@https.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).