I finally made the jump from using a Physical Ethernet -> VLAN -> Bridge stack to Physical Ethernet Devices -> Bond -> VLANs ->MacvTap. Notice bridges are not included, that’s because they don’t work with Linux bonding, you need to use Macvtap interfaces.
Here’s a sample configuration (you’ll need to install ifenslave & vlan if you haven’t already):
# The loopback network interface auto lo iface lo inet loopback #Intel Interface #1 auto p4p1 iface p4p1 inet manual bond-master bond0 #Intel Interface #2 auto p4p2 iface p4p2 inet manual bond-master bond0 #Onboard Intel NIC auto eth0 iface eth0 inet manual bond-master bond0 #Primary Bond Interface auto bond0 iface bond0 inet manual bond-miimon 100 # Specifies the MII link monitoring frequency in milliseconds. This determines how often the link state of each slave is inspected for link failures. bond-downdelay 200 # Specifies the time, in milliseconds, to wait before disabling a slave after a link failure has been detected. bond-updelay 200 # Specifies the time, in milliseconds, to wait before enabling a slave after a link recovery has been detected. bond-mode 0 # round robin (think of it as network raid 0) bond-slaves none # defined in the interfaces above with bond-master #DMZ VLAN auto bond0.11 # this sets a vlan tag of 11 for all traffic on this interface iface bond0.11 inet manual vlan-raw-device bond0
So, the above will aggregate three NICs and round robin packets across the three interfaces to get the combined output of the three. Once you’ve setup the above, you can go into virt-manager and add a Macvtap interface paired to either the bond0 interface or one of you VLAN bonded interfaces.
I set mine as virtio and mode of bridge. This allows other guests in the same vlan to communicate within the host.