This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-users] Re: xen is causing network problems to Dom0 - bridge problem

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Re: xen is causing network problems to Dom0 - bridge problem?
From: "Marco Strullato" <marco.strullato@xxxxxxxxx>
Date: Wed, 3 Oct 2007 16:43:56 +0200
Delivery-date: Wed, 03 Oct 2007 07:44:48 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=OPfIEnP21f0NKxIwTPpH5AT3WnA0YRKI2WJnK/IGXZQ=; b=Ql98iQv7sJs8sHBELj9I735+SMd2/sMDgMfZctRc2SJZ4vrBW3z5yaxKBHBTvgK4cZFtwQyXONuUjkUEKRJIpcTA/b7mnAZ44XVBO4cdQh8tjJBdoA11xP2KfJ97KJmVaGB/ypCpnld+uwLjFQU98PVckLITzPde2QiR77fKmkk=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=jiF7OqxWDjqRQL8j8z8stXedB0b74ESYCB4LyOV7Q98sikcyTk1hwUPQsIkOGKWtYhUlEeJc0xBPyXA4GZw4FxFYaCkJ5nco0ZEYfLbw/I82bgAexMkD0wRslkd+CjT0xRKvfPjQvbLwynBt7gVFlTTTMe12acwVw81Qx/ZEEUc=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <b9f669850710030639q4a92a5d9xb2c5521f8b78221@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <b9f669850710030639q4a92a5d9xb2c5521f8b78221@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Solved: I deleted the directory /var/lib/xend/state and reboot. The problem was due to a dirty configuration present into that directory

2007/10/3, Marco Strullato < marco.strullato@xxxxxxxxx>:
Hi all!
xen is causing network problems to Dom0.

I'll explain what happens during boot:
-network interface module is loaded correctly
-network starts correctly and it gets an ip from dhcp
-xend starts and make Dom0 offline.

/etc/xen/xend-config.sxp is:
(xend-unix-server yes)
(xend-unix-path /var/lib/xend/xend-socket)
(xend-relocation-hosts-allow '^localhost$ ^localhost\\.localdomain$')
(network-script network-bridge)
(vif-script vif-bridge)
(dom0-min-mem 256)
(dom0-cpus 0)
(vncpasswd '')

I think the problem is due to /etc/xen/scripts/network-bridge: I think the script has some problem and it does not complete the bridge creation.
If I boot Dom0 without starting xend. I get eth0 and lo running
If I boot Dom0 starting network and xend I get lo, tmpbridge and virbr0 interfaces: eth0 is missing and there are other devices that appears to be temporary devices.
If I boot Dom0 starting only network and I execute /etc/xen/scripts/network-bridge start I get eth0, lo, peth0: so it appears that the script is running fine.
if I boot Dom0 starting network, executing the script tc/xen/scripts/network-bridge start and then service xend start I get eth0, lo, peth0, tmpbridge and virbr0: xen runs well however ther are tmpbridge and virbr0 devices.
if I boot Dom0 starting network, executing the script /etc/xen/scripts/network-bridge start, executing service xend start and xm create <DomainU> I get eth0, lo, peth0, tmpbridge, virbr0 and vif1.0.

I changed the log level to debug and I wrote some set -x in the right place: I get

Xend started at Wed Oct  3 15:18:20 2007.
device eth0 already exists; can't create bridge with the same name
set hello timer failed: No such file or directory
set forward delay failed: No such file or directory
set stp status failed: No such file or directory
++ set -e
+ . /etc/xen/scripts/xen-network-common.sh
++ set -x
++ '[' -e /etc/SuSE-release ']'
++ which ifup
+ findCommand start
+ for arg in '"$@"'
+ expr index start =
+ command=start
+ return
+ evalVariables start
+ for arg in '"$@"'
+ expr index start = '>' 1
++ ip route list
++ awk '/^default / { print $NF }'
++ sed 's/.* dev //'
+ netdev=eth0
+ bridge=eth0
+ antispoof=no
+ pdev=peth0
+ tdev=tmpbridge
+ case "$command" in
+ op_start
+ set -x
+ '[' eth0 = null ']'
+ link_exists peth0
+ ip link show peth0
+ return 1
+ create_bridge tmpbridge
+ local bridge=tmpbridge
+ '[' '!' -e /sys/class/net/tmpbridge/bridge ']'
+ preiftransfer eth0
+ true
+ transfer_addrs eth0 tmpbridge
+ local src="">+ local dst=tmpbridge
+ ip addr show dev tmpbridge
+ egrep -q '^ *inet '
+ ip addr show dev eth0
+ egrep '^ *inet '
+ sed -e '
s/inet/ip addr add/
s/eth0/dev tmpbridge/
+ sh -e
+ ip route list
+ sed -ne '
/dev tmpbridge\( \|$\)/ {
  s/^/ip route del /
+ sh -e
+ ifdown eth0
+ ip link set eth0 name peth0
+ ip link set tmpbridge name eth0
SIOCSIFNAME: Device or resource busy

What do you think?
Did you have the same problem?


Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>