From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 105841] New: "KVM: x86: apply guest MTRR virtualization on host reserved pages" causes kernel to panic on boot
Date: Mon, 12 Oct 2015 15:35:41 +0000 [thread overview]
Message-ID: <bug-105841-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=105841
Bug ID: 105841
Summary: "KVM: x86: apply guest MTRR virtualization on host
reserved pages" causes kernel to panic on boot
Product: Virtualization
Version: unspecified
Kernel Version: 4.2.0
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: kvm
Assignee: virtualization_kvm@kernel-bugs.osdl.org
Reporter: vapier@gentoo.org
Regression: Yes
Created attachment 190041
--> https://bugzilla.kernel.org/attachment.cgi?id=190041&action=edit
kernel config
after upgrading to linux-4.2, i found my system no longer booted -- it paniced
pretty early on. after bisecting it down, it started with:
commit fd717f11015f673487ffc826e59b2bad69d20fe5
KVM: x86: apply guest MTRR virtualization on host reserved pages
going back to the linux-4.2 release, if i revert these commits, things boot:
fd717f11015f673487ffc826e59b2bad69d20fe5
e098223b789b4a618dacd79e5e0dad4a9d5018d1
3c2e7f7de3240216042b61073803b61b9b3cfb22
i needed all three because the other two started using code from the first bad
commit.
i'm using a AMD Phenom(tm) II X4 980 Processor. having trouble getting a panic
log (no serial port). will try to manually offload it.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2015-10-12 15:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-12 15:35 bugzilla-daemon [this message]
2015-10-12 15:36 ` [Bug 105841] "KVM: x86: apply guest MTRR virtualization on host reserved pages" causes kernel to panic on boot bugzilla-daemon
2015-10-12 15:37 ` bugzilla-daemon
2015-10-13 7:37 ` 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-105841-28872@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