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

[Xen-users] Dell R605: Broadcom PCI pass through problem


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Per Jensen <per@xxxxxxxxx>
  • Date: Sun, 23 Aug 2009 14:00:45 +0200
  • Delivery-date: Sun, 23 Aug 2009 05:01:25 -0700
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


List,

I am working on a Dell R605 server which has a pcicard with 2 Broadcom
NetXtreme II BCM5709 nics. I want to let a PV vm have access to it.

OS is Debian Lenny  2.6.26-2-xen-amd64. I have compiled the "offical"
2.6.18 Xen kernel with 3.2.3 and 3.3.2 versions with same result as
using the Lenny kernel.

The domU "sees" the pcicard:
A lspci gives:
balrog2:~# lspci
00:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709
Gigabit Ethernet (rev 20)


There IS a difference between the dom0 and domU lspci output. On dom0
each nic is output as 00:06:0.0 and 00:06:0.1, while there is no ".x" in
 the lspci output on domU.

I have no luck setting up the eth1/eth2 interfaces on domU. The bnx2
driver is aliased to eth1 and eth2 and IS loaded. When trying to setup
eth1 I get this:
balrog2:~# ifup eth1
SIOCSIFADDR: No such device
eth1: ERROR while getting interface flags: No such device
SIOCSIFNETMASK: No such device
SIOCSIFBRDADDR: No such device
eth1: ERROR while getting interface flags: No such device
eth1: ERROR while getting interface flags: No such device
Failed to bring up eth1.


To me it seems I am almost there, but am currently stuck, should one of
you have succeeded using the a  similiar pcicard, I am very interested
in hearing how.




lspci on dom0 gives:
master:/etc/xen# lspci|grep -i netx
06:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709
Gigabit Ethernet (rev 20)
06:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709
Gigabit Ethernet (rev 20)
08:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708
Gigabit Ethernet (rev 12)


On dom0 pciback is working:
master:/etc/xen# dmesg|grep seiz
[    0.988026] pciback 0000:06:00.0: seizing device
[    0.988026] pciback 0000:06:00.1: seizing device


master:/etc/xen# ls -l /sys/bus/pci/drivers/pciback
total 0
lrwxrwxrwx 1 root root    0 2009-08-23 13:25 0000:06:00.0 ->
../../../../devices/pci0000:00/0000:00:0a.0/0000:06:00.0
lrwxrwxrwx 1 root root    0 2009-08-23 13:25 0000:06:00.1 ->
../../../../devices/pci0000:00/0000:00:0a.0/0000:06:00.1
- --w------- 1 root root 4096 2009-08-23 13:25 bind
lrwxrwxrwx 1 root root    0 2009-08-23 13:25 module ->
../../../../module/pciback
- --w------- 1 root root 4096 2009-08-23 13:25 new_id
- --w------- 1 root root 4096 2009-08-23 13:25 new_slot
- -rw------- 1 root root 4096 2009-08-23 13:25 permissive
- -rw------- 1 root root 4096 2009-08-23 13:25 quirks
- --w------- 1 root root 4096 2009-08-23 13:25 remove_slot
- -r-------- 1 root root 4096 2009-08-23 13:25 slots
- --w------- 1 root root 4096 2009-08-23 13:22 uevent
- --w------- 1 root root 4096 2009-08-23 13:25 unbind

Regards
Per


- --
- ----------------------------------------------------------------------
Per Jensen        http://www.net-es.dk/~pj      FSF member #1516
- ----------------------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkqRL1UACgkQSO+YZlPNgGXYUwCgpqVJ8bVREzHNUXppTRgkdujG
6AQAoJB3M+FmPYdt8OkboEM7xjxbqp9F
=BgVh
-----END PGP SIGNATURE-----

_______________________________________________
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®.