[Bug 1153364] Re: trouble with guest network connectivity when host is using a bonded interface

[ben thielsen]

some more information - while running a ping from another physical host,
against a guest, i did a bit of testing with tshark:

192.168.1.123 - other physical host on network
192.168.1.60 - virtual host
192.168.1.70 - virtual guest

on the virtual host, the current active slave is eth0, so i started
there:

>cat /proc/net/bonding/bond0 
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

Bonding Mode: adaptive load balancing
Primary Slave: None
Currently Active Slave: eth0
MII Status: up
MII Polling Interval (ms): 0
Up Delay (ms): 0
Down Delay (ms): 0

Slave Interface: eth0
MII Status: up
Speed: 100 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 00:19:b9:ec:43:f1
Slave queue ID: 0

tshark appears to indicate that the ping requests are reaching the physical interface on the virtual host:
>tshark -i eth0 'icmp[icmptype]==icmp-echo'
Capturing on eth0
  0.000000 192.168.1.123 -> 192.168.1.70 ICMP 98 Echo (ping) request  id=0xa494, seq=540/7170, ttl=64
  1.000273 192.168.1.123 -> 192.168.1.70 ICMP 98 Echo (ping) request  id=0xa494, seq=541/7426, ttl=64
  2.001328 192.168.1.123 -> 192.168.1.70 ICMP 98 Echo (ping) request  id=0xa494, seq=542/7682, ttl=64
  3.002381 192.168.1.123 -> 192.168.1.70 ICMP 98 Echo (ping) request  id=0xa494, seq=543/7938, ttl=64
^C4 packets captured

next, tshark appears to indicate that the ping requests are reaching the bond interface:
>tshark -i bond0 'icmp[icmptype]==icmp-echo'
Capturing on bond0
  0.000000 192.168.1.123 -> 192.168.1.70 ICMP 98 Echo (ping) request  id=0xa494, seq=796/7171, ttl=64
  1.001077 192.168.1.123 -> 192.168.1.70 ICMP 98 Echo (ping) request  id=0xa494, seq=797/7427, ttl=64
  2.001996 192.168.1.123 -> 192.168.1.70 ICMP 98 Echo (ping) request  id=0xa494, seq=798/7683, ttl=64
  3.002751 192.168.1.123 -> 192.168.1.70 ICMP 98 Echo (ping) request  id=0xa494, seq=799/7939, ttl=64
^C4 packets captured

continuing on, tshark appears to indicate that the ping requests are reaching the bridge interface:
>tshark -i br0 'icmp[icmptype]==icmp-echo'
Capturing on br0
  0.000000 192.168.1.123 -> 192.168.1.70 ICMP 98 Echo (ping) request  id=0xa494, seq=665/39170, ttl=64
  1.001045 192.168.1.123 -> 192.168.1.70 ICMP 98 Echo (ping) request  id=0xa494, seq=666/39426, ttl=64
  2.001173 192.168.1.123 -> 192.168.1.70 ICMP 98 Echo (ping) request  id=0xa494, seq=667/39682, ttl=64
  3.002232 192.168.1.123 -> 192.168.1.70 ICMP 98 Echo (ping) request  id=0xa494, seq=668/39938, ttl=64
  4.003298 192.168.1.123 -> 192.168.1.70 ICMP 98 Echo (ping) request  id=0xa494, seq=669/40194, ttl=64
^C5 packets captured

while doing each of these captures, i was running a matching capture on
the guest, and did not see any of these packets.  while i'm not quite
sure what [if any] the implication is, it would seem that somehow, the
packets are getting lost on their way to the guest, after they reach the
bridge interface.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1153364

Title:
  trouble with guest network connectivity when host is using a bonded
  interface

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1153364/+subscriptions