[Xen-users] Xen 3.1 on Debian Etch: Dom0 eth0 dead

["Florian Engelmann (Manntech)" <florian.engelmann@xxxxxxxxxxx>]

Hi,
I just installed a clean debian etch 4.0r1 with LVM on our Dell PowerEdge
2900. The system has 2 Broadcom onboard NICs and I also installed 2 Intel
Pro 1000 NICs. I installed all needed pakages and also dev86.

apt-get install screen ssh debootstrap python python-twisted iproute
bridge-utils libcurl3-dev libssl0.9.7 libvncserver-dev yaird

I installed like this:

wget
http://bits.xensource.com/oss-xen/release/3.1.0/bin.tgz/xen-3.1.0-install-x8
6_32.tgz
tar xvzf xen-3.1.0-install-x86_32.tgz
cd dist/
./install.sh
mv /lib/tls /lib/tls.disabled
update-rc.d xend defaults 20 21
update-rc.d xendomains defaults 21 20
depmod 2.6.18-xen
mkinitrd.yaird -o /boot/initrd.img-2.6.18-xen 2.6.18-xen
update-grub

All worked without any errors. So i rebooted into my xen kernel.

shutdown -r now

The kernel booted also without any errors an i got my login prompt. I tried
to login with ssh from my workstation but that did not work. So i tried to
ping my Server what also failed. An ifconfig gives me an eth0 device with my
local IP 192.168.1.6 a lo device a peth0 device a vif0.0 device and a xenbr0
device without any IP. I did not modify the /etc/xen/xend-config.sxp and my
/etc/network/interfaces looks like this:

iface eth0 inet static
        address 192.168.1.7
        netmask 255.255.255.0
        #network 192.168.1.0
        #broadcast 192.168.1.255
        gateway 192.168.1.201
        # dns-* options are implemented by the resolvconf package, if
installed
        #dns-nameservers 192.168.1.210
        #dns-search manntech.local

auto eth3
iface eth3 inet static
        address 192.168.99.7
        netmask 255.255.255.0
        network 192.168.99.0
        broadcast 192.168.99.255


While eth0 is my default LAN interface and eth3 is my crossover interface to
the 2nd clusternode. If I change

(network-script network-bridge)
to
(network-script 'network-bridge netdev=eth1')

my eth0 works fine but any DomU I start does not get any network connection.

I did many tests and on a Desktop System I used to test the same setup
(Debian Etch 4.0r1 and Xen 3.1) there was no problem with eth0 after the
installation. I also tried to install Xen 3.1 from source and I also
compiled my own Dom0 kernel. Nothing helped.

This is my dmesg with (network-script 'network-bridge netdev=eth1')
configured:

e1000: 0000:0b:01.0: e1000_probe: (PCI:66MHz:32-bit) 00:1b:21:07:6a:c7
hda: ATAPI 48X DVD-ROM CD-R/RW drive, 1536kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
ACPI: PCI Interrupt 0000:0b:02.0[A] -> GSI 36 (level, low) -> IRQ 21
e1000: 0000:0b:02.0: e1000_probe: (PCI:66MHz:32-bit) 00:0e:0c:d8:1c:43
e1000: eth1: e1000_probe: Intel(R) PRO/1000 Network Connection
Broadcom NetXtreme II Gigabit Ethernet Driver bnx2 v1.4.44 (August 10, 2006)
ACPI: PCI Interrupt 0000:09:00.0[A] -> GSI 16 (level, low) -> IRQ 16
eth1: Broadcom NetXtreme II BCM5708 1000Base-T (B2) PCI-X 64-bit 133MHz
found at mem f4000000, IRQ 16, node addr 0019b9d8f488
ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 16 (level, low) -> IRQ 16
eth0: Broadcom NetXtreme II BCM5708 1000Base-T (B2) PCI-X 64-bit 133MHz
found at mem f8000000, IRQ 16, node addr 0019b9d8f486
Adding 3951980k swap on /dev/sda2.  Priority:-1 extents:1 across:3951980k
Filesystem "dm-0": Disabling barriers, not supported by the underlying
device
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Filesystem "dm-4": Disabling barriers, not supported by the underlying
device
XFS mounting filesystem dm-4
Ending clean XFS mount for filesystem: dm-4
Filesystem "dm-5": Disabling barriers, not supported by the underlying
device
XFS mounting filesystem dm-5
Ending clean XFS mount for filesystem: dm-5
Filesystem "dm-1": Disabling barriers, not supported by the underlying
device
XFS mounting filesystem dm-1
Ending clean XFS mount for filesystem: dm-1
Filesystem "dm-2": Disabling barriers, not supported by the underlying
device
XFS mounting filesystem dm-2
Ending clean XFS mount for filesystem: dm-2
Filesystem "dm-3": Disabling barriers, not supported by the underlying
device
XFS mounting filesystem dm-3
Ending clean XFS mount for filesystem: dm-3
e1000: eth3: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex
ACPI: Power Button (FF) [PWRF]
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
ADDRCONF(NETDEV_UP): eth0: link is not ready
IPv6 over IPv4 tunneling driver
bnx2: eth0 NIC Link is Up, 100 Mbps full duplex, receive & transmit flow
control ON
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Bridge firewalling registered
device vif0.0 entered promiscuous mode
audit(1189408717.279:2): dev=vif0.0 prom=256 old_prom=0 auid=4294967295
xenbr0: port 1(vif0.0) entering learning state
xenbr0: topology change detected, propagating
xenbr0: port 1(vif0.0) entering forwarding state
ADDRCONF(NETDEV_UP): peth1: link is not ready
bnx2: peth1 NIC Link is Up, 100 Mbps full duplex, receive & transmit flow
control ON
ADDRCONF(NETDEV_CHANGE): peth1: link becomes ready
device peth1 entered promiscuous mode
audit(1189408719.429:3): dev=peth1 prom=256 old_prom=0 auid=4294967295
xenbr0: port 2(peth1) entering learning state
xenbr0: topology change detected, propagating
xenbr0: port 2(peth1) entering forwarding state
eth3: no IPv6 routers present
vif0.0: no IPv6 routers present
eth0: no IPv6 routers present
peth1: no IPv6 routers present

What is going wrong? Any ideas how to solve that Problem?

Mit freundlichen Grüssen / Best regards

Florian Engelmann
EDV Service / IT Services

Manntech Fassadenbefahrsysteme GmbH
Mannesmannstr. 5
- Industriegebiet Kugelbichl -
82291 Mammendorf
Tel.: +49 (0) 8145 / 999 - 271
Email: florian.engelmann@xxxxxxxxxxx
http://www.manntech.de



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