Xen users - Oct 2013 - bridged networking doesn't bring up eth0: RTNETLINK answers: File exists

I am running Xen on Debian wheezy. I switched from routed networking to bridged
networking. Now I can''t seem to get eth0 to come up. When the network
script
tries to bring it up, it gets an error: RTNETLINK answers: File exists

Any tips? details below

brian

root@trout:/etc/xen# egrep -v ''#|^ *$'' xend-config.sxp
(network-script network-bridge)
(vif-script vif-bridge)
(dom0-min-mem 196)
(enable-dom0-ballooning yes)
(total_available_memory 0) 
(dom0-cpus 0)
(vncpasswd '''')

root@trout:/etc/xen#  ifup eth0
ifdown: interface eth0 not configured
RTNETLINK answers: File exists

root@trout:~# brctl show
bridge name	bridge id		STP enabled	interfaces
eth0		8000.8c89a511f016	no		peth0

root@trout:~# cat /etc/network/interfaces
# The primary network interface
auto eth0

iface eth0 inet static
        address 173.228.81.234
        broadcast 173.228.81.255
        netmask 255.255.255.0
        gateway 173.228.81.1

-- 
Brian Lavender
http://www.brie.com/brian/

"There are two ways of constructing a software design. One way is to
make it so simple that there are obviously no deficiencies. And the other
way is to make it so complicated that there are no obvious deficiencies."

Professor C. A. R. Hoare
The 1980 Turing award lecture

Hmm, I guess the (network-script network-bridge) isn''t supported
anymore.
http://wiki.xen.org/wiki/Host_Configuration/Networking#Example_Debian-style_bridge_configuration_.28e.g._Debian.2C_Ubuntu.29

On Sat, Oct 05, 2013 at 04:56:06PM -0700, Brian Lavender
wrote:
> I am running Xen on Debian wheezy. I switched from routed networking to
bridged
> networking. Now I can''t seem to get eth0 to come up. When the
network script
> tries to bring it up, it gets an error: RTNETLINK answers: File exists
> 
> Any tips? details below
> 
> brian
> 
> root@trout:/etc/xen# egrep -v ''#|^ *$'' xend-config.sxp
> (network-script network-bridge)
> (vif-script vif-bridge)
> (dom0-min-mem 196)
> (enable-dom0-ballooning yes)
> (total_available_memory 0) 
> (dom0-cpus 0)
> (vncpasswd '''')
> 
> root@trout:/etc/xen#  ifup eth0
> ifdown: interface eth0 not configured
> RTNETLINK answers: File exists
> 
> root@trout:~# brctl show
> bridge name	bridge id		STP enabled	interfaces
> eth0		8000.8c89a511f016	no		peth0
> 
> root@trout:~# cat /etc/network/interfaces
> # The primary network interface
> auto eth0
> 
> iface eth0 inet static
>         address 173.228.81.234
>         broadcast 173.228.81.255
>         netmask 255.255.255.0
>         gateway 173.228.81.1
> 
> -- 
> Brian Lavender
> http://www.brie.com/brian/
> 
> "There are two ways of constructing a software design. One way is to
> make it so simple that there are obviously no deficiencies. And the other
> way is to make it so complicated that there are no obvious
deficiencies."
> 
> Professor C. A. R. Hoare
> The 1980 Turing award lecture
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users
-- 
Brian Lavender
http://www.brie.com/brian/

"There are two ways of constructing a software design. One way is to
make it so simple that there are obviously no deficiencies. And the other
way is to make it so complicated that there are no obvious deficiencies."

Professor C. A. R. Hoare
The 1980 Turing award lecture

On Sat, 2013-10-05 at 23:31 -0700, Brian Lavender wrote:
> Hmm, I guess the (network-script network-bridge) isn''t supported
anymore.
>
http://wiki.xen.org/wiki/Host_Configuration/Networking#Example_Debian-style_bridge_configuration_.28e.g._Debian.2C_Ubuntu.29
Correct, it was fragile and prone to weird breakage. AFAIK it has always
been disabled and not recommended by the Debian maintainer and more
recently (allow this a couple of releases ago, IIRC) upstream followed
suite.

Ian.