Hi guys, I am trying to get bonding work on a debian etch system. I searched already in the mailing list but unfortunately I couldnt find a proper solution. This is what i did so far. - Installed Debian Etch on my server - Installed the following packages for using Xen from the Debian repository: xen-hypervisor-3.0.3-1-i386-pae linux-image-2.6.18-5-xen-686 linux-image-2.6.18-5-xen-686 xen-tools libc6-xen bridge-utils - Setup bonding like this: /etc/modprobe.d/arch/i386 ========================alias bond0 bonding options bond0 mode=6 miimon=50 /etc/network/interfaces ======================auto eth0 eth1 auto bond0 iface bond0 inet static address 10.3.4.2 netmask 255.255.255.0 network 10.3.4.0 broadcast 10.3.4.255 gateway 10.3.4.1 up /sbin/ifenslave bond0 eth0 down /sbin/ifenslave -d bond0 eth0 ======================================= Everything is working fine so far. To get bonding (kind of) working with xen I read the following howto: http://vandelande.com/guides/howto%20setup%20XEN%20using%20network%20bonding%20on%20SLES10.html I took the posted script and saved is as /etc/xen/scripts/network-bonding-bridge If I run the script the according devices are created. So far so good. The next I created a domU. My setup is quit simple: =============================================kernel = ''/boot/vmlinuz-2.6.18-5-xen-686'' ramdisk = ''/boot/initrd.img-2.6.18-5-xen-686'' memory = ''256'' root = ''/dev/sda1 ro'' disk [''phy:/dev/sda8,sda1,w'',''phy:/dev/sda9,sda2,w'',''phy:/dev/sda10,sda3,w'' ] name = ''vm_mydomU'' vif=[ ''ip=10.3.4.3'' ] dhcp="off" netmask=''255.255.255.000'' gateway=''10.3.4.1'' ============================================= If I start the domU there are no error-messages at all. The connection works for a (very) short while. For example if I send a ping to a random host (internal or external), the connection works for around 5 or 6 ICMP-message-replies. Then the connection brakes down. Kind of the same problem was already described on the list in the following post: http://lists.xensource.com/archives/html/xen-users/2007-04/msg00236.html Unfortunately nobody answered. :-/ I hope someone got bonding to work with xen and could describe me what I am doing wrong. Would be glad to get some help. Cheers, Artur -- "There are 10 kinds of people in the world, those who understand binary math, and those who don''t." _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Pierre-Alain RIVIERE
2007-Oct-16 12:06 UTC
Re: [Xen-users] Xen with NIC Bonding on Debian Etch ?
Hello, As far as I''m concerned I have no problem with NIC bonding on Xen. I''ve used the following to get it working : http://anothergeekwebsite.com/fr/2007/06/xen-vlan-et-bonding-oui-oui-tout-ca (sorry it''s in french but only the configuration files are important) OK, there''s also VLAN support but you can drop this part, it is likely the same. It seems I proceed the same way as you but for the xen network script. Artur Mücke wrote:> Hi guys, > > I am trying to get bonding work on a debian etch system. I searched > already in the mailing list but unfortunately I couldnt find a proper > solution. This is what i did so far. > > - Installed Debian Etch on my server > - Installed the following packages for using Xen from the Debian repository: > > xen-hypervisor-3.0.3-1-i386-pae > linux-image-2.6.18-5-xen-686 > linux-image-2.6.18-5-xen-686 > xen-tools > libc6-xen > bridge-utils > > - Setup bonding like this: > > /etc/modprobe.d/arch/i386 > ========================> alias bond0 bonding > options bond0 mode=6 miimon=50 > > /etc/network/interfaces > ======================> auto eth0 eth1 > > auto bond0 > iface bond0 inet static > address 10.3.4.2 > netmask 255.255.255.0 > network 10.3.4.0 > broadcast 10.3.4.255 > gateway 10.3.4.1 > up /sbin/ifenslave bond0 eth0 > down /sbin/ifenslave -d bond0 eth0 > =======================================> > Everything is working fine so far. To get bonding (kind of) working with > xen I read the following howto: > > http://vandelande.com/guides/howto%20setup%20XEN%20using%20network%20bonding%20on%20SLES10.html > > I took the posted script and saved is as > /etc/xen/scripts/network-bonding-bridge > > If I run the script the according devices are created. > > So far so good. > > The next I created a domU. My setup is quit simple: > > =============================================> kernel = ''/boot/vmlinuz-2.6.18-5-xen-686'' > ramdisk = ''/boot/initrd.img-2.6.18-5-xen-686'' > memory = ''256'' > root = ''/dev/sda1 ro'' > disk > [''phy:/dev/sda8,sda1,w'',''phy:/dev/sda9,sda2,w'',''phy:/dev/sda10,sda3,w'' ] > name = ''vm_mydomU'' > > vif=[ ''ip=10.3.4.3'' ] > dhcp="off" > netmask=''255.255.255.000'' > gateway=''10.3.4.1'' > =============================================> > If I start the domU there are no error-messages at all. The connection > works for a (very) short while. For example if I send a ping to a random > host (internal or external), the connection works for around 5 or 6 > ICMP-message-replies. Then the connection brakes down. Kind of the same > problem was already described on the list in the following post: > > http://lists.xensource.com/archives/html/xen-users/2007-04/msg00236.html > > Unfortunately nobody answered. :-/ > > I hope someone got bonding to work with xen and could describe me what I > am doing wrong. > > Would be glad to get some help. > > Cheers, > > Artur > > > > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Pierre-Alain RIVIERE wrote:> Artur Mücke wrote: >> Pierre-Alain RIVIERE wrote: >> >>> Hello, >>> >>> As far as I''m concerned I have no problem with NIC bonding on Xen. >>> >>> I''ve used the following to get it working : >>> http://anothergeekwebsite.com/fr/2007/06/xen-vlan-et-bonding-oui-oui-tout-ca >>> >>> (sorry it''s in french but only the configuration files are important) >>> >>> OK, there''s also VLAN support but you can drop this part, it is likely >>> the same. >>> >>> It seems I proceed the same way as you but for the xen network script. >>> >>> >>> Artur Mücke wrote: >>> >>>> Hi guys, >>>> >>>> I am trying to get bonding work on a debian etch system. I searched >>>> already in the mailing list but unfortunately I couldnt find a proper >>>> solution. This is what i did so far. >>>> >>>> - Installed Debian Etch on my server >>>> - Installed the following packages for using Xen from the Debian >>>> repository: >>>> >>>> xen-hypervisor-3.0.3-1-i386-pae >>>> linux-image-2.6.18-5-xen-686 >>>> linux-image-2.6.18-5-xen-686 >>>> xen-tools >>>> libc6-xen >>>> bridge-utils >>>> >>>> - Setup bonding like this: >>>> >>>> /etc/modprobe.d/arch/i386 >>>> ========================>>>> alias bond0 bonding >>>> options bond0 mode=6 miimon=50 >>>> >>>> /etc/network/interfaces >>>> ======================>>>> auto eth0 eth1 >>>> >>>> auto bond0 >>>> iface bond0 inet static >>>> address 10.3.4.2 >>>> netmask 255.255.255.0 >>>> network 10.3.4.0 >>>> broadcast 10.3.4.255 >>>> gateway 10.3.4.1 >>>> up /sbin/ifenslave bond0 eth0 >>>> down /sbin/ifenslave -d bond0 eth0 >>>> =======================================>>>> >>>> Everything is working fine so far. To get bonding (kind of) working >>>> with >>>> xen I read the following howto: >>>> >>>> http://vandelande.com/guides/howto%20setup%20XEN%20using%20network%20bonding%20on%20SLES10.html >>>> >>>> >>>> >>>> I took the posted script and saved is as >>>> /etc/xen/scripts/network-bonding-bridge >>>> >>>> If I run the script the according devices are created. >>>> >>>> So far so good. >>>> >>>> The next I created a domU. My setup is quit simple: >>>> >>>> =============================================>>>> kernel = ''/boot/vmlinuz-2.6.18-5-xen-686'' >>>> ramdisk = ''/boot/initrd.img-2.6.18-5-xen-686'' >>>> memory = ''256'' >>>> root = ''/dev/sda1 ro'' >>>> disk >>>> [''phy:/dev/sda8,sda1,w'',''phy:/dev/sda9,sda2,w'',''phy:/dev/sda10,sda3,w'' >>>> ] >>>> name = ''vm_mydomU'' >>>> >>>> vif=[ ''ip=10.3.4.3'' ] >>>> dhcp="off" >>>> netmask=''255.255.255.000'' >>>> gateway=''10.3.4.1'' >>>> =============================================>>>> >>>> If I start the domU there are no error-messages at all. The connection >>>> works for a (very) short while. For example if I send a ping to a >>>> random >>>> host (internal or external), the connection works for around 5 or 6 >>>> ICMP-message-replies. Then the connection brakes down. Kind of the same >>>> problem was already described on the list in the following post: >>>> >>>> http://lists.xensource.com/archives/html/xen-users/2007-04/msg00236.html >>>> >>>> >>>> Unfortunately nobody answered. :-/ >>>> >>>> I hope someone got bonding to work with xen and could describe me >>>> what I >>>> am doing wrong. >>>> >>>> Would be glad to get some help. >>>> >>>> Cheers, >>>> >>>> Artur >>>> >>>> >>>> >>>> >>>> >>>> >> >> Thx for your quick reply. I''ll try to understand the french howto and >> will get back to you later. I hope I am gonna get it work. Will >> definitely post it here. >> >> > I''m the writer so if there''s any problem about this howto tell me. > > By the way, you forgot to CC to xen-users.Thx for your quick reply. I''ll try to understand the french howto and will get back to you later. I hope I am gonna get it work. Will definitely post it here. -- "There are 10 kinds of people in the world, those who understand binary math, and those who don''t." _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Pierre-Alain RIVIERE wrote:> Artur Mücke wrote: >> Pierre-Alain RIVIERE wrote: >> >>> Hello, >>> >>> As far as I''m concerned I have no problem with NIC bonding on Xen. >>> >>> I''ve used the following to get it working : >>> http://anothergeekwebsite.com/fr/2007/06/xen-vlan-et-bonding-oui-oui-tout-ca >>> >>> (sorry it''s in french but only the configuration files are important) >>> >>> OK, there''s also VLAN support but you can drop this part, it is likely >>> the same. >>> >>> It seems I proceed the same way as you but for the xen network script. >>> >>>Im back. Unfortunately its not working yet but I dont know why. This is what I did, after I read your howto and (kind of) understood it: The configuration looks different in debian but I think that doesnt care. /etc/modprobe.d/arch/i386 ========================alias bond0 bonding options bond0 miimon=100 mode=0 Its different to your setup but I think that should alright or am I wrong? Moreover my network differs from yours. I have only one network, so I dont need two bridges or do I? /etc/xen/scripts/bonding-bridge ==============================#!/bin/sh dir=$(dirname "$0") "$dir/network-bridge" "$@" vifnum=0 bridge=xenbr0 /etc/xen/xend-config.sxp =======================Replaced: (network-script network-bridge) with: network-script bonding-bridge) My domU: /etc/xen/vm_test.sxp ===================vif = [''mac=02:00:00:00:00:01, bridge=xenbr0''] If i restart the xen-daemon, the network connection brakes down. So after the creation of the xenbr0 and the other devices took place, the connection network connection isnt working anymore. I cant reach any host by ICMP in my network. Any ideas what I am doing wrong? Cheers, Artur "There are 10 kinds of people in the world, those who understand binary math, and those who don''t." _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, 2007-10-16 at 16:04 +0200, Artur Mücke wrote:> > > Unfortunately its not working yet but I dont know why. This is what I > did, after I read your howto and (kind of) understood it: > > The configuration looks different in debian but I think that doesnt > care. > > /etc/modprobe.d/arch/i386 > ========================> alias bond0 bonding > options bond0 miimon=100 mode=0It may be significant that mode=0 is different from mode=6. This may become significant on an ethernet bridge, where you''re already horking with layer 2 (MAC''s) and the failure you''re seeing sounds like an ARP problem, so... I wasn''t able to get anything other than mode=1 to work and I assume it''s due to ARP issues. Everything in dom0 works just fine, but as soon as a domU tries to ping something on the same subnet, its connection drops. It seems to me that bonding, bridging, and Xen don''t really work. Why else would there be no formal documentation on this from Xen/Xensource, Red Hat, etc? =) John -- 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
Don''t interpret a lack of documentation to mean anything. All xen docs are horribly neglected. If you get your problem sorted out, you might want to add a blurb to the wiki.> It seems to me that bonding, bridging, and Xen don''t really work. Why > else would there be no formal documentation on this from Xen/Xensource, > Red Hat, etc? =) > > John_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
John Madden wrote:> On Tue, 2007-10-16 at 16:04 +0200, Artur Mücke wrote: > >> Unfortunately its not working yet but I dont know why. This is what I >> did, after I read your howto and (kind of) understood it: >> >> The configuration looks different in debian but I think that doesnt >> care. >> >> /etc/modprobe.d/arch/i386 >> ========================>> alias bond0 bonding >> options bond0 miimon=100 mode=0 >> > > It may be significant that mode=0 is different from mode=6. This may > become significant on an ethernet bridge, where you''re already horking > with layer 2 (MAC''s) and the failure you''re seeing sounds like an ARP > problem, so... > > I wasn''t able to get anything other than mode=1 to work and I assume > it''s due to ARP issues. Everything in dom0 works just fine, but as soon > as a domU tries to ping something on the same subnet, its connection > drops. > > It seems to me that bonding, bridging, and Xen don''t really work. Why > else would there be no formal documentation on this from Xen/Xensource, > Red Hat, etc? =) > > John > > > >While it''s not "official" documentation, I have a how-to written for Xen + bonding + vlans on RHEL 5 using mixed bond modes (1 and 4 LACP). http://www.certifried.com/files/Xen_networking.odt again, this is all on RHEL 5, so you maybe won''t get so much out of it since you''re running Debian. So far we have 6 bridges configured that are each on different VLANs and I can mix and match any combination inside the VM (up to 4 of couse since that''s the eth limit inside a VM currently). This all over bonded copper (mode 1) and bonded fiber (mode 4). Mark _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Mark Nielsen wrote:> John Madden wrote: >> On Tue, 2007-10-16 at 16:04 +0200, Artur Mücke wrote: >> >>> Unfortunately its not working yet but I dont know why. This is what I >>> did, after I read your howto and (kind of) understood it: >>> >>> The configuration looks different in debian but I think that doesnt >>> care. >>> >>> /etc/modprobe.d/arch/i386 >>> ========================>>> alias bond0 bonding >>> options bond0 miimon=100 mode=0 >> >> It may be significant that mode=0 is different from mode=6. This may >> become significant on an ethernet bridge, where you''re already horking >> with layer 2 (MAC''s) and the failure you''re seeing sounds like an ARP >> problem, so... >> >> I wasn''t able to get anything other than mode=1 to work and I assume >> it''s due to ARP issues. Everything in dom0 works just fine, but as soon >> as a domU tries to ping something on the same subnet, its connection >> drops. >> >> It seems to me that bonding, bridging, and Xen don''t really work. Why >> else would there be no formal documentation on this from Xen/Xensource, >> Red Hat, etc? =) >> >> John >> >> >> >> > While it''s not "official" documentation, I have a how-to written for Xen > + bonding + vlans on RHEL 5 using mixed bond modes (1 and 4 LACP). > http://www.certifried.com/files/Xen_networking.odt > > again, this is all on RHEL 5, so you maybe won''t get so much out of it > since you''re running Debian. So far we have 6 bridges configured that > are each on different VLANs and I can mix and match any combination > inside the VM (up to 4 of couse since that''s the eth limit inside a VM > currently). This all over bonded copper (mode 1) and bonded fiber (mode 4). > > Mark >Hi guys, thx for your answers. Sorry, I havent been at my computer yesterday anymore. I will try to get it work today and let you know if its working. Cheers Artur -- "There are 10 kinds of people in the world, those who understand binary math, and those who don''t." _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users