From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 203845] Can't run qemu/kvm on 5.0.0 kernel (NULL pointer dereference)
Date: Fri, 07 Jun 2019 18:46:47 +0000 [thread overview]
Message-ID: <bug-203845-28872-3CSYX29XoN@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-203845-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=203845
Sean Christopherson (sean.j.christopherson@intel.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sean.j.christopherson@intel
| |.com
--- Comment #1 from Sean Christopherson (sean.j.christopherson@intel.com) ---
The EIP and code stream puts this at the following line in
mmu_alloc_direct_roots():
vcpu->arch.mmu->pae_root[i] = root | PT_PRESENT_MASK;
The code in question is only encountered on a 32-bit KVM with two-dimensional
paging (TDP) is disabled, i.e. without AMD's Nested Page Tables, which fits
your setup (i686-pae on Athlon). What I can't figure out is how pae_root would
be NULL in this scenario. There is one flow that I think could theoretically
result in a NULL pae_root, but it would require using nested virtualization,
which doesn't seem to be the case here.
I tried to test my theory but running a 32-bit KVM without TDP just hangs for
me, i.e. it appears to be broken on Intel VMX at least as far back as v4.20.
What was the last kernel that did work on your system? That might help narrow
down when things went awry. In the meantime, I'll try to debug/bisect the
issue I'm seeing as time allows.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2019-06-07 18:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 15:57 [Bug 203845] New: Can't run qemu/kvm on 5.0.0 kernel (NULL pointer dereference) bugzilla-daemon
2019-06-07 18:46 ` bugzilla-daemon [this message]
2019-06-08 17:36 ` [Bug 203845] " bugzilla-daemon
2019-06-13 9:49 ` bugzilla-daemon
2019-06-13 14:30 ` bugzilla-daemon
2019-07-16 16:34 ` bugzilla-daemon
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=bug-203845-28872-3CSYX29XoN@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).