Unable to get network connectivity on VMs

[Kyc]

When running VMs I'm having issues getting connectivity to the outside network.

My end goal is to have a private VM network on 192.168.100.* and an external facing network on 172.16.10.*, and both will be physically connected on separate switches but for testing right now everything is connected to one switch.

My interfaces configuration on one of the servers is:

# network interface settingsauto lo
iface lo inet loopback


iface eth0 inet manual


iface eth1 inet manual


iface eth2 inet manual


iface eth3 inet manual


auto bond0
iface bond0 inet manual
        slaves eth2 eth3
        bond-mode 0
        bond-miimon 100
        bond-downdelay 200
        bond-updelay 200


auto bond1
iface bond1 inet manual
        slaves eth0 eth1
        bond-mode 0
        bond-miimon 100
        bond-downdelay 200
        bond-updelay 200


auto vmbr0
iface vmbr0 inet static
        address  192.168.100.90
        netmask  255.255.255.0
        gateway  192.168.100.10
        bridge_ports bond0
        bridge_stp off
        bridge_fd 0




auto vmbr1
iface vmbr1 inet manual
        bridge_ports bond1
        bridge_stp off
        bridge_fd 0

In the VM is have two realtek NICs, one for each bridge. I'm not getting DHCP on either interface. When I assign an IP to the VM vmbr0 NIC (192.168.100.1) I can ping the virtual machine host (192.168.100.90) but nothing else on the network.

Any suggestions on how to move forward?

Thanks!

 

[Kyc]

I took the interfaces out of their bonding and it works now, interfaces config:

# network interface settingsauto lo
iface lo inet loopback


iface eth0 inet manual


iface eth1 inet manual


iface eth2 inet manual


iface eth3 inet manual


auto vmbr0
iface vmbr0 inet static
        address  192.168.100.90
        netmask  255.255.255.0
        gateway  192.168.100.10
        bridge_ports eth2 eth3
        bridge_stp off
        bridge_fd 0




auto vmbr1
iface vmbr1 inet manual
        bridge_ports eth0 eth1
        bridge_stp off
        bridge_fd 0

Both the 192.168.100.* and the 172.16.10.* networks are accessible for inside the VMs now.

I'm wondering of some modes for bonding breaks the bridge... I'll try with active-passive tomorrow and see how that goes.