Originally, the L1 hypervisor triggered the following message from L0:
nested_vmx_run: VMCS MSR_{LOAD,STORE} unsupported
This message was removed with commit ff651cb613b4 ("KVM: nVMX: Add
nested msr load/restore algorithm").
It seems likely that this was induced by an attempt to save/restore
MSR_CORE_PERF_GLOBAL_CTRL, since L0 doesn't set the
VM_ENTRY_LOAD_IA32_PERF_GLOBAL_CTRL/VM_EXIT_LOAD_IA32_PERF_GLOBAL_CTRL
bits in L1's VMX capability MSRs. (As an aside: why not?) This MSR is
virtualized in intel_pmu.c, so I would expect the original problem to
be resolved.
On Wed, Dec 21, 2016 at 1:01 AM, David Hildenbrand <david@xxxxxxxxxx> wrote:
> Am 21.12.2016 um 01:34 schrieb Jim Mattson:
>>
>> This reverts commit bc6134942dbbf31c25e9bd7c876be5da81c9e1ce.
>>
>> A CPUID instruction executed in VMX non-root mode always causes a
>> VM-exit, regardless of the leaf being queried.
>
>
> Makes sense, but wonder if the original problem has been resolved?
>
> --
>
> David
--
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
