Fedora xen - Feb 2008 - Custom bridge script; upgrade from Fedora 6 to Fedora 8

Hi,

Since upgrading from Fedora 6 to Fedora 8 my custom bridge script  
stopped working.   I need to have both eth0 and eth1 bridged into each  
XM.   My xen machines are just defined in old-style /etc/xen/foo  
configuration files, like

vif = [ ''mac=00:16:3e:42:08:1d, bridge=xenbr0'',
''mac=00:16:3e:
42:08:1e, bridge=xenbr1'' ]

I''ve changed that to

vif = [ ''mac=00:16:3e:42:08:1d, bridge=eth0'',
''mac=00:16:3e:42:08:1e,
bridge=eth1'' ]

but when I do a "xm create foo" I still end up with the new interfaces
on the wrong bridge!

# brctl show
bridge name	bridge id		STP enabled	interfaces
eth0		8000.0030488c8a26	no		peth0
eth1		8000.0030488c8a27	no		peth1
xenbr0		8000.feffffffffff	no		vif1.0
xenbr1		8000.feffffffffff	no		vif1.1

If I manually move the vifX.X interfaces to the eth0/eth1 bridges then  
everything works.

This is my custom bridge script:

#!/bin/sh
dir=$(dirname "$0")
"$dir/network-bridge" "$@" netdev=eth1 bridge=eth1
"$dir/network-bridge" "$@" netdev=eth0 bridge=eth0

Any ideas?


  - ask

-- 
http://develooper.com/ - http://askask.com/

Any ideas?

Maybe my question could be rephrased as:

How do I convert my /etc/xen configuration files to virsh XML files?


  - ask


Begin forwarded message:
> From: Ask Bjørn Hansen <ask@develooper.com>
> Date: February 10, 2008 1:24:10 AM PST
> To: fedora-xen@redhat.com
> Subject: [Fedora-xen] Custom bridge script; upgrade from Fedora 6 to  
> Fedora 8
>
> Hi,
>
> Since upgrading from Fedora 6 to Fedora 8 my custom bridge script  
> stopped working.   I need to have both eth0 and eth1 bridged into  
> each XM.   My xen machines are just defined in old-style /etc/xen/ 
> foo configuration files, like
>
> vif = [ ''mac=00:16:3e:42:08:1d, bridge=xenbr0'',
''mac=00:16:3e:
> 42:08:1e, bridge=xenbr1'' ]
>
> I''ve changed that to
>
> vif = [ ''mac=00:16:3e:42:08:1d, bridge=eth0'',
''mac=00:16:3e:
> 42:08:1e, bridge=eth1'' ]
>
> but when I do a "xm create foo" I still end up with the new  
> interfaces on the wrong bridge!
>
> # brctl show
> bridge name	bridge id		STP enabled	interfaces
> eth0		8000.0030488c8a26	no		peth0
> eth1		8000.0030488c8a27	no		peth1
> xenbr0		8000.feffffffffff	no		vif1.0
> xenbr1		8000.feffffffffff	no		vif1.1
>
> If I manually move the vifX.X interfaces to the eth0/eth1 bridges  
> then everything works.
>
> This is my custom bridge script:
>
> #!/bin/sh
> dir=$(dirname "$0")
> "$dir/network-bridge" "$@" netdev=eth1 bridge=eth1
> "$dir/network-bridge" "$@" netdev=eth0 bridge=eth0
>
> Any ideas?
>
>
> - ask
>
> -- 
> http://develooper.com/ - http://askask.com/
>
>
> --
> Fedora-xen mailing list
> Fedora-xen@redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-xen


-- 
http://develooper.com/ - http://askask.com/

Ask Bjørn Hansen wrote:
> Any ideas?
> 
> Maybe my question could be rephrased as:
> 
> How do I convert my /etc/xen configuration files to virsh XML files?
> 
> 
start the VM with xm, and when the guest is running, you can do
virsh dumpxml <guestname>

Olivier

Also, while I can''t offer a complete solution, I have used
"logger" (see man
page) to debug network configuration scripts.

Cheers,

Fred.

On Thu, Mar 20, 2008 at 8:44 AM, Olivier Renault <orenault@redhat.com>
wrote:
> Ask Bjørn Hansen wrote:
> > Any ideas?
> >
> > Maybe my question could be rephrased as:
> >
> > How do I convert my /etc/xen configuration files to virsh XML files?
> >
> >
> start the VM with xm, and when the guest is running, you can do
> virsh dumpxml <guestname>
>
> Olivier
>
> --
> Fedora-xen mailing list
> Fedora-xen@redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-xen
>

Hi everyone,

The "best" custom network-bridge script I have come up with was:

#!/bin/sh
dir=$(dirname "$0")
"$dir/network-bridge" "$@" netdev=eth1 bridge=eth1
"$dir/network-bridge" "$@" netdev=eth0 bridge=eth0

I''d prefer however to have the bridges called xenbr0 and xenbr1 -- but
when I try that I end up with half a bridge made and a "tmpbridge"  
device.

Any ideas?   I''m (still) on Fedora 8.


  - ask

On May 7, 2008, at 19:16, Ask Bjørn Hansen wrote:

[ whoops - hit send too soon ]

Hi everyone,

The "best" custom network-bridge script I have come up with was:

#!/bin/sh
dir=$(dirname "$0")
"$dir/network-bridge" "$@" netdev=eth1 bridge=eth1
"$dir/network-bridge" "$@" netdev=eth0 bridge=eth0

I''d prefer however to have the bridges called xenbr0 and xenbr1 -- but
when I try that I end up with half a bridge made and a "tmpbridge"  
device.

For example with this script:

#!/bin/sh
dir=$(dirname "$0")

"$dir/network-bridge" "$@" vifnum=1 bridge=xenbr1
netdev=eth1
"$dir/network-bridge" "$@" vifnum=0 bridge=xenbr0
netdev=eth0

I end up with this:

[root@app1 ~]# /etc/xen/scripts/solfo-network-bridge start
Nothing to flush.
Waiting for peth1 to negotiate link...SIOCGIFFLAGS: No such device
Error for wireless request "Set Encode" (8B2A) :
     SET failed on device eth1 ; No such device.
SIOCGIFFLAGS: No such device
Failed to bring up eth1.
Error: either "local" is duplicate, or "secondary" is a
garbage.

[root@app1 ~]# brctl show
bridge name	bridge id		STP enabled	interfaces
tmpbridge		8000.000000000000	no		
xenbr1		8000.0030488a53ef	no		peth1


Any ideas?   I''m (still) on Fedora 8.


  - ask

-- 
http://www.askbjoernhansen.com/