From: Nadav Amit <nadav.amit@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Sebastian Rachuj <rachus@web.de>,
rkrcmar@redhat.com, tglx@linutronix.de, mingo@redhat.com,
hpa@zytor.com, x86@kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: kvm_intel fails to load on Conroe CPUs running Linux 4.12
Date: Mon, 7 Aug 2017 10:12:33 -0700 [thread overview]
Message-ID: <BF661608-B598-498F-9FDF-94B9D9DE722F@gmail.com> (raw)
In-Reply-To: <596b1df7-7fec-4acf-f19a-67ed4e1ba150@redhat.com>
Paolo Bonzini <pbonzini@redhat.com> wrote:
> On 06/08/2017 23:23, Sebastian Rachuj wrote:
>> On 06.08.2017 23:10, Paolo Bonzini wrote:
>>> On 05/08/2017 21:26, Sebastian Rachuj wrote:
>>>> Dear linux developers,
>>>>
>>>> since my upgrade from linux 4.11 to linux 4.12 the "kvm_intel" module
>>>> does not load correctly anymore. "Modprobing" the kernel module gives an
>>>> Input/Output error. It seems to be related to the CPU architecture and
>>>> (to my knowledge) affects Conroe CPUs. I did a bisect and found the
>>>> following commit as the guilty one:
>>>
>>> What is your cpuinfo? I tested on a Conroe Xeon X3220 (family 6,
>>> model 15, stepping 11) when I posted that patch, and it did have virtual
>>> NMIs.
>>
>> Thank you for looking into the issue. My cpuinfo is as follows:
>
> Looks like Intel was already differentiating virtualization features
> across SKUs. Please run the attached script as root to see what other
> things are different (apparently) between non-Xeon and Xeon Conroes.
There may be another explanation. If I remember correctly from my days in
Intel, Intel initially sold CMWA (Conroe) B-step. The next step, E-step,
introduced a couple of new features, which may have included vNMI.
The CPU of Sebastian appears to be B1 according to cpuinfo.
Nadav
next prev parent reply other threads:[~2017-08-07 17:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-05 19:26 Sebastian Rachuj
2017-08-06 21:10 ` Paolo Bonzini
2017-08-06 21:23 ` Sebastian Rachuj
2017-08-07 9:43 ` Paolo Bonzini
2017-08-07 17:12 ` Nadav Amit [this message]
2017-08-07 17:17 ` Sebastian Rachuj
2017-08-07 17:50 ` Paolo Bonzini
2017-08-07 18:43 ` Sebastian Rachuj
2017-08-08 21:46 ` Niall Walsh
[not found] <35eda6a9-086e-f899-e131-288f2346effe@wiesinger.com>
2017-08-17 21:14 ` Gerhard Wiesinger
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=BF661608-B598-498F-9FDF-94B9D9DE722F@gmail.com \
--to=nadav.amit@gmail.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rachus@web.de \
--cc=rkrcmar@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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
all inboxes | Powered by JetHome®