Xen users - Nov 2006 - Crash when buildin'' up dual-bridged environment

Hi all,

I''ve a debian etch running Xen with everything upgraded to the latest
packages.

It''s running on 2.6.17-2-xen-686 kernel (from package
linux-image-2.6.17-2-xen-686).

I need to build up a dual-bridge, since all domUs need to be dual-homed.

I''ve configured xend following
http://wiki.xensource.com/xenwiki/XenNetworking:

[...]
#!/bin/sh
dir=$(dirname "$0")
"$dir/network-bridge" "$@" vifnum=0
"$dir/network-bridge" "$@" vifnum=1
[...]

When dom0 comes up, everything seems to work as expected, i think: the
machine is correctly reachable on its "eth0" interface, and I see the
two bridges up:

bridge name     bridge id               STP enabled     interfaces
xenbr0          8000.feffffffffff       no              vif0.0
                                                        peth0
xenbr1          8000.feffffffffff       no              vif0.1
                                                        peth1

The test-domU has been configured as follows:


kernel  = ''/boot/vmlinuz-2.6.17-2-xen-686''
ramdisk = ''/boot/initrd.img-2.6.17-2-xen-686''
memory  = ''256''
root    = ''/dev/sda1 ro''
disk    = [ ''phy:VG00/....'' ]
vif=[ ''ip=147.123.X.Y,bridge=xenbr0'',
''ip=192.168.X.Y,bridge=xenbr1'' ]
on_poweroff = ''destroy''
on_reboot   = ''restart''
on_crash    = ''restart''


This domU works correctly in a single-bridge environment.

The problem is when i create the domU dual-bridged: after joining the
VIFs to the bridges, dom0 crashes...

Is this a known issue? Did I made something wrong?
Is there anybody with a similar setup on the same software? Does it work
for you?

If somebody guides me on how to have the kernel Ooops printed some way
(without using a photocamera, I mean :-D ), i''ll provide it...

Thank you.

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

On Fri, 2006-11-17 at 12:09 +0100, Skull wrote:
> Hi all,
> 
> I''ve a debian etch running Xen with everything upgraded to the
latest
> packages.
> 
> It''s running on 2.6.17-2-xen-686 kernel (from package
> linux-image-2.6.17-2-xen-686).
> 
> I need to build up a dual-bridge, since all domUs need to be dual-homed.
> 
I`m having similar problems, have you gotten any further finding the
cause ? 

greetz
> 
-- 
Kris Buytaert <mlkb@x-tend.be>



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

Kris Buytaert wrote:
>> I''ve a debian etch running Xen with everything upgraded to the
latest
>> packages.
>>
>> It''s running on 2.6.17-2-xen-686 kernel (from package
>> linux-image-2.6.17-2-xen-686).
>>
>> I need to build up a dual-bridge, since all domUs need to be
dual-homed.
> 
> I`m having similar problems, have you gotten any further finding the
> cause ? 
Nope. Other work in queue and I''m still stuck there... :-(

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

(I''ve seen some CC''s on those messages so I kept them - sorry
about
duplicated messages, also I don''t have the message which this thread
was
start)

I''ve run into the same problem some while ago. I''ve figured
what I was
doing wrong : I was putting IP addresses on the bridges and using them
as ''normal'' interfaces in Dom0, besides the bridging. That
gave me a lot
of random panics and/or other problems.

I''ve solved this by using the ''proper'' xen
networking, by using properly
the interfaces provided by netloop module (xen kernel module) and using
veth0/veth1 on Dom0 and adding the vif0.0/vif0.1 into the different
bridges. It worked like a charm.

Other problem that I got into was ... once xend starts and executes the
default network script, it does all the (messy) suff with your
interfaces, renaming eth0 to peth0, veth0 to eth0, copying mac addresses
and so on ...  But (on debian unstable at least) I had some daemons
running before xend was started (bind for example, NFS mounts) and this
messed everything.
So I''ve commented out the xen networking script and wrote my own inside
debian''s network init, so my bridges, interfaces, macs, firewall .. are
done as soon as the network is UP.

My enviroment is working perfectly now, after I figured and fixed a
small problem that I had with the connection tracking with iptables.

I hope that it helped a bit ;)

[]''s

On Wed, 2006-11-29 at 11:35 +0100, Kris Buytaert wrote:
> On Fri, 2006-11-17 at 12:09 +0100, Skull wrote:
> > Hi all,
> > 
> > I''ve a debian etch running Xen with everything upgraded to
the latest
> > packages.
> > 
> > It''s running on 2.6.17-2-xen-686 kernel (from package
> > linux-image-2.6.17-2-xen-686).
> > 
> > I need to build up a dual-bridge, since all domUs need to be
dual-homed.
> 
> > 
> 
> I`m having similar problems, have you gotten any further finding the
> cause ? 
> 
> greetz
> 
> > 

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

On 4 Dec 2006 at 11:33, Theo Cabrerizo Diem wrote:
> and so on ...  But (on debian unstable at least) I had some daemons
> running before xend was started (bind for example, NFS mounts) and this
> messed everything.
Hi!

In SLES10 there are also several networking services started before xend:
NFS, SLP, SSH, NTP, ...

I''m unsure whether this causes problems, because the correct
configuration (XEN
using bonding) did never work reliable (causing broadcast storms, etc.), but a 
somewhat illegal configuration seems to work (specifying the enslaved bonding 
interface to be added to the XEN bridge). I was unable to fix the provided
scripts
to make bonding work as expected...

Regards,
Ulrich


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

Hello

I don''t know about Suse init scripts .. never messed too much with
them,
but I belive that you can do some ''black magic'' with the ifup
scripts
and setup all your ''xen aware network'' once you bring your
interfaces up
(and before any daemon starts).

I starting making some test by not using any network script with xend,
doing all network/bridge/blahblah stuff by hand .. and testing what was
needed or not (and reading xen scripts). I have no problems anymore
related with the ''interface renaming'' (notably bind and squid
needed
restarts after xend).

[]''s

BTW, can someone set the list to force the reply-to address to the list
itself :-P .. so clicking in the reply button would reply to the list,
not to the email''s author ?



On Mon, 2006-12-04 at 13:05 +0100, Ulrich Windl wrote:
> On 4 Dec 2006 at 11:33, Theo Cabrerizo Diem wrote:
> 
> > and so on ...  But (on debian unstable at least) I had some daemons
> > running before xend was started (bind for example, NFS mounts) and
this
> > messed everything.
> 
> Hi!
> 
> In SLES10 there are also several networking services started before xend:
> NFS, SLP, SSH, NTP, ...
> 
> I''m unsure whether this causes problems, because the correct
configuration (XEN
> using bonding) did never work reliable (causing broadcast storms, etc.),
but a
> somewhat illegal configuration seems to work (specifying the enslaved
bonding
> interface to be added to the XEN bridge). I was unable to fix the provided
scripts
> to make bonding work as expected...
> 
> Regards,
> Ulrich
> 

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