[Xen-devel] pciback module not working

["David Brown" <dmlb2000@xxxxxxxxx>]

This issue was brought up about a year and a half ago. So I'll bring
it up again and see if anything happens.

I've got an infiniband network and am attempting to pass the
infiniband card through the host and give it to the guest.
I'm working with standard CentOS 5.2 on both guest and host with their
provided xen (3.0.3 ish). I've also attempted to install the newest
Xen 3.3 and use their standard host kernel and that did the same
thing. The guest dmesg output in the guest is similar on both
permissive and normal mode.

I'm getting issues with detecting the firmware on the card for some reason...

Any help would be appreciated.

Thanks,
- David Brown

=== GUEST dmesg output ===
ib_mthca: Mellanox InfiniBand HCA driver v1.0 (February 28, 2008)
ib_mthca: Initializing 0000:00:00.0
PCI: Enabling device 0000:00:00.0 (0000 -> 0002)
PCI: Setting latency timer of device 0000:00:00.0 to 64
ib_mthca 0000:00:00.0: QUERY_FW command failed, aborting.
ib_mthca: probe of 0000:00:00.0 failed with error -11
=======================

=== Host modprobe.conf ===
alias eth0 bnx2
alias eth1 bnx2
alias scsi_hostadapter cciss
options pciback hide=(41:00.0)
=====================

=== Host lspci output ===
# lspci -vs 41:00.0
41:00.0 InfiniBand: Mellanox Technologies MT25204 [InfiniHost III Lx
HCA] (rev 20)
        Subsystem: Hewlett-Packard Company Unknown device 170a
        Flags: fast devsel, IRQ 16
        Memory at fdc00000 (64-bit, non-prefetchable) [disabled] [size=1M]
        Memory at fd000000 (64-bit, prefetchable) [disabled] [size=8M]
        Capabilities: [40] Power Management version 2
        Capabilities: [48] Vital Product Data
        Capabilities: [90] Message Signalled Interrupts: 64bit+ Queue=0/5 
Enable-
        Capabilities: [84] MSI-X: Enable- Mask- TabSize=32
        Capabilities: [60] Express Endpoint IRQ 0
=====================

This makes sure it get loaded first off before anything else.
=== Host mkinitrd cmd ===
# mkinitrd -f --with=pciback --preload pciback
/boot/initrd-2.6.18-92.1.10.el5xen.img 2.6.18-92.1.10.el5xen
====================

=== Host pciback dmesg ===
pciback 0000:41:00.0: Driver tried to write to a read-only
configuration space field at offset 0x44, size 2. This may be
harmless, but if you have problems with your device:
1) see permissive attribute in sysfs
2) report problems to the xen-devel mailing list along with details of
your device obtained from lspci.
PCI: Enabling device 0000:41:00.0 (0000 -> 0002)
ACPI: PCI Interrupt 0000:41:00.0[A] -> GSI 16 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:41:00.0 to 64
ACPI: PCI interrupt for device 0000:41:00.0 disabled
======================

=== Host pciback dmesg (after setting it permissive) ===
pciback 0000:41:00.0: enabling permissive mode configuration space accesses!
pciback 0000:41:00.0: permissive mode is potentially unsafe!
pciback: vpci: 0000:41:00.0: assign to virtual slot 0
device vif1.0 entered promiscuous mode
ADDRCONF(NETDEV_UP): vif1.0: link is not ready
blkback: ring-ref 9, event-channel 28, protocol 1 (x86_64-abi)
PCI: Enabling device 0000:41:00.0 (0000 -> 0002)
ACPI: PCI Interrupt 0000:41:00.0[A] -> GSI 16 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:41:00.0 to 64
ACPI: PCI interrupt for device 0000:41:00.0 disabled
=========================================

=== Guest lspci output ===
# lspci -v
00:00.0 InfiniBand: Mellanox Technologies MT25204 [InfiniHost III Lx
HCA] (rev 20)
        Subsystem: Hewlett-Packard Company Unknown device 170a
        Flags: fast devsel, IRQ 16
        Memory at fdc00000 (64-bit, non-prefetchable) [disabled] [size=1M]
        Memory at fd000000 (64-bit, prefetchable) [disabled] [size=8M]
        Capabilities: [40] Power Management version 2
        Capabilities: [48] Vital Product Data
        Capabilities: [90] Message Signalled Interrupts: 64bit+
Queue=0/5 Enable-
        Capabilities: [84] MSI-X: Enable- Mask- TabSize=32
        Capabilities: [60] Express Endpoint IRQ 0
=====================

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel