There's a warning to alarm the user when the guest has a valid exit_int_info, but really shouldn't have. We don't want that warning when running an L2 guest, because we're in control of the state then anyways, so let's not warn when running nested. Signed-off-by: Alexander Graf <agraf@xxxxxxx> --- arch/x86/kvm/svm.c | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/arch/x86/kvm/svm.c b/arch/x86/kvm/svm.c index 28fcbd0..12ec8ee 100644 --- a/arch/x86/kvm/svm.c +++ b/arch/x86/kvm/svm.c @@ -2404,7 +2404,8 @@ static int handle_exit(struct kvm_vcpu *vcpu) return 0; } - if (is_external_interrupt(svm->vmcb->control.exit_int_info) && + if (!is_nested(svm) && + is_external_interrupt(svm->vmcb->control.exit_int_info) && exit_code != SVM_EXIT_EXCP_BASE + PF_VECTOR && exit_code != SVM_EXIT_NPF && exit_code != SVM_EXIT_TASK_SWITCH) printk(KERN_ERR "%s: unexpected exit_ini_info 0x%x " -- 1.6.0.2 -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
