]> git.baikalelectronics.ru Git - kernel.git/commit
x86/kvm/vmx: do not use vm-exit instruction length for fast MMIO when running nested
authorVitaly Kuznetsov <vkuznets@redhat.com>
Thu, 25 Jan 2018 15:37:07 +0000 (16:37 +0100)
committerRadim Krčmář <rkrcmar@redhat.com>
Wed, 31 Jan 2018 17:25:34 +0000 (18:25 +0100)
commit0b0fbdd529a7b6e19798282cd6a5e007326b4133
treeb6fbb28c52ff362013c2ca10763369febb2db1e9
parent976f86d679b3a763e08fe2d69840bdfc3f36b2a1
x86/kvm/vmx: do not use vm-exit instruction length for fast MMIO when running nested

I was investigating an issue with seabios >= 1.10 which stopped working
for nested KVM on Hyper-V. The problem appears to be in
handle_ept_violation() function: when we do fast mmio we need to skip
the instruction so we do kvm_skip_emulated_instruction(). This, however,
depends on VM_EXIT_INSTRUCTION_LEN field being set correctly in VMCS.
However, this is not the case.

Intel's manual doesn't mandate VM_EXIT_INSTRUCTION_LEN to be set when
EPT MISCONFIG occurs. While on real hardware it was observed to be set,
some hypervisors follow the spec and don't set it; we end up advancing
IP with some random value.

I checked with Microsoft and they confirmed they don't fill
VM_EXIT_INSTRUCTION_LEN on EPT MISCONFIG.

Fix the issue by doing instruction skip through emulator when running
nested.

Fixes: 318a40203d50ef81207a1b87af2bce2e01eaf5e1
Suggested-by: Radim Krčmář <rkrcmar@redhat.com>
Suggested-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
Acked-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Radim Krčmář <rkrcmar@redhat.com>
arch/x86/kvm/vmx.c
arch/x86/kvm/x86.c