[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] pciback and pci passtrought problems


  • To: Xen Users <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: Velten Spägele <xen@xxxxxxxxx>
  • Date: Thu, 05 Mar 2009 20:09:04 +0100
  • Delivery-date: Thu, 05 Mar 2009 11:16:05 -0800
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.