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! >
