| |
|
 |
|
 |
|
|
|
| |
|
|
xen-users
Re: [Xen-users] Using bonding-device bond0 for Xen
So,
I tried my configuration with Xen 2.0 testing and Kernel 2.6.12 now
and it made no difference.
In my Syslog, these Messages appear:
Sep 12 22:38:10 satan kernel: bond0: received packet with own
address as source
address
and the network connection of XenU breaks after about 10 Minutes.
Does anybody know, if this in normal or may this be my problem?
I'm about to give up bonding network interfaces with Xen.. ;(
#auto br-bond0
#iface br-bond0 inet static
# address 193.168.142.121
# gateway 193.168.142.1
# network 193.168.142.0
# netmask 255.255.255.0
# pre-up /sbin/ifconfig eth0 up
# pre-up /sbin/ifconfig eth1 up
# pre-up /sbin/ifconfig bond0 up
# pre-up /sbin/ifenslave bond0 eth0
# pre-up /sbin/ifenslave bond0 eth1
# pre-up /usr/sbin/brctl addbr br-bond0
# pre-up /usr/sbin/brctl addif br-bond0 bond0
# pre-up /usr/sbin/brctl stp br-bond0 off
# pre-up /usr/sbin/brctl setfd br-bond0 0
On Sep 12, 2005, at 5:14 PM, Richard Mayer wrote:
No,
neither Dom0 nor DomU freeze and I'm not using NFS for the root
file-systems at the moment.
Everything works without any problem - only the network connection
seems
to be gone.
I can still ping the XenU from Xen0. But i cannot ping Xen0 from XenU.
Every seems to be very strange to me.
I have two parallel installations and the problems is present on both
machines.
Could it have to do anything with the Subnet-Mask of the Bridge
Device.
I have taken a look at some other "standard"-Xen Installation and
there,
the Bridge Network Device uses the Network Mask 255.255.255.255.
For my statically configured bridge I'm using 255.255.255.0 because
otherwise it wouldn't work...
Regards
Richard Mayer
On Mandag 12 september 2005 16:41, Richard Mayer wrote:
Hello,
I'm still running into problems with bonding.
When I boot the server, everything seems to be fine and I have no
problems
with network connectivity. I can reach XenU und also reach the
outside
world from XenU. However, after a while of doing nothing with the
virtual
Machines (about 10-15 minutes) the network connection is gone.
I can't reach XenU anymore and when logging in through xm console
I can't
reach any other IP Address from within the XenU.
Do you have any idea, what the reason for this behavour might be?
Does the domU freeze?
Does you DomU have it's root filesystem mounted via nfs?
Please make sure that you can ping any sizes of packages from the
domU to
your
nfs server. You may need to set package sizes used by nfs down to a
low value
e.g. 1024 to make sure al packages are so small that you don't need IP
fragmentation. Maybe you will need to lower you MTU of the eth0
interface
inside the domU.
If you domU doesn't freeze or you don't use rootfs over nfs, then you
probably
need to look elsewhere for the source of your problems.
Regards,
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
| |
|
Home