Re: [Xen-users] Networking with more NIC's

["Peter Fastré" <peter.fastre@xxxxxxxxx>]

On 3/17/07, jez <jez@xxxxxxxxxx> wrote:

Okay, I should probably have read a little more between the lines from
your previous posts and just assumed that all you wanted to do was to
have you DomU interfaces bridged with eth0 on Dom0. You don't care
about eth1 or eth2 for the moment right?

Well, if that is what you want, the main problem you've got at the
moment is that there are two bridges and one of them doesn't even seem
to really exist. I honestly don't have a clue how this could happen, but
I can suggest something for you to try.

In the file /etc/xen/xend-config.sxp, change:

    (network-script network-bridge)

to

    (network-script 'network-bridge bridge=xenbr0 netdev=eth0')

I've done this.
Now my ifconfig output is this:
eth0      Link encap:Ethernet  HWaddr 00:30:48:33:3B:74
          inet addr:10.200.1.100  Bcast: 0.0.0.0  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:182 errors:0 dropped:0 overruns:0 frame:0
          TX packets:52 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:13024 (12.7 KiB)  TX bytes:5656 (5.5 KiB)

eth1      Link encap:Ethernet  HWaddr 00:30:48:33:3B:75
          inet addr:10.201.1.100   Bcast:10.201.1.255  Mask:255.255.255.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Base address:0x2020 Memory:da020000-da040000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:308 errors:0 dropped:0 overruns:0 frame:0
          TX packets:94 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:24450 (23.8 KiB)  TX bytes:14650 (14.3 KiB)
          Base address:0x2000 Memory:da000000-da020000

vif0.1    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:52 errors:0 dropped:0 overruns:0 frame:0
          TX packets:182 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:5656 (5.5 KiB)  TX bytes:13024 ( 12.7 KiB)

xenbr0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:130 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:6246 (6.0 KiB)  TX bytes:0 (0.0 b)

root@vm01:~# brctl show
bridge name     bridge id               STP enabled     interfaces
xenbr0          8000.feffffffffff        no              vif0.1
                                                        peth0

Seems to be a little better? But the default route is still gone after starting xen.

Reboot your server to give it a fresh start. Then check 'ifconfig' and
also 'brctl show' to see that there is only the one bridge, xenbr0. If
all looks well, then try to start a DomU.

Still no success.
I'm doing some research on my own (mailling list/internet/configuration examples), and tried a lot of different values in the .sxp files, in the configuration files.
I tried changing the vif section:

# By default, no network interfaces are configured.  You may have one created
# with sensible defaults using an empty vif clause:
#
# vif = [ '' ]
#
# or optionally override backend, bridge, ip, mac, script, type, or vifname:
#
# vif = [ 'mac=00:16:3e:00:00:11, bridge=xenbr0' ]
#
# or more than one interface may be configured:
#
# vif = [ '', 'bridge=xenbr1' ]

When I read this, one would think that it's possible to boot a vm without network interface? I know this wouldn't make sense, but it could be useful for testing, not? But when I remove the vif option, the vm also doesn't boot.

Another thing I try.
I set the line in the config.sxp back to (network-script network-bridge)

When I do this, I find something strange too:
root@vm01:/etc/xen/scripts# ./network-bridge status
============================================================
5: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
    link/ether 00:30:48:33:3b:75 brd ff:ff:ff:ff:ff:ff
    inet 10.201.1.100/24 scope global eth1
12: xenbr1: <BROADCAST,NOARP,UP> mtu 1500 qdisc noqueue
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff

bridge name     bridge id               STP enabled     interfaces
xenbr1          8000.feffffffffff       no              vif0.1
                                                        peth1

10.200.1.0/24 dev eth0  proto kernel  scope link  src 10.200.1.100
10.201.1.0/24 dev eth1  proto kernel  scope link  src 10.201.1.100
127.0.0.0/8 dev lo  scope link
default via 10.200.1.1 dev eth0  metric 1

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
10.200.1.0      0.0.0.0         255.255.255.0    U     0      0        0 eth0
10.201.1.0      0.0.0.0         255.255.255.0   U     0      0        0 eth1
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
0.0.0.0         10.200.1.1       0.0.0.0         UG    1      0        0 eth0
============================================================


It seems it's creating a xenbr1 because it thinks that's my outgoing interface. So I guess your suggestion should be followed, and I have to add something to the xend-config.sxp file to get things right.

If this has to do with my distribution (Slackware), please just say that. I don't like to switch, but if necessary, I'll do that. I tried ubuntu 6.06 64-bit, which worked fine, but not all my machines are 64-bit. With ubuntu 6.06 32-bit I ran into big problems because of the TLS-libs, which should be recompiled with some options (something about no segments). I didn't succeed doing that. I did succeed recompiling the glibc on my slackware box, so now I'm using this.
But if all my problems would be resolved by choosing some other distribution, please let me know. I'm working on this Xen-setup for more than two weeks now, and I just don't know it anymore. I considered moving to the commercial version of xen, but my server is not supported by them (3ware 9650 controller). I'm also willing to pay someone to get installation support, I just want it to work :(

cheers

Peter

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