[Xen-users] Xen on Debian Etch - no dom0 network

[George Karaolides <george@xxxxxxxxxxxxxxxxxx>]

Greetings everyone,

I am trying to set up Xen on Debian Etch for the first time.

Hardware is an IBM Blade type HS21 (IBM machine type-model 8853A2G).

Everything is installed from Debian packages, nothing is locally
compiled.  Relevant packages installed, with revision numbers:

linux-image-2.6.18-5-xen-amd64       2.6.18.dfsg.1-13etch6
linux-modules-2.6.18-5-xen-amd64     2.6.18.dfsg.1-13etch6
xen-linux-system-2.6.18-5-xen-amd64  2.6.18.dfsg.1-13etch6
xen-tools                            2.8-2
xen-utils-3.0.3-1                    3.0.3-0-4
xen-utils-common                     3.0.3-0-2

I have succeeded in creating and booting a guest domain with Debian as
the guest OS, and controlling the guest domain via xm console, so I
guess the basic installation of Xen is OK.

However, I am failing to bring up networking for dom0.

The blade's network setup is as simple as it gets.  Just one of its two
ethernet interfaces is used as eth0, configured with static settings
from Debian's /etc/network/interfaces file.

When the default choice of network-dummy is used as the network startup
script in /etc/xen/xend-config.sxp, the blade has network connectivity.

ifconfig output for eth0 with network-dummy:

# ifconfig
eth0      

Link encap:Ethernet  HWaddr 00:1A:64:8C:BE:AA
inet addr:192.168.0.2  Bcast:192.168.0.255  Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
RX packets:769 errors:0 dropped:0 overruns:0 frame:0
TX packets:433 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:68461 (66.8 KiB)  TX bytes:76186 (74.4 KiB)
Interrupt:19 Memory:da000000-da011100

When I change the choice of network script in /etc/xen/xend-config.sxp
to try and bring up networking for Xen, the blade boots up with no
ethernet connectivity.  But it seems that the various virtual interfaces
and the bridge for dom0 are configured correctly, here is the output of
ifconfig with bridging enabled:

eth0
Link encap:Ethernet  HWaddr 00:1A:64:8C:BE:AA
inet addr:192.168.0.2  Bcast:192.168.0.255  Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
RX packets:7 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:764 (764.0 b)  TX bytes:468 (468.0 b)

lo
Link encap:Local Loopback
inet addr:127.0.0.1  Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
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
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
RX packets:15 errors:0 dropped:0 overruns:0 frame:0
TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1356 (1.3 KiB)  TX bytes:732 (732.0 b)
Interrupt:20 Memory:da000000-da011100

vif0.0
Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
RX packets:6 errors:0 dropped:0 overruns:0 frame:0
TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:468 (468.0 b)  TX bytes:764 (764.0 b)

xenbr0
Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
RX packets:11 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:958 (958.0 b)  TX bytes:0 (0.0 b)


And here is the output of brctl show:

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


And of iptables -L -n -v (just the same as with network-dummy):

Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source
destination

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source
destination

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source
destination


And of route -n (again this is the same as with network-dummy):

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
192.168.0.0     0.0.0.0         255.255.255.0 U     0      0        0
eth0
0.0.0.0         192.168.0.1     0.0.0.0         UG    0      0        0
eth0


I am not sure how to troubleshoot this any further.  I have read the
background on Xen networking at
http://wiki.xensource.com/xenwiki/XenNetworking and understood the basic
concepts more or less, but there seems to be little information on what
to check if it doesn't work as described.

Any help would be very much appreciated.

Best regards,

George Karaolides
System Administrator
OTEnet Telecommunications Ltd.
Nicosia, Cyprus


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