From: Sebastian Rachuj <rachus@web.de>
To: Paolo Bonzini <pbonzini@redhat.com>,
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 20:43:54 +0200 [thread overview]
Message-ID: <2a05dd6c-0094-ea3f-ae68-265809817a78@web.de> (raw)
In-Reply-To: <6726cf9c-8eb5-8930-fca0-8f5867660847@redhat.com>
On 07.08.2017 19:50, Paolo Bonzini wrote:
> On 07/08/2017 19:17, Sebastian Rachuj wrote:
>>>>
>>>> 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.
>>
>> Here you are, I hope it helps:
>
> Not much to say, unfortunately. It's pretty much the same capabilities
> as a Prescott/Cedar Mill processor, except that it has MSR bitmaps. It
> also lacks FlexPriority compared to the Conroe I had checked.
>
> It's not great that even the revert patch doesn't apply cleanly---this
> is *not* necessarily a boring area of the hypervisor...
>
> Given the rarity of your machine I'm currently leaning towards _not_
> reverting the change. I'll check another non-Xeon Core 2 tomorrow that
> is from December 2008 (IIRC). If that one also lacks vNMI, or if I get
> other reports, I suppose I will have to reconsider that.
That's unfortunate to hear. Just for completeness, I want to mention a
thread in the Archlinux forum, I created, where two other people (Sadar
and losko) also complained about not working KVM [1]. Additionally,
Linux 4.12 has not reached yet reached distributions with a greater
amount of users.
If supporting these chips is too much of a hassle, I will probably have
to buy a new CPU to enjoy KVM support with a current linux kernel.
Anyway, thanks again for figuring this out!
[1]: https://bbs.archlinux.org/viewtopic.php?id=228645
next prev parent reply other threads:[~2017-08-07 18:45 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
2017-08-07 17:17 ` Sebastian Rachuj
2017-08-07 17:50 ` Paolo Bonzini
2017-08-07 18:43 ` Sebastian Rachuj [this message]
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=2a05dd6c-0094-ea3f-ae68-265809817a78@web.de \
--to=rachus@web.de \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--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®