Hi,
once again, Problems with pciback and pci passthrough
the system
--------------------------------------------------------------------------------
DOMAIN0:~# lspci -tv
-[0000:00]-+-00.0 nVidia Corporation nForce3 250Gb Host Bridge
+-01.0 nVidia Corporation nForce3 250Gb LPC Bridge
+-01.1 nVidia Corporation nForce 250Gb PCI System Management
+-02.0 nVidia Corporation CK8S USB Controller
+-02.1 nVidia Corporation CK8S USB Controller
+-02.2 nVidia Corporation nForce3 EHCI USB 2.0 Controller
+-05.0 nVidia Corporation CK8S Ethernet Controller
+-08.0 nVidia Corporation CK8S Parallel ATA Controller (v2.5)
+-0a.0 nVidia Corporation CK8S Serial ATA Controller (v2.5)
+-0b.0-[0000:01]----00.0 nVidia Corporation NV34 [GeForce
FX 5200]
+-0e.0-[0000:02]--+-05.0 Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+
| +-06.0 Atheros Communications, Inc.
AR5212 802.11abg NIC
| +-07.0 Cologne Chip Designs GmbH ISDN
network controller [HFC-PCI]
| +-08.0 Motorola Wildcard X100P
| \-09.0 Intel Corporation 536EP Data Fax Modem
+-18.0 Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
HyperTransport Technology Configuration
+-18.1 Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
Address Map
+-18.2 Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
DRAM Controller
\-18.3 Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
Miscellaneous Control
------------------------------------------------------------------------------------
i used this patch
------------------------------------------------------------------------------------
diff -r 6ab55f716ce3 tools/python/xen/util/pci.py
--- a/tools/python/xen/util/pci.py Thu Oct 09 17:18:11 2008 +0100
+++ b/tools/python/xen/util/pci.py Fri Oct 10 13:16:00 2008 +0800
@@ -696,6 +696,7 @@ class PciDevice:
def do_FLR(self):
""" Perform FLR (Functional Level Reset) for the
device.
"""
+ return
if self.dev_type == DEV_TYPE_PCIe_ENDPOINT:
# If PCIe device supports FLR, we use it.
if self.pcie_flr:
diff -r 6ab55f716ce3 tools/python/xen/xend/server/pciif.py
--- a/tools/python/xen/xend/server/pciif.py Thu Oct 09 17:18:11 2008 +0100
+++ b/tools/python/xen/xend/server/pciif.py Fri Oct 10 13:18:25 2008 +0800
@@ -375,6 +375,7 @@ class PciController(DevController):
pci_dev_list = pci_dev_list + [(domain, bus, slot, func)]
for (domain, bus, slot, func) in pci_dev_list:
+ continue
try:
dev = PciDevice(domain, bus, slot, func)
except Exception, e:
--------------------------------------------------------------------------------------
and was activating in the kernel options "PCI_device backend driver as
built in.
but the result is:
--------------------------------------------------------------------------------------
DOMAIN0:~# dmesg | grep pciback
Bootdata ok (command line is root=/dev/sda2 ro console=tty0
pciback.hide=(0000:02:05.0)(0000:02:06.0)(0000:02:07.0)(0000:02:08.0)(0000:02:09.0)
)
Kernel command line: root=/dev/sda2 ro console=tty0
pciback.hide=(0000:02:05.0)(0000:02:06.0)(0000:02:07.0)(0000:02:08.0)(0000:02:09.0)
Unknown boot option
`pciback.hide=(0000:02:05.0)(0000:02:06.0)(0000:02:07.0)(0000:02:08.0)(0000:02:09.0)'':
ignoring
--------------------------------------------------------------------------------------
after trying to load pciback as module:
--------------------------------------------------------------------------------------
echo -n 0000:02:05.0 > /sys/bus/pci/drivers/8139too/unbind
modprobe pciback
echo -n 0000:02:05.0 > /sys/bus/pci/drivers/pciback/new_slot
echo -n 0000:02:05.0 > /sys/bus/pci/drivers/pciback/bind
echo -n 0000:02:06.0 > /sys/bus/pci/drivers/pciback/new_slot
echo -n 0000:02:06.0 > /sys/bus/pci/drivers/pciback/bind
echo -n 0000:02:07.0 > /sys/bus/pci/drivers/pciback/new_slot
echo -n 0000:02:07.0 > /sys/bus/pci/drivers/pciback/bind
---------------------------------------------------------------------------------------
this result with xm:
---------------------------------------------------------------------------------------
DOMAIN0:~# xm create /etc/xen/auto/fli4l
Using config file "/etc/xen/auto/fli4l".
Error: pci: 0000:02:05.0: non-page-aligned MMIO BAR found.
---------------------------------------------------------------------------------------
so can i use the last xen release only with very special Hardware, or
would it be possible to use it like in the older versions ?
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Velten, On 5 Mar 2009, at 20:09, Velten Spägele wrote:> so can i use the last xen release only with very special Hardware, > or would it be possible to use it like in the older versions ?I have the same problem, but it has nothing to do with PCI passthrough in general. It seems to be a problem with passing devices in a specific state to a DomU. I currently have a DomU which gets all the USB controllers on my mainboard passed through, or at least is supposed to. However, when I start up the domain it complains about device 00:13.2, which is an USB EHCI controller and I think the only controller that has a device connected to it, because that device does not show up in lsusb inside the DomU. The second Controller (or rather the first, 00:12.2) works fine. I haven''t been able to test what happens if I unplug the device, the case LCD to be more precise, because the system is currently running and I don''t like working inside running systems, so this is only a hunch. In your case, the device might be in that (undesired) state, because it was already initialized/used by a device driver in Dom0, so the first thing to try would be to use a kernel with pciback built in. That way, it will be able to grab your PCI devices on boot as you specified on the command-line (which shouldn''t do much right now). An alternative would be to blacklist the device driver module (8139too in your case), to prevent the system from loading it automatically on boot. However, in both cases, you will not be able to start up your DomU again without rebooting, after you try to use it in Dom0. If that does not help, removing that specific device from the DomU "fixes" the problem for me and my DomU starts up normally with all the other devices visible inside. Since the device that causes the problem on your system is a NIC, this might be a good idea anyways, since you will need it in Dom0 with a bridge and a virtual NIC in your Fli4L DomU in order to have other DomUs and Dom0 access your LAN (if you''re doing what I think you are :) ). I hope this helps you a little, Paul. - -- Paul Schulze Mail: avlex82@gmail.com Why can''t a programmer tell the difference between Halloween and Christmas? Because OCT31 = DEC25. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (Darwin) iEYEARECAAYFAkm2SV4ACgkQj2zIQLJNnKNYkACfdgEYkCXyDg4HTkT0yGxYbfO8 bZ8AoO4N4Pz2f+x0DWa0OJy2gtkgCD7y =zwvK -----END PGP SIGNATURE----- _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users