From: Paolo Bonzini <pbonzini@redhat.com>
To: Valentine Sinitsyn <valentine.sinitsyn@gmail.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
kvm@vger.kernel.org
Subject: Re: Nested paging in nested SVM setup
Date: Wed, 20 Aug 2014 08:55:01 +0200 [thread overview]
Message-ID: <53F44645.2000708@redhat.com> (raw)
In-Reply-To: <53F44440.6070408@gmail.com>
Il 20/08/2014 08:46, Valentine Sinitsyn ha scritto:
>
> You can see the problem here: the code tries to access APIC MMIO
> register, which is trapped by KVM's MMU code (at nested page table
> walk). During MMIO access emulation, KVM decides to inject 0x23c
> exception (which looks wrong, as there is no exception with this number
> defined). After that things become flawed (pay attention to empty reason
> in the last line; the VMCB is certainly not in the state KVM
> expects/supports).
>
> I'm no KVM expert, and will be grateful for debugging suggestions (or
> maybe even assistance).
Is the 0x23c always the same? Can you try this patch?
diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
index 204422de3fed..194e9300a31b 100644
--- a/arch/x86/kvm/x86.c
+++ b/arch/x86/kvm/x86.c
@@ -346,6 +346,7 @@ static void kvm_multiple_exception(struct kvm_vcpu *vcpu,
kvm_make_request(KVM_REQ_EVENT, vcpu);
+ WARN_ON(nr > 0x1f);
if (!vcpu->arch.exception.pending) {
queue:
vcpu->arch.exception.pending = true;
Paolo
next prev parent reply other threads:[~2014-08-20 6:55 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 11:36 Nested paging in nested SVM setup Valentine Sinitsyn
2014-06-18 12:47 ` Jan Kiszka
2014-06-18 16:59 ` Valentine Sinitsyn
2014-06-19 9:32 ` Paolo Bonzini
2014-06-19 5:03 ` Valentine Sinitsyn
2014-08-20 6:46 ` Valentine Sinitsyn
2014-08-20 6:55 ` Paolo Bonzini [this message]
2014-08-20 7:37 ` Valentine Sinitsyn
2014-08-20 8:11 ` Paolo Bonzini
2014-08-20 9:49 ` Valentine Sinitsyn
2014-08-21 6:28 ` Valentine Sinitsyn
2014-08-21 8:48 ` Valentine Sinitsyn
2014-08-21 11:04 ` Paolo Bonzini
2014-08-21 11:06 ` Jan Kiszka
2014-08-21 11:12 ` Valentine Sinitsyn
2014-08-21 11:16 ` Valentine Sinitsyn
2014-08-21 11:24 ` Paolo Bonzini
2014-08-21 12:28 ` Valentine Sinitsyn
2014-08-21 12:38 ` Valentine Sinitsyn
2014-08-21 13:40 ` Valentine Sinitsyn
2014-09-01 17:41 ` Paolo Bonzini
2014-09-01 19:21 ` Valentine Sinitsyn
2014-09-02 8:25 ` Paolo Bonzini
2014-09-02 9:16 ` Valentine Sinitsyn
2014-09-02 11:21 ` Paolo Bonzini
2014-09-02 11:26 ` Valentine Sinitsyn
2014-08-21 17:35 ` Valentine Sinitsyn
2014-08-21 20:31 ` Paolo Bonzini
2014-08-22 4:33 ` Valentine Sinitsyn
2014-08-22 8:53 ` Paolo Bonzini
2014-09-01 16:11 ` Paolo Bonzini
2014-09-01 17:04 ` Paolo Bonzini
2014-09-02 6:09 ` Valentine Sinitsyn
2014-09-02 6:21 ` Valentine Sinitsyn
2014-09-02 9:45 ` Paolo Bonzini
2014-09-02 9:53 ` Valentine Sinitsyn
2014-09-02 11:48 ` Paolo Bonzini
2014-09-02 10:31 ` Valentine Sinitsyn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53F44645.2000708@redhat.com \
--to=pbonzini@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=valentine.sinitsyn@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.