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

[Xen-users] xen networking and pci late binding



Hi,
I have a PC with 3 ethernet interfaces. I am trying to a) assign 2 ethernet interfaces exclusively to one domU by using the late binding method and b) to use a bridge between the third interface and dom0 (that works fine). The goal is to not to have to use bridges for the exclusively assigned interfaces.
Is it possible? (If not, no need to read the rest)

The problem I have is that I cannot ping out of the exclusively assigned ethernet interfaces in the domU.

The ethernet interfaces in the domU have a mac address assigned by xen, not the actual card mac address. So, I assigned the card mac address to the ethernet interfaces (otherwise you would need a bridge, wouldn't you?), but it still does not work.

How can I verify that the pci are actually binded to the domU? After I unbind/bind the pci, the "lspci" command still shows the devices in the dom0 and "lspci" returns an error in the domU. One way I found was to try to enable the interface (ifconfig ethX up) in the domU, and it does not work, which leads me to conclude that the interfaces are assigned to the domU.

Also, when I create the domU after I unbind/bind the interfaces, a bridge is created as follows:
brctl show
bridge name     bridge id               STP enabled     interfaces
xenbr1          8000.feffffffffff       no              peth1
                                                       vif0.1
                                                       vif2.0
                                                       vif2.1
                                                       vif2.2

All 3 interfaces are bridged. I would expect the two hidden interfaces not to be part of the bridge.
Am I missing something?

I am using xen 3.0.2 with the default configuration (downloaded with yum) and FC5. Here is the lpsci:
lspci | grep Ethernet
02:01.0 Ethernet controller: D-Link System Inc RTL8139 Ethernet (rev 10)
02:02.0 Ethernet controller: D-Link System Inc DL10050 Sundance Ethernet (rev 15) 02:0c.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller (rev 02)

and here is the script to bind/unbind:
#!/bin/sh
#
ifdown eth0
ifdown dev1804289383

echo -n 0000:02:02.0 > /sys/bus/pci/drivers/sundance/unbind
echo -n 0000:02:02.0 > /sys/bus/pci/drivers/pciback/new_slot
echo -n 0000:02:02.0 > /sys/bus/pci/drivers/pciback/bind

echo -n 0000:02:01.0 > /sys/bus/pci/drivers/8139too/unbind
echo -n 0000:02:01.0 > /sys/bus/pci/drivers/pciback/new_slot
echo -n 0000:02:01.0 > /sys/bus/pci/drivers/pciback/bind

Here is the domU configuration (the first pci/mac, empty, is the dom0-domU bridge, the last 2 are the exclusively assigned ethernet):
name = "apache"
memory = "256"
disk = [ 'file:/xen/vm1disk1,xvda,w' ]
vif = [ '','mac=00:50:ba:b0:59:ce', 'mac=00:53:46:e7:6f:9e' ]
bootloader="/usr/bin/pygrub"
pci = [ '', '02,01,0', '02,02,0' ]
on_reboot   = 'restart'
on_crash    = 'restart'

Thanks,
Pascal



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