From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 104271] Boot crashes on Lenovo W520 with KVM and Discrete Graphic enabled in BIOS
Date: Wed, 09 Sep 2015 19:25:14 +0000 [thread overview]
Message-ID: <bug-104271-28872-9lBbu0oWB2@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-104271-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=104271
Alex Williamson <alex.williamson@redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |alex.williamson@redhat.com
--- Comment #3 from Alex Williamson <alex.williamson@redhat.com> ---
You might get more attention moving this bug to Drivers/PCI and including the
full dmesg or console log of the failure and lspci -vvv so we know something
about your system. If it doesn't boot, there are always screen shots or
netconsole if you're serial port challenged.
KVM is a hypervisor, it has nothing to do with your system not booting. More
likely it's something with the IOMMU. Does disabling VT-d help? What about
booting with iommu=pt? BTW, reproducing on another W520 doesn't mean the
hardware isn't broken, it just means this isn't a point defect. Hardware is
broken a disturbing amount of the time.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2015-09-09 19:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-09 9:05 [Bug 104271] New: Boot crashes on Lenovo W520 KVM and Discrete Graphic enabled in BIOS bugzilla-daemon
2015-09-09 9:07 ` [Bug 104271] Boot crashes on Lenovo W520 with " bugzilla-daemon
2015-09-09 12:41 ` bugzilla-daemon
2015-09-09 16:36 ` bugzilla-daemon
2015-09-09 19:25 ` bugzilla-daemon [this message]
2015-09-11 9:23 ` bugzilla-daemon
2015-09-11 9:38 ` bugzilla-daemon
2015-09-29 9:31 ` 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-104271-28872-9lBbu0oWB2@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).