no worries. i'm a bit embarrassed i couldn't offer a more directed initial report.
i do believe the vhost_net module is installed and working: >lsmod | grep -i vhost vhost_net 31874 1 macvtap 18294 1 vhost_net >pp | grep -i vhost root 2534 1 3 22:11 ? 00:00:22 /usr/bin/kvm -name aurora -S -M pc-1.0 -cpu core2duo,+lahf_lm,+dca,+xtpr,+cx16,+tm2,+est,+vmx,+ds_cpl,+pbe,+tm,+ht,+ss,+acpi,+ds -enable-kvm -m 1024 -smp 1,sockets=1,cores=1,threads=1 -uuid 542c39da-f539-6014-6f91-36575f0aef4e -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/aurora.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -device ahci,id=ahci0,bus=pci.0,addr=0x4 -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/srv/vc/disks/aurora,if=none,id=drive-sata0-0-0,format=qcow2 -device ide-hd,bus=ahci0.0,drive=drive-sata0-0-0,id=sata0-0-0,bootindex=1 -drive if=none,media=cdrom,id=drive-sata0-0-1,readonly=on,format=raw -device ide-cd,bus=ahci0.1,drive=drive-sata0-0-1,id=sata0-0-1 -netdev tap,fd=21,id=hostnet0,vhost=on,vhostfd=22 -device virtio-net-pci,tx=bh,netdev=hostnet0,id=net0,mac=52:54:00:f3:b2:32,bus=pci.0,addr=0x3 -vnc 0.0.0.0:0 -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 i've tested with lxc as you ask - it seems to not exhibit this problem. pings both from the container/guest against other devices on the network, as well as pings against the container/guest. i did notice, with some consistency, duplicate pings - but i know that this is sometimes simply just a largely innocuous side affect of certain types of load balancing, so i'm not necessarily terribly concerned about that. in addition, connectivity to the guest/container in general seemed to be fine, which which not the case with the prior testing. a couple of other notes to add that i've come across [or remembered] since my previous post. i have since also tested with balance-tlb, and this seems to work ok, with no symptoms of intermittent network connectivity - both for my kvm guests, as well as the lxc container/guest. also, i had forgotten about it when i initially wrote up this submission, but initially, i was using macvtap for my kvm guest network connectivity, and this is where i first saw the symptoms. i then switched to using a bridged setup, partially to test things further, but also for also reasons related to some of the limitations of macvtap [specifically guests not being able to communicate with the host when using the same interface]. ultimately, i intend to stay with the bridged configuration, because of this, but wanted to mention that the symptoms do appear to be present with both. lastly, one other possibly interesting bit of info - as i was testing again this morning with balance-alb and lxc, i tested again with a kvm guest to ensure the symptom was still present. this time when pinging, not only were the symptoms still present, i saw some behavior i hadn't noticed previously: ping aurora PING aurora.example.com (192.168.1.70): 56 data bytes 64 bytes from 192.168.1.70: icmp_seq=0 ttl=64 time=0.466 ms 92 bytes from xenon.example.com (192.168.1.60): Redirect Host(New addr: 192.168.1.70) Vr HL TOS Len ID Flg off TTL Pro cks Src Dst 4 5 00 0054 7b83 0 0000 3f 01 7c14 192.168.1.123 192.168.1.70 64 bytes from 192.168.1.70: icmp_seq=1 ttl=64 time=0.279 ms 92 bytes from xenon.example.com (192.168.1.60): Redirect Host(New addr: 192.168.1.70) Vr HL TOS Len ID Flg off TTL Pro cks Src Dst 4 5 00 0054 19c2 0 0000 3f 01 ddd5 192.168.1.123 192.168.1.70 64 bytes from 192.168.1.70: icmp_seq=2 ttl=64 time=0.306 ms 92 bytes from xenon.example.com (192.168.1.60): Redirect Host(New addr: 192.168.1.70) Vr HL TOS Len ID Flg off TTL Pro cks Src Dst 4 5 00 0054 8fc5 0 0000 3f 01 67d2 192.168.1.123 192.168.1.70 64 bytes from 192.168.1.70: icmp_seq=3 ttl=64 time=0.278 ms 92 bytes from xenon.example.com (192.168.1.60): Redirect Host(New addr: 192.168.1.70) Vr HL TOS Len ID Flg off TTL Pro cks Src Dst 4 5 00 0054 08f0 0 0000 3f 01 eea7 192.168.1.123 192.168.1.70 64 bytes from 192.168.1.70: icmp_seq=4 ttl=64 time=0.285 ms 92 bytes from xenon.example.com (192.168.1.60): Redirect Host(New addr: 192.168.1.70) Vr HL TOS Len ID Flg off TTL Pro cks Src Dst 4 5 00 0054 438e 0 0000 3f 01 b409 192.168.1.123 192.168.1.70 64 bytes from 192.168.1.70: icmp_seq=5 ttl=64 time=0.327 ms 64 bytes from 192.168.1.70: icmp_seq=5 ttl=64 time=0.329 ms (DUP!) 64 bytes from 192.168.1.70: icmp_seq=6 ttl=64 time=0.292 ms 64 bytes from 192.168.1.70: icmp_seq=7 ttl=64 time=0.266 ms 92 bytes from xenon.example.com (192.168.1.60): Redirect Host(New addr: 192.168.1.70) Vr HL TOS Len ID Flg off TTL Pro cks Src Dst 4 5 00 0054 2be0 0 0000 3f 01 cbb7 192.168.1.123 192.168.1.70 Request timeout for icmp_seq 8 ^C --- aurora.example.com ping statistics --- 10 packets transmitted, 8 packets received, +1 duplicates, 20.0% packet loss round-trip min/avg/max/stddev = 0.266/0.314/0.466/0.057 ms this ping was done from another computer on the network. aurora is the kvm guest, and xenon is the kvm host. i'm not sure what it may or may not be indicative, but in the past, i don't recall seeing the redirection messages. -ben -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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/linux/+bug/1153364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
