From: Paolo Bonzini <pbonzini@redhat.com>
To: "KVM list" <kvm@vger.kernel.org>,
"Fabian Grünbichler" <f.gruenbichler@proxmox.com>
Subject: Re: [PATCH] KVM: VMX: require virtual NMI support
Date: Mon, 30 Oct 2017 09:34:00 +0100 [thread overview]
Message-ID: <69ffa991-34e9-fb12-a52f-22170f1e5bf5@redhat.com> (raw)
In-Reply-To: <20171027083808.grmr2anywk4rcwel@nora.maurer-it.com>
On 27/10/2017 10:38, Fabian Grünbichler wrote:
> On Wed, Oct 25, 2017 at 11:07:54AM +0200, Fabian Grünbichler wrote:
>> On Wed, Oct 25, 2017 at 10:40:11AM +0200, Paolo Bonzini wrote:
>>> On 25/10/2017 10:12, Fabian Grünbichler wrote:
>>>> any update on this? 4.14 is soon out the door, and 4.13 with the
>>>> breaking change just got released as part of Ubuntu 17.10 / Artful..
>>>
>>> I had posted a patch on October 10th, but no one replied with test results.
>>>
>>
>> sorry, missed the (second) thread.
>>
>> currently building, will get back with test results ASAP.
>
> so, while we haven't found any affected hardware in our test lab (not
> even in the to-be-discarded pile), feedback from users has been positive
> across the board for the following CPUs which were not able to use KVM
> without the patch:
>
> - Intel Xeon 3040 (Conroe)
> - Intel Xeon 5050 (Dempsey)
> - Intel Xeon 5130 (Woodcrest)
> - Intel Xeon E3-1256L V2 (Ivy Bridge)
Ivy Bridge definitely worked without the patch.
Can you send me a link to the exact patch you applied (pastebin or
something like that)?
Thanks,
Paolo
> - Intel Core 2 Duo T5600 (Merom)
>
> with no negative reports so far[1]. if you want more detailed
> information like vmxcap or cpuinfo, those can probably be requested.
>
> the kernel used is based on Ubuntu's 4.13.0-16.19 kernel, which is based
> on 4.13.4.
>
> I'll monitor the thread for more feedback one way or another, and
> forward any problems that seem relevant.
>
> thanks!
>
next prev parent reply other threads:[~2017-10-30 8:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 12:38 [PATCH] KVM: VMX: require virtual NMI support Paolo Bonzini
2017-04-03 11:46 ` David Hildenbrand
2017-09-13 17:23 ` Zdenek Kaspar
2017-09-13 20:34 ` Paolo Bonzini
2017-10-25 8:12 ` Fabian Grünbichler
2017-10-25 8:40 ` Paolo Bonzini
2017-10-25 9:07 ` Fabian Grünbichler
2017-10-27 8:38 ` Fabian Grünbichler
2017-10-30 8:34 ` Paolo Bonzini [this message]
2017-10-30 8:52 ` Fabian Grünbichler
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=69ffa991-34e9-fb12-a52f-22170f1e5bf5@redhat.com \
--to=pbonzini@redhat.com \
--cc=f.gruenbichler@proxmox.com \
--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).