KVM: VMX: Don't kill the VM on an unexpected #VE
authorSean Christopherson <seanjc@google.com>
Sat, 18 May 2024 00:04:28 +0000 (17:04 -0700)
committerPaolo Bonzini <pbonzini@redhat.com>
Thu, 23 May 2024 16:27:17 +0000 (12:27 -0400)
commit40e8a6901a2c983e3e541a363865e02cf591d458
treeeea7aa3318a0abaa39be6b802b44329bbc0c6ed4
parent803482f472ccc9576c0e606143725d1d8c61019d
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>
arch/x86/kvm/vmx/vmx.c