Jan Kiszka <jan.kiszka@xxxxxxxxxxx> writes: > On 2014-03-20 04:28, Bandan Das wrote: >> Some Type 1 hypervisors such as XEN won't enable VMX without it present >> >> Signed-off-by: Bandan Das <bsd@xxxxxxxxxx> >> --- >> arch/x86/kvm/vmx.c | 3 ++- >> 1 file changed, 2 insertions(+), 1 deletion(-) >> >> diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c >> index 3927528..26c1d38 100644 >> --- a/arch/x86/kvm/vmx.c >> +++ b/arch/x86/kvm/vmx.c >> @@ -2273,7 +2273,8 @@ static __init void nested_vmx_setup_ctls_msrs(void) >> nested_vmx_pinbased_ctls_high &= ~PIN_BASED_VMX_PREEMPTION_TIMER; >> } >> nested_vmx_exit_ctls_high |= (VM_EXIT_ALWAYSON_WITHOUT_TRUE_MSR | >> - VM_EXIT_LOAD_IA32_EFER | VM_EXIT_SAVE_IA32_EFER); >> + VM_EXIT_LOAD_IA32_EFER | VM_EXIT_SAVE_IA32_EFER | >> + VM_EXIT_ACK_INTR_ON_EXIT); >> >> /* entry controls */ >> rdmsr(MSR_IA32_VMX_ENTRY_CTLS, >> > > Shouldn't this come after patch 2? Right, that makes sense. Will fix in v2. > Jan -- 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