forked from Minki/linux
KVM: nVMX: Fix bug preventing more than two levels of nesting
The nested VMX feature is supposed to fully emulate VMX for the guest. This (theoretically) not only allows it to run its own guests, but also also to further emulate VMX for its own guests, and allow arbitrarily deep nesting. This patch fixes a bug (discovered by Kevin Tian) in handling a VMLAUNCH by L2, which prevented deeper nesting. Deeper nesting now works (I only actually tested L3), but is currently *absurdly* slow, to the point of being unusable. Signed-off-by: Nadav Har'El <nyh@il.ibm.com> Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
This commit is contained in:
parent
7f4382e8fd
commit
509c75ea19
@ -5694,8 +5694,8 @@ static int vmx_handle_exit(struct kvm_vcpu *vcpu)
|
||||
if (vmx->nested.nested_run_pending)
|
||||
kvm_make_request(KVM_REQ_EVENT, vcpu);
|
||||
|
||||
if (exit_reason == EXIT_REASON_VMLAUNCH ||
|
||||
exit_reason == EXIT_REASON_VMRESUME)
|
||||
if (!is_guest_mode(vcpu) && (exit_reason == EXIT_REASON_VMLAUNCH ||
|
||||
exit_reason == EXIT_REASON_VMRESUME))
|
||||
vmx->nested.nested_run_pending = 1;
|
||||
else
|
||||
vmx->nested.nested_run_pending = 0;
|
||||
|
Loading…
Reference in New Issue
Block a user