On Thu, Nov 17, 2016 at 01:41:12PM +0100, Paolo Bonzini wrote:
> On 09/11/2016 04:10, Huang, Kai wrote:
>> Hi Greg,
>>
>> Thanks for reporting this issue.
>>
>> I don't have 4.1.y source code tree at hand but after taking a glance
>> looks the commit a3eaa8649e4c6a6afdafaa04b9114fb230617bb1 ("KVM: VMX:
>> Fix commit which broke PML") fixes this by removing vmwrite to
>> SECONDARY_VM_EXEC_CONTROL in vmx_disable_pml, so yes I think this commit
>> can fix this issue.
>>
>> But I think you probably need another commit to fix potential vmwrite
>> error when creating vcpu: 4e59516a12a6ef6dcb660cb3a3f70c64bd60cfec (kvm:
>> vmx: ensure VMCS is current while enabling PML). Peter found and fixed
>> this issue, so I also added him to cc-list.
>>
>> Paolo/Radim, please comment if I made mistake here.
>
> Yes, we should backport both of them. Greg, can you test it? Then I'll
> send the two patches to linux-stable.
Yes, we've been running with both patches internally without problems
for a week or so.
Greg
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
