public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
* problems with pci passthrough of nic and a DL380G6
@ 2009-05-11  2:09 David S. Ahern
  2009-05-11 22:50 ` Alex Williamson
  0 siblings, 1 reply; 2+ messages in thread
From: David S. Ahern @ 2009-05-11  2:09 UTC (permalink / raw)
  To: kvm-devel


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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2009-05-11 22:50 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-05-11  2:09 problems with pci passthrough of nic and a DL380G6 David S. Ahern
2009-05-11 22:50 ` Alex Williamson

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox