From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 107561] New: 4.2 breaks PCI passthrough in QEMU/KVM
Date: Mon, 09 Nov 2015 12:18:07 +0000 [thread overview]
Message-ID: <bug-107561-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=107561
Bug ID: 107561
Summary: 4.2 breaks PCI passthrough in QEMU/KVM
Product: Virtualization
Version: unspecified
Kernel Version: 4.2
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: kvm
Assignee: virtualization_kvm@kernel-bugs.osdl.org
Reporter: fhorn50@gmail.com
Regression: No
QEMU/KVM VM's using PCI pass-through are taking a long time to boot, or never
booting. The issue is only present when the VM has more then ~2.5G of ram. I
was able to get a VM with 6G to boot, but I had to let it run overnight.
More info can be found in this thread:
https://bbs.archlinux.org/viewtopic.php?id=203240
Someone in the forum seems to have narrowed it down to a a set of commits
regarding kvm and mtrr in 4.1-rc2 that are in the mainline kernel as of 4.2.
Specifically commit fa61213746a706dd975661151c35795ca4dd82c2 KVM: MTRR:
simplify kvm_mtrr_get_guest_memory_type.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2015-11-09 12:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-09 12:18 bugzilla-daemon [this message]
2015-11-12 22:20 ` [Bug 107561] 4.2 breaks PCI passthrough in QEMU/KVM bugzilla-daemon
2015-11-13 0:43 ` bugzilla-daemon
2015-11-16 2:12 ` bugzilla-daemon
2015-11-21 10:03 ` bugzilla-daemon
2015-11-22 23:45 ` bugzilla-daemon
2015-11-22 23:49 ` bugzilla-daemon
2015-11-22 23:51 ` bugzilla-daemon
2015-11-23 18:40 ` bugzilla-daemon
2015-12-10 21:22 ` bugzilla-daemon
2015-12-10 21:24 ` bugzilla-daemon
2015-12-10 21:51 ` bugzilla-daemon
2015-12-10 22:23 ` bugzilla-daemon
2015-12-11 22:01 ` bugzilla-daemon
2015-12-12 5:52 ` bugzilla-daemon
2015-12-14 15:56 ` 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-107561-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