From: "David S. Ahern" <daahern@cisco.com>
To: kvm-devel <kvm@vger.kernel.org>
Subject: problems with pci passthrough of nic and a DL380G6
Date: Sun, 10 May 2009 20:09:53 -0600 [thread overview]
Message-ID: <4A0788F1.5020704@cisco.com> (raw)
Are the instructions for passing a device at:
http://www.linux-kvm.org/page/How_to_assign_devices_with_VT-d_in_KVM
supposed to work for passing one of four onboard nics to a guest? I ask
because not only did it not work, it made my server a very unhappy camper.
Server: HP DL380 G6, 1 E5540, 6 GB RAM (3x2), latest BIOS
SMT enabled, VT-d2 enabled
Host OS: Fedora core 9 OS, kvm.git 66b0aed4a9e15..., pxe booted
Device is last of the four on-board nics (the host is using the first
one). Commands:
modprobe pci-stub
echo "14e4 1639" > /sys/bus/pci/drivers/pci-stub/new_id
echo "0000:03:00.1" > '/sys/bus/pci/devices/0000:03:00.1/driver/unbind'
echo "0000:03:00.1" > /sys/bus/pci/drivers/pci-stub/bind
Those commands worked fine. At this point I tried to mount the 4th
logical disk (host OS is run via pxe and automounting of drives is not
setup) and it failed. Since that disk holds the guest I wanted to run, I
decided to reboot and start fresh. During reboot the server hung after a
few BIOS initialization screens but before the PXE attempt. There was a
1 line message on the screen about an unknown NMI.
The IML for the server shows a couple of critical errors - description
is "Unknown Event (Class 6, Code 4). A second reboot attempt hung at the
same place. I had to disable VT-d2 in the BIOS to get it to come back.
Any ideas?
david
next reply other threads:[~2009-05-11 2:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-11 2:09 David S. Ahern [this message]
2009-05-11 22:50 ` problems with pci passthrough of nic and a DL380G6 Alex Williamson
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=4A0788F1.5020704@cisco.com \
--to=daahern@cisco.com \
--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