KVM: VMX: Don't kill the VM on an unexpected #VE

Don't terminate the VM on an unexpected #VE, as it's extremely unlikely
the #VE is fatal to the guest, and even less likely that it presents a
danger to the host.  Simply resume the guest on "failure", as the #VE info
page's BUSY field will prevent converting any more EPT Violations to #VEs
for the vCPU (at least, that's what the BUSY field is supposed to do).

Signed-off-by: Sean Christopherson <seanjc@google.com>
Message-ID: <20240518000430.1118488-8-seanjc@google.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

diff --git a/arch/x86/kvm/vmx/vmx.c b/arch/x86/kvm/vmx/vmx.c
index 51b2cd13250a2d232dfff04341a345c1be967303..069fbbc1e04a0077b150b0c694693dd3e5e371d3 100644 (file)
--- a/arch/x86/kvm/vmx/vmx.c
+++ b/arch/x86/kvm/vmx/vmx.c
@@ -5217,8 +5217,8 @@ static int handle_exception_nmi(struct kvm_vcpu *vcpu)
        if (is_invalid_opcode(intr_info))
                return handle_ud(vcpu);
 
-       if (KVM_BUG_ON(is_ve_fault(intr_info), vcpu->kvm))
-               return -EIO;
+       if (WARN_ON_ONCE(is_ve_fault(intr_info)))
+               return 1;
 
        error_code = 0;
        if (intr_info & INTR_INFO_DELIVER_CODE_MASK)