On 16.04.2016 17:09, Mimiko wrote:
Hello.Recently I started to use qemu-kvm for virtualisation. I've setup a bridged network and use it in virtual machine: <network> <name>default</name> <forward mode='bridge'/> <bridge name='virbr0' /> </network> <domain type='kvm'> <name>test</name> <os> <type arch='x86_64' machine='pc-1.1'>hvm</type> <boot dev='network'/> <boot dev='hd'/> </os> <devices> <interface type='bridge'> <mac address='52:54:00:3f:69:98'/> <source bridge='br0'/> <model type='e1000'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </interface> </devices> </domain> When the bond used in the bridge setup is set to 802.3ad, network in guests work ok. When I use bridge mode advanced-alb, network in guests works for some time then starts to timeout connections. What could be the conflict of qemu with advanced-alb mode? This is my specifications: Linux 3.2.0-4-amd64 #1 SMP Debian 3.2.73-2+deb7u3 x86_64 GNU/Linux auto eth0 iface eth0 inet manual auto eth1 iface eth1 inet manual auto bond0 iface bond0 inet manual # load balancing and fault tolerance bond-slaves eth0 eth1 bond-mode 802.3ad #bond-mode balance-alb bond-miimon 100 bond-downdelay 200 bond-updelay 200 up ip link set bond0 mtu 9000 auto br0 iface br0 inet static bridge_ports bond0 bridge_stp off bridge_fd 0 #bridge_maxage 0 bridge_ageing 0 bridge_maxwait 0 up ip link set br0 mtu 9000 I've skipped adress/mask specification. I've tried to enable stp, change mtu, change delay. Nothing helps. Same configuration in interfaces, I change only `bond-mode`. With `bond-mode 802.3ad` everything works ok. With `bond-mode advanced-alb` guest have network problems. The host system does not have any network problem in any mode. Thank you
*filter :FORWARD DROP [0:0] iptables -A FORWARD -i br0 -o br0 -j ACCEPT -- Mimiko desu.
