[Bug 220631] kernel crash in kvm_intel module on Xeon Silver 4314s

[bugzilla-daemon@kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=220631

Sean Christopherson (seanjc@google.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |seanjc@google.com

--- Comment #4 from Sean Christopherson (seanjc@google.com) ---
This is due to a known a CPU/ucode bug where some Intel CPUs generate spurious
#VEs.


[  +0.000151] kvm: #VE 65dbc7f8
[  +0.000154] kvm: #VE 65dbc7f8, spte[4] = 0x8010000418c52807, spte[3] =
0x801000045b676807, spte[2] = 0x86100023d0000bf7

The "fix" is to disable CONFIG_KVM_INTEL_PROVE_VE.  KVM_INTEL_PROVE_VE isn't
intended for production use (it's akin to PROVE_LOCKING), and the help text
even calls out that some CPUs generate spurious #VEs.

config KVM_INTEL_PROVE_VE
        bool "Check that guests do not receive #VE exceptions"
        depends on KVM_INTEL && EXPERT
        help
          Checks that KVM's page table management code will not incorrectly
          let guests receive a virtualization exception.  Virtualization
          exceptions will be trapped by the hypervisor rather than injected
          in the guest.

          Note: some CPUs appear to generate spurious EPT Violations #VEs
          that trigger KVM's WARN, in particular with eptad=0 and/or nested
          virtualization.

          If unsure, say N.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.