Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I was wondering if anyone has any experience with setting up LACP (802.3ad dynamic link aggregation) & a bridge for use with KVM.
I have a HP ML370 with 2 x gigabit nics that I installed Centos 6.4 & KVM (virgin run with KVM). To keep it simple I just configured 1 nic, and setup a bridge (as the docs recommended). This setup worked fine, and I am using QEMU on a separate Slackware box to admin the guests. I was able to access the host & the guests no problem.
I would like to take advantage of both nics on the server & would like to setup LACP (bonding mode 4) + the Bridge. I am no stranger to LACP, and all my servers with more than 2 nics are setup this way. No problem.
The problem I am having is getting the bonded links to work with the bridge. Does anyone know how to do this? I currently have the bond 4 working, and can confirm on the switch that LACP partnership is active & up. I cannot ping/access the guests anymore, and the guests (using the bridge) cannot access anything.
Up to this point bonding works, I can ping the host, and the host can access outbound.
When I originally configged the KVM bridge I called it br0, so I would like to keep this name so I don't have to redo everything.
Some of the docs online mention I need to setup a tagged vlan on the switch for this config. Is this true, do I really need a vlan?
I did setup a tagged vlan (vlan11), and added the following ifcfg files, but no dice.
So, do I really need a vlan setup on the switch for this config?
If not I suppose I can ditch the ifcfg-bond0.11 config file, and remove the tagged vlan from the switch? If this is the case, can I simply add BRIDGE=br0 to the bond0 config, and remove the VLAN & STP from the br0 config?
I was able to solve the problem. VLAN is not required, so I deleted the vlan from the switch, and removed it from the config files.
I changed the bond0 config to layer 2, and added the BRIDGE setup. Made the br0 (bridge) config layer 3.
Here are the config files for the LACP (2 nics) + Bridge setup for KVM in case anyone else needs help with this type of setup (Centos).