Re: [Xen-users] No network connectivity for domU in SuSE 10, Xen 3

[Lars Braeuer <lbraeuer@xxxxxxxx>]

Kris Vassallo wrote:
> On Wed, 2006-02-08 at 14:22 +0100, Thorolf Godawa wrote:
>
> > Hi,
> >
> > try to set STARTMODE='onboot' in the ifcfg-eth0.... in dom0 and domU.
> As was in my last email, startmode is set to onboot and I have tried 
> auto as well, but still the darn thing won't come up  on domU boot
> > It also seems to be better to set the config of the domU to a static
> > MAC-address, because with every boot (and new MAC-address if they are
> > created random) SuSE creates a new eth-if!
> >
> > Check in the 30-net_persistent_names.rules that there is only one entry
> > for eth0 for the wanted MAC-address!
> Same thing here, I already have the physical address set in the domU 
> config and I only have 1 line (which I included in my previous posting) 
> in my 30-net_persistent_names.rules which corresponds to the same mac as 
> is set in the domU configuration file. Yet still the interface doesn't 
> come up at domU boot.
> Any other ideas on why SuSU 10 wont bring up eth0 on domU boot?
> -Kris
>
> > Maybe it helps!



I'm experiencing the same problem with xen 3 + suse 10 (kernel-xen 2.6.13).

After Dom0 boot up the following interfaces are present (cable is attached to 
eth0):

1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: vif0.0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
    inet6 fe80::fcff:ffff:feff:ffff/64 scope link
       valid_lft forever preferred_lft forever
3: eth0: <BROADCAST,MULTICAST,NOTRAILERS,UP> mtu 1500 qdisc noqueue
    link/ether 00:e0:81:58:91:11 brd ff:ff:ff:ff:ff:ff
    inet 192.168.123.109/24 brd 192.168.123.255 scope global eth0
    inet6 fe80::2e0:81ff:fe58:9111/64 scope link
       valid_lft forever preferred_lft forever
4: peth0: <BROADCAST,MULTICAST,NOARP,UP> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
    inet6 fe80::fcff:ffff:feff:ffff/64 scope link
       valid_lft forever preferred_lft forever
5: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
    link/ether 00:e0:81:58:91:10 brd ff:ff:ff:ff:ff:ff
6: sit0: <NOARP> mtu 1480 qdisc noop
    link/sit 0.0.0.0 brd 0.0.0.0
7: xenbr0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
    inet 192.168.123.120 peer 192.168.123.254/32 brd 192.168.123.255 scope 
global xenbr0
    inet6 fe80::200:ff:fe00:0/64 scope link
       valid_lft forever preferred_lft forever


The script "network-bridge" runs completely till the last line (verified), but is hanging afterwards 
as a zombie.
 6368 ?        Z      0:00 [network-bridge] <defunct>


Dom0 brctl show output is:
bridge name     bridge id               STP enabled     interfaces
xenbr0          8000.feffffffffff       no              vif0.0
                                                        peth0


When a DomU system is started (suse) a new interface is added in Dom0:

8: vif1.0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff


The config of the DomU system looks like this:

--------------------------------------
name ="domu1"
kernel ="/boot/vmlinuz-2.6.13-15-xen"
memory =1024
vif = ['mac=aa:00:00:01:01:00, bridge=xenbr0']
disk = ['phy:sda5,sda1,w']
root ="/dev/sda1 ro"

# network
nics=1
dhcp ="off"
ip="192.168.123.90"
netmask="255.255.255.0"
gateway="192.168.123.254"
hostname="domu1"

extra="3"
--------------------------------------

The following interfaces are present within domu1:

1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: vif0.0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
3: veth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
4: eth5: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
    link/ether aa:00:00:01:01:00 brd ff:ff:ff:ff:ff:ff
5: sit0: <NOARP> mtu 1480 qdisc noop
    link/sit 0.0.0.0 brd 0.0.0.0



Although the vif-bridge script is stated as vif-script in the xend-config.sxp 
it is not run.
(vif-script        vif-bridge)


... so I tried to add the stuff manually:

brctl addif xenbr0 vif1.0
ifconfig vif1.0 up
(Didn't add the iptables rules yet, because all chains are "ACCEPT")


Leading to (Dom0):

bridge name     bridge id               STP enabled     interfaces
xenbr0          8000.feffffffffff       no              vif0.0
                                                        peth0
                                                        vif1.0


When I configure eth5 (in domu1) with an ip address (192.168.123.90) and try to add a route to the 
net I get:
# route add -net 192.168.123.0 netmask 255.255.255.0 eth5
SIOCADDRT: Network is down


Is there another way to get it manually working?

Why would'nt the vif-bridge script run (the script is executable)?

Is there a bridge setup within the DomU required? The bridge userland tools are installed within the 
domu1.

Best,

Lars

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