Pkg xen devel - Nov 2008 - Bug#477525: xen-utils-3.2-1: xend start fails using network-route

Package: xen-utils-3.2-1
Version: 3.2.1-2
Followup-For: Bug #477525

I have the same problem after updating from etch to lenny. (Thus updating Xen
from 3.0 to 3.2)

Does anyone know how to fix this?

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-1-xen-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages xen-utils-3.2-1 depends on:
ii  e2fslibs               1.41.2-1          ext2 filesystem libraries
ii  iproute                20080725-2        networking and traffic control too
ii  libc6                  2.7-15            GNU C Library: Shared libraries
ii  libgcrypt11            1.4.1-1           LGPL Crypto library - runtime libr
ii  libgnutls26            2.4.2-1           the GNU TLS library - runtime libr
ii  libncurses5            5.6+20080830-1    shared libraries for terminal hand
ii  libsdl1.2debian        1.2.13-2          Simple DirectMedia Layer
ii  libxenstore3.0         3.2.1-2           Xenstore communications library fo
ii  python                 2.5.2-2           An interactive high-level object-o
ii  python-central         0.6.8             register and build utility for Pyt
ii  udev                   0.125-7           /dev/ and hotplug management daemo
ii  xen-utils-common       3.2.0-2           XEN administrative tools - common 
ii  zlib1g                 1:1.2.3.3.dfsg-12 compression library - runtime

Versions of packages xen-utils-3.2-1 recommends:
ii  bridge-utils                  1.4-5      Utilities for configuring the Linu
ii  xen-hypervisor-3.2-1-amd64 [x 3.2.1-2    The Xen Hypervisor on AMD64

Versions of packages xen-utils-3.2-1 suggests:
ii  xen-docs-3.2                  3.2.1-2    Documentation for Xen

-- no debconf information

Finally I had spare time to work on this problem. I learned that all I  
had to do was to set the device to use explicitly in

/etc/xen/xend-config.sxp:
(network-script 'network-route netdev=eth0')

I guess in Xen <3.2 eth0 was the default setting.

Solved for me.

-- 
Gerd Fleischer

85051 Ingolstadt
GERMANY

jabber k3t at jabber.org