Hello,
did anybody succeed to use Xen 2.0.7 with a Bonding-Device in dom0?
I have configured a Bonding-Device consisting of eth0 and eth1 for
redundancy reasons in dom0. I don''t succeed in using this device with
Xen.
I adopted some scripts in /etc/xen/scripts:
in network:
netdev=${netdev:-bond0}
in vif-route:
main_ip=`ifconfig bond0 | grep "inet addr:" | sed -e
''s/.*inet
addr:\(\w\w*\.\w\w
*\.\w\w*\.\w\w*\).*/\1/''`
but it did''t help.
Is there anything more I can do?
I can''t reach the outside world from a xenU.
Without bonding it works without any problems.
Please help...
Regards
Richard
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Andreas Bach Aaen (AH/TED)
2005-Sep-08 13:46 UTC
Re: [Xen-users] Using bonding-device bond0 for Xen
On Torsdag 08 september 2005 15:28, Richard Mayer wrote:> Hello, > > did anybody succeed to use Xen 2.0.7 with a Bonding-Device in dom0?Yes almost. I have used it with success on Xen 2.0.6> I have configured a Bonding-Device consisting of eth0 and eth1 for > redundancy reasons in dom0. I don''t succeed in using this device with Xen. > I adopted some scripts in /etc/xen/scripts:I have just shortcutted the network script and setup a static configuration elsewhere in Dom0. Remember that interfaces added to a bridge may not have an IP address. You can provide the bridge with an IP address, but not the interfaces attached to it. You must setup a bridge and then add your bond0 interface to the bridge. The DomU''s that you add will then need an entry like: vif = [ ''mac=aa:00:00:00:00:11, bridge=br-bond0'' ] in their configuration. Regards, -- Andreas Bach Aaen System Developer, M. Sc. Ericsson Danmark A/S tel: +45 89 38 51 00 Skanderborgvej 232 fax: +45 89 38 51 01 8260 Viby J Denmark andreas.bach.aaen@ericsson.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thank you very much for the information!
I managed to create a static bridge-device und disabled the
"network"-script. Now I can reach the Xen0 - Domain from the XenU -
Domain but not any further.
This is what I did to my /etc/network/interfaces:
auto bond0
iface bond0 inet static
address ipaddress
gateway gatewayaddress
network networkaddress
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
As I said, I can reach the Xen0-Domain now.
Could you maybe send your configuration file?
This bridge-stuff is pretty new to me... :)
Regards
Richard
Andreas Bach Aaen (AH/TED) wrote:> On Torsdag 08 september 2005 15:28, Richard Mayer wrote:
>
>>Hello,
>>did anybody succeed to use Xen 2.0.7 with a Bonding-Device in dom0?
>
>
> Yes almost. I have used it with success on Xen 2.0.6
>
>
>>I have configured a Bonding-Device consisting of eth0 and eth1 for
redundancy reasons in dom0. I don''t succeed in using this device with
Xen.>>I adopted some scripts in /etc/xen/scripts:
>
>
> I have just shortcutted the network script and setup a static
configuration> elsewhere in Dom0.
> Remember that interfaces added to a bridge may not have an IP address.
You can> provide the bridge with an IP address, but not the interfaces attached
to it.>
> You must setup a bridge and then add your bond0 interface to the bridge.
The DomU''s that you add will then need an entry
like:> vif = [ ''mac=aa:00:00:00:00:11, bridge=br-bond0'' ]
> in their configuration.
>
> Regards,
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Sorry,
actually this is what I tried:
auto br-bond0
iface br-bond0 inet static
address ipaddress
gateway gatewayaddress
network networkaddress
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
Regards
Richard
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Sorry,
actually this is what I tried:
auto br-bond0
iface br-bond0 inet static
address ipaddress
gateway gatewayaddress
network networkaddress
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
Regards
Richard
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Andreas Bach Aaen (AH/TED)
2005-Sep-09 07:16 UTC
Re: [Xen-users] Using bonding-device bond0 for Xen
On Torsdag 08 september 2005 18:52, Richard Mayer wrote:> Thank you very much for the information! > I managed to create a static bridge-device und disabled the > "network"-script. Now I can reach the Xen0 - Domain from the XenU - > Domain but not any further.This might be an normal IP network problem. Do you have a default gateway within the domU?> This is what I did to my /etc/network/interfaces: > > auto bond0 > iface bond0 inet static > address ipaddress > gateway gatewayaddress > network networkaddress > 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-bond0pre-up /usr/sbin/brctl setfd br-bond0 0 might be a good idea to add as well.> pre-up /usr/sbin/brctl addif br-bond0 bond0 > > As I said, I can reach the Xen0-Domain now. > Could you maybe send your configuration file?You won''t gain anything with it, it''s much more complex.> This bridge-stuff is pretty new to me... :)It must be for new stuff for many - and difficult to understand as it''s light on documentation. Regards -- Andreas Bach Aaen System Developer, M. Sc. Ericsson Danmark A/S tel: +45 89 38 51 00 Skanderborgvej 232 fax: +45 89 38 51 01 8260 Viby J Denmark andreas.bach.aaen@ericsson.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
OK, Thank you very much for your help. This option: pre-up /usr/sbin/brctl setfd br-bond0 0 seems to have solved my problem. I''m still getting this warning that Xen0 received a packet with its own address as source: satan:/opt/vmachines/vm1# ping satan-db PING satan-db.dnbond0: received packet with own address as source address but network connectivity of the XenU now seems to be ok! I''ll try if redundancy is also ok when I unplug one of the Ethernet cables... Thanks for your help! On Torsdag 08 september 2005 18:52, Richard Mayer wrote:>> Thank you very much for the information! >> I managed to create a static bridge-device und disabled the >> "network"-script. Now I can reach the Xen0 - Domain from the XenU - >> Domain but not any further.This might be an normal IP network problem. Do you have a default gateway within the domU?>> This is what I did to my /etc/network/interfaces: >> >> auto bond0 >> iface bond0 inet static >> address ipaddress >> gateway gatewayaddress >> network networkaddress >> 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-bond0pre-up /usr/sbin/brctl setfd br-bond0 0 might be a good idea to add as well.>> pre-up /usr/sbin/brctl addif br-bond0 bond0 >> >> As I said, I can reach the Xen0-Domain now. >> Could you maybe send your configuration file?You won''t gain anything with it, it''s much more complex.>> This bridge-stuff is pretty new to me... :)It must be for new stuff for many - and difficult to understand as it''s light on documentation. Regards -- Andreas Bach Aaen System Developer, M. Sc. Ericsson Danmark A/S tel: +45 89 38 51 00 Skanderborgvej 232 fax: +45 89 38 51 01 8260 Viby J Denmark andreas.bach.aaen@ericsson.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
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?
This is the network config of my Xen0:
auto br-bond0
iface br-bond0 inet static
address 193.168.142.120
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
and this is the XenU-Config:
auto eth0
iface eth0 inet static
address 193.168.142.122
netmask 255.255.255.0
gateway 193.168.142.1
network 193.168.142.0
I disabled the /etc/xen/scripts/network script (with exit 0 in the
beginning).
Is there anything else I have to add manually?
Regards
Richard Mayer
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Andreas Bach Aaen (AH/TED)
2005-Sep-12 14:53 UTC
Re: [Xen-users] Using bonding-device bond0 for Xen
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, -- Andreas Bach Aaen System Developer, M. Sc. Ericsson Danmark A/S tel: +45 89 38 51 00 Skanderborgvej 232 fax: +45 89 38 51 01 8260 Viby J Denmark andreas.bach.aaen@ericsson.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
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@lists.xensource.com http://lists.xensource.com/xen-users
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@lists.xensource.com > http://lists.xensource.com/xen-users > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users