[Xen-users] Re: network-bridge fails leaving tmpbridge around

["Daniel P. Berrange" <berrange@xxxxxxxxxx>]

On Fri, May 11, 2007 at 12:12:52PM +0100, Richard W.M. Jones wrote:
> 'service xend start' is failing in the network-bridge script.  It fails 
> in such a way as to kill the network completely and leave tmpbridge around.

Can you capture

  ifconfig -a
  brctl show
  ip route show

Before & after doing the service xend start. 

> 
> I modified network-bridge by adding at the top:
> 
>       #!/bin/bash
>       
>       exec 2>/tmp/log
>       set -x
> 
> so that I could see what commands are failing.  The complete log is 
> attached, but it turns out that the last thing logged is:
> 
>       + ifdown eth0
>       + ip link set eth0 name peth0
>       + ip link set tmpbridge name eth0
>       SIOCSIFNAME: Device or resource busy

I'm puzzelled how the eth0 name can be busy, when we just renamed
it (apparently without error) to be peth0 instead.

> so it would seem to be failing here:
> 
>       op_start () {
>       #...
>       #...
>           if ! ifdown ${netdev}; then
>               # If ifdown fails, remember the IP details.
>               get_ip_info ${netdev}
>               ip link set ${netdev} down
>               ip addr flush ${netdev}
>           fi
>           ip link set ${netdev} name ${pdev}
>           ip link set ${tdev} name ${bridge}    <--- fails
> 
> It's strange because tmpbridge has just been created and eth0 is down, 
> so how can either device be busy?

Indeed, very odd.

Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

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