On Wed, Mar 4, 2015 at 12:04 PM, Bandan Das wrote:
> Wincy Van writes:
>
>> On Wed, Mar 4, 2015 at 1:39 AM, Bandan Das wrote:
>>> Wincy Van writes:
>>>
In commit 3af18d9c5fe9 ("KVM: nVMX: Prepare for using hardware MSR
bitmap"),
we are setting MSR_BITMAP in prepare_vmcs02 if we
Wincy Van writes:
> On Wed, Mar 4, 2015 at 1:39 AM, Bandan Das wrote:
>> Wincy Van writes:
>>
>>> In commit 3af18d9c5fe9 ("KVM: nVMX: Prepare for using hardware MSR bitmap"),
>>> we are setting MSR_BITMAP in prepare_vmcs02 if we should use hardware. This
>>> is not enough since the field will b
On Wed, Mar 4, 2015 at 1:39 AM, Bandan Das wrote:
> Wincy Van writes:
>
>> In commit 3af18d9c5fe9 ("KVM: nVMX: Prepare for using hardware MSR bitmap"),
>> we are setting MSR_BITMAP in prepare_vmcs02 if we should use hardware. This
>> is not enough since the field will be modified by following vmx
Wincy Van writes:
> In commit 3af18d9c5fe9 ("KVM: nVMX: Prepare for using hardware MSR bitmap"),
> we are setting MSR_BITMAP in prepare_vmcs02 if we should use hardware. This
> is not enough since the field will be modified by following vmx_set_efer.
>
> Fix this by setting vmx_msr_bitmap_nested
In commit 3af18d9c5fe9 ("KVM: nVMX: Prepare for using hardware MSR bitmap"),
we are setting MSR_BITMAP in prepare_vmcs02 if we should use hardware. This
is not enough since the field will be modified by following vmx_set_efer.
Fix this by setting vmx_msr_bitmap_nested in vmx_set_msr_bitmap if vcpu