One of collegues said that configuring bonding on domU does not make sense because the virtual nic on domU and virtual bridge on dom0 may not detect netowrk failure. I think that bonding on domU should work with arp such as below: "options bond0 arp_interval=1000 arp_ip_target=10.25.81.1,10.24.22.70 mode=1 primary=eth1" I tried bonding on domU but it did not work. (domU detected network failure but backup interface did not work properly) Anyone who tried to confiure bonding on bomU? If it worked, would you share bonding configuration files (/etc/modprobe.conf, and ifcfg-*) Thank you in advnace _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 7/12/2010 8:36 PM, dongkyu lee wrote:> One of collegues said that configuring bonding on domU does not make > sense because > the virtual nic on domU and virtual bridge on dom0 may not detect > netowrk failure. > I think that bonding on domU should work with arp such as below: > "options bond0 arp_interval=1000 arp_ip_target=10.25.81.1,10.24.22.70 > mode=1 primary=eth1" > I tried bonding on domU but it did not work. (domU detected network > failure but backup interface did not work properly) > Anyone who tried to confiure bonding on bomU? If it worked, would you > share bonding configuration files (/etc/modprobe.conf, and ifcfg-*) > Thank you in advnace > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-usersYou are looking at this the wrong way I do believe. Bonding needs to be done on dom0 and just have a single interface on the domu. I am sure someone else can explain better than myself, but you would want the failover functionality to be present on the dom0 so all the domu''s benefit, not just one. Just my $0.02. Donny B. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
What you need is two separate things. First is bonding on dom0. Then you need some kind of live failover for the domu''s to another dom0. For the failover I would look into drbd or similar. The reason bonding on the domu won''t work is because if the dom0 crashes, what is going to keep the domu running? The domu has to have the dom0 for at least networking. Donny B. On 7/13/2010 9:39 PM, dongkyu lee wrote:> I appreciate of your reply. > The reason I want to confire bonding on domU is that I have > experienced system failure (system crash,hang) serveral times with two > bondings on dom0. We suspected single bonding works fine but multiple > bonding may cause some problems on xen kernel (dom0). That is why I > tried bonding on domU. > anyone can tell me why I should not configure bodning on domU? > > 2010/7/13 Donny Brooks <dbrooks@mdah.state.ms.us > <mailto:dbrooks@mdah.state.ms.us>> > > On 7/12/2010 8:36 PM, dongkyu lee wrote: >> One of collegues said that configuring bonding on domU does not >> make sense because >> the virtual nic on domU and virtual bridge on dom0 may not detect >> netowrk failure. >> I think that bonding on domU should work with arp such as below: >> "options bond0 arp_interval=1000 >> arp_ip_target=10.25.81.1,10.24.22.70 mode=1 primary=eth1" >> I tried bonding on domU but it did not work. (domU detected >> network failure but backup interface did not work properly) >> Anyone who tried to confiure bonding on bomU? If it worked, would >> you share bonding configuration files (/etc/modprobe.conf, and >> ifcfg-*) >> Thank you in advnace >> >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com <mailto:Xen-users@lists.xensource.com> >> http://lists.xensource.com/xen-users > You are looking at this the wrong way I do believe. Bonding needs > to be done on dom0 and just have a single interface on the domu. I > am sure someone else can explain better than myself, but you would > want the failover functionality to be present on the dom0 so all > the domu''s benefit, not just one. Just my $0.02. > > Donny B. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com <mailto: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
> The reason bonding on the domu won''t work is because if the dom0 > crashes, what is going to keep the domu running? The domu has to have > the dom0 for at least networking.Well obviously domU will fail if dom0 fails. But bonding on dom0 is complicated, and it should certainly work in domU. ...Or why should it not? I believe that''s what OP is asking. -- John Madden Sr UNIX Systems Engineer Ivy Tech Community College of Indiana jmadden@ivytech.edu _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 14 Jul 2010, at 15:41, John Madden wrote:>> The reason bonding on the domu won''t work is because if the dom0 >> crashes, what is going to keep the domu running? The domu has to have >> the dom0 for at least networking. > > Well obviously domU will fail if dom0 fails. But bonding on dom0 is > complicated, and it should certainly work in domU. ...Or why should > it not? I believe that''s what OP is asking.Isn''t bonding dependant on link state? How will domU detect that the primary link is down? Just wondering... Thomas _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users