Xen users - Oct 2007 - xen is causing network problems to Dom0 - bridge problem?

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=eth0
+ 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@\([0-9]\+\.[0-9]\+\.[0-9]\+\.[0-9]\+/[0-9]\+\)@\1@
s/eth0/dev tmpbridge/
''
+ sh -e
+ ip route list
+ sed -ne ''
/dev tmpbridge\( \|$\)/ {
  s/^/ip route del /
  p
}''
+ 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?

Thanks


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

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@gmail.com>:
>
> 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=eth0
> + 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@\([0-9]\+\.[0-9]\+\.[0-9]\+\.[0-9]\+/[0-9]\+\)@\1@
> s/eth0/dev tmpbridge/
> ''
> + sh -e
> + ip route list
> + sed -ne ''
> /dev tmpbridge\( \|$\)/ {
>   s/^/ip route del /
>   p
> }''
> + 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?
>
> Thanks
>
>
>

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