* [PATCHv3 0/4] qemu-kvm: vhost net support
@ 2009-08-17 12:37 Michael S. Tsirkin
2009-08-17 12:48 ` Avi Kivity
` (3 more replies)
0 siblings, 4 replies; 22+ messages in thread
From: Michael S. Tsirkin @ 2009-08-17 12:37 UTC (permalink / raw)
To: avi, kvm, virtualization; +Cc: gregory.haskins
This adds support for vhost-net virtio kernel backend.
This is RFC, but works without issues for me.
Still needs to be split up, tested and benchmarked properly,
but posting it here in case people want to test drive
the kernel bits I posted.
Changes since v2:
- minor fixes
- added patch to build on RHEL5.3
Changes since v1:
- rebased on top of 9dc275d9d660fe1cd64d36102d600885f9fdb88a
Michael S. Tsirkin (4):
qemu-kvm: move virtio-pci.o to near pci.o
virtio: move features to an inline function
qemu-kvm: vhost-net implementation
qemu-kvm: add compat eventfd
Makefile.hw | 2 +-
Makefile.target | 3 +-
compat/sys/eventfd.h | 13 ++++
configure | 1 +
hw/vhost_net.c | 181 ++++++++++++++++++++++++++++++++++++++++++++++++++
hw/vhost_net.h | 30 ++++++++
hw/virtio-balloon.c | 2 +-
hw/virtio-blk.c | 2 +-
hw/virtio-console.c | 2 +-
hw/virtio-net.c | 34 +++++++++-
hw/virtio-pci.c | 43 +++++++++++-
hw/virtio.c | 19 -----
hw/virtio.h | 38 ++++++++++-
net.c | 6 ++-
net.h | 1 +
qemu-kvm.c | 8 --
qemu-kvm.h | 9 +++
17 files changed, 353 insertions(+), 41 deletions(-)
create mode 100644 compat/sys/eventfd.h
create mode 100644 hw/vhost_net.c
create mode 100644 hw/vhost_net.h
^ permalink raw reply [flat|nested] 22+ messages in thread* Re: [PATCHv3 0/4] qemu-kvm: vhost net support 2009-08-17 12:37 [PATCHv3 0/4] qemu-kvm: vhost net support Michael S. Tsirkin @ 2009-08-17 12:48 ` Avi Kivity 2009-08-17 12:48 ` Avi Kivity ` (2 subsequent siblings) 3 siblings, 0 replies; 22+ messages in thread From: Avi Kivity @ 2009-08-17 12:48 UTC (permalink / raw) To: Michael S. Tsirkin; +Cc: kvm, virtualization, gregory.haskins On 08/17/2009 03:37 PM, Michael S. Tsirkin wrote: > but posting it here in case people want to test drive > the kernel bits I posted. > I think that is best served if you post a link to a git tree... -- error compiling committee.c: too many arguments to function ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [PATCHv3 0/4] qemu-kvm: vhost net support 2009-08-17 12:37 [PATCHv3 0/4] qemu-kvm: vhost net support Michael S. Tsirkin 2009-08-17 12:48 ` Avi Kivity @ 2009-08-17 12:48 ` Avi Kivity 2009-08-18 20:54 ` Alex Williamson 2009-08-18 20:54 ` Alex Williamson 3 siblings, 0 replies; 22+ messages in thread From: Avi Kivity @ 2009-08-17 12:48 UTC (permalink / raw) To: Michael S. Tsirkin; +Cc: kvm, virtualization On 08/17/2009 03:37 PM, Michael S. Tsirkin wrote: > but posting it here in case people want to test drive > the kernel bits I posted. > I think that is best served if you post a link to a git tree... -- error compiling committee.c: too many arguments to function ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [PATCHv3 0/4] qemu-kvm: vhost net support 2009-08-17 12:37 [PATCHv3 0/4] qemu-kvm: vhost net support Michael S. Tsirkin 2009-08-17 12:48 ` Avi Kivity 2009-08-17 12:48 ` Avi Kivity @ 2009-08-18 20:54 ` Alex Williamson 2009-08-18 21:04 ` Michael S. Tsirkin 2009-08-18 21:04 ` Michael S. Tsirkin 2009-08-18 20:54 ` Alex Williamson 3 siblings, 2 replies; 22+ messages in thread From: Alex Williamson @ 2009-08-18 20:54 UTC (permalink / raw) To: Michael S. Tsirkin; +Cc: avi, kvm, virtualization, gregory.haskins On Mon, Aug 17, 2009 at 6:37 AM, Michael S. Tsirkin<mst@redhat.com> wrote: > This adds support for vhost-net virtio kernel backend. > > This is RFC, but works without issues for me. I got this to build by syncing up some headers in kvm/include/linux, but it doesn't seem to be working quite right. I have an unused e1000e nic in my system (eth10,00:17:a4:77:a4:08) that I ifconfig up, then launch a VM with the option: -net nic,model=virtio,macaddr=00:17:a4:77:a4:08,vhost=eth10 The virtio nic is functional in the guest, but it gets packet dupes on ping, which is likely contributing to the poor performance, roughly 1/3rd of virtio-net userspace for tcp_stream and tcp_rr. I think I have all the offload option disabled on the nic in the host. Any idea what I might be doing wrong? This seems quite a bit off of the udp_rr results you posted. Thanks, Alex ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [PATCHv3 0/4] qemu-kvm: vhost net support 2009-08-18 20:54 ` Alex Williamson @ 2009-08-18 21:04 ` Michael S. Tsirkin 2009-08-18 21:11 ` Alex Williamson 2009-08-18 21:11 ` Alex Williamson 2009-08-18 21:04 ` Michael S. Tsirkin 1 sibling, 2 replies; 22+ messages in thread From: Michael S. Tsirkin @ 2009-08-18 21:04 UTC (permalink / raw) To: Alex Williamson; +Cc: avi, kvm, virtualization, gregory.haskins On Tue, Aug 18, 2009 at 02:54:23PM -0600, Alex Williamson wrote: > On Mon, Aug 17, 2009 at 6:37 AM, Michael S. Tsirkin<mst@redhat.com> wrote: > > This adds support for vhost-net virtio kernel backend. > > > > This is RFC, but works without issues for me. > > I got this to build by syncing up some headers in kvm/include/linux, > but it doesn't seem to be working quite right. I have an unused > e1000e nic in my system (eth10,00:17:a4:77:a4:08) that I ifconfig up, > then launch a VM with the option: > > -net nic,model=virtio,macaddr=00:17:a4:77:a4:08,vhost=eth10 > > The virtio nic is functional in the guest, but it gets packet dupes on > ping, which is likely contributing to the poor performance, roughly > 1/3rd of virtio-net userspace for tcp_stream and tcp_rr. I think I > have all the offload option disabled on the nic in the host. Any idea > what I might be doing wrong? This seems quite a bit off of the udp_rr > results you posted. Thanks, > > Alex Did you assign ip address in host by any chance? You don't want that. -- MST ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [PATCHv3 0/4] qemu-kvm: vhost net support 2009-08-18 21:04 ` Michael S. Tsirkin @ 2009-08-18 21:11 ` Alex Williamson 2009-08-18 21:11 ` Alex Williamson 1 sibling, 0 replies; 22+ messages in thread From: Alex Williamson @ 2009-08-18 21:11 UTC (permalink / raw) To: Michael S. Tsirkin; +Cc: avi, kvm, virtualization On Tue, Aug 18, 2009 at 3:04 PM, Michael S. Tsirkin<mst@redhat.com> wrote: > Did you assign ip address in host by any chance? You don't want that. Nope, just up on the host, no IP: eth10 Link encap:Ethernet HWaddr 00:17:a4:77:a4:08 inet6 addr: fe80::217:a4ff:fe77:a408/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:22446487 errors:0 dropped:0 overruns:0 frame:0 TX packets:4529008 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1492187453 (1.3 GiB) TX bytes:2972806236 (2.7 GiB) Memory:fbae0000-fbb00000 ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [PATCHv3 0/4] qemu-kvm: vhost net support 2009-08-18 21:04 ` Michael S. Tsirkin 2009-08-18 21:11 ` Alex Williamson @ 2009-08-18 21:11 ` Alex Williamson 2009-08-18 21:23 ` Alex Williamson ` (3 more replies) 1 sibling, 4 replies; 22+ messages in thread From: Alex Williamson @ 2009-08-18 21:11 UTC (permalink / raw) To: Michael S. Tsirkin; +Cc: avi, kvm, virtualization, gregory.haskins On Tue, Aug 18, 2009 at 3:04 PM, Michael S. Tsirkin<mst@redhat.com> wrote: > Did you assign ip address in host by any chance? You don't want that. Nope, just up on the host, no IP: eth10 Link encap:Ethernet HWaddr 00:17:a4:77:a4:08 inet6 addr: fe80::217:a4ff:fe77:a408/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:22446487 errors:0 dropped:0 overruns:0 frame:0 TX packets:4529008 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1492187453 (1.3 GiB) TX bytes:2972806236 (2.7 GiB) Memory:fbae0000-fbb00000 ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [PATCHv3 0/4] qemu-kvm: vhost net support 2009-08-18 21:11 ` Alex Williamson @ 2009-08-18 21:23 ` Alex Williamson 2009-08-18 21:23 ` Alex Williamson ` (2 subsequent siblings) 3 siblings, 0 replies; 22+ messages in thread From: Alex Williamson @ 2009-08-18 21:23 UTC (permalink / raw) To: Michael S. Tsirkin; +Cc: avi, kvm, virtualization On Tue, Aug 18, 2009 at 3:11 PM, Alex Williamson<alex.williamson@hp.com> wrote: > On Tue, Aug 18, 2009 at 3:04 PM, Michael S. Tsirkin<mst@redhat.com> wrote: >> Did you assign ip address in host by any chance? You don't want that. > > Nope, just up on the host, no IP: > > eth10 Link encap:Ethernet HWaddr 00:17:a4:77:a4:08 > inet6 addr: fe80::217:a4ff:fe77:a408/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:22446487 errors:0 dropped:0 overruns:0 frame:0 > TX packets:4529008 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:1492187453 (1.3 GiB) TX bytes:2972806236 (2.7 GiB) > Memory:fbae0000-fbb00000 > Hmm, I lose the dupe and get pretty respectable tcp_rr rates if I use the host as my target IP, is the issue maybe isolated to off-box communication? tcp_stream is still worse than userspace though. Alex _______________________________________________ Virtualization mailing list Virtualization@lists.linux-foundation.org https://lists.linux-foundation.org/mailman/listinfo/virtualization ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [PATCHv3 0/4] qemu-kvm: vhost net support 2009-08-18 21:11 ` Alex Williamson 2009-08-18 21:23 ` Alex Williamson @ 2009-08-18 21:23 ` Alex Williamson 2009-08-20 7:03 ` Michael S. Tsirkin 2009-08-20 7:03 ` Michael S. Tsirkin 2009-08-23 19:22 ` Michael S. Tsirkin 2009-08-23 19:22 ` Michael S. Tsirkin 3 siblings, 2 replies; 22+ messages in thread From: Alex Williamson @ 2009-08-18 21:23 UTC (permalink / raw) To: Michael S. Tsirkin; +Cc: avi, kvm, virtualization, gregory.haskins On Tue, Aug 18, 2009 at 3:11 PM, Alex Williamson<alex.williamson@hp.com> wrote: > On Tue, Aug 18, 2009 at 3:04 PM, Michael S. Tsirkin<mst@redhat.com> wrote: >> Did you assign ip address in host by any chance? You don't want that. > > Nope, just up on the host, no IP: > > eth10 Link encap:Ethernet HWaddr 00:17:a4:77:a4:08 > inet6 addr: fe80::217:a4ff:fe77:a408/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:22446487 errors:0 dropped:0 overruns:0 frame:0 > TX packets:4529008 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:1492187453 (1.3 GiB) TX bytes:2972806236 (2.7 GiB) > Memory:fbae0000-fbb00000 > Hmm, I lose the dupe and get pretty respectable tcp_rr rates if I use the host as my target IP, is the issue maybe isolated to off-box communication? tcp_stream is still worse than userspace though. Alex ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [PATCHv3 0/4] qemu-kvm: vhost net support 2009-08-18 21:23 ` Alex Williamson @ 2009-08-20 7:03 ` Michael S. Tsirkin 2009-08-20 22:05 ` Alex Williamson 2009-08-20 22:05 ` Alex Williamson 2009-08-20 7:03 ` Michael S. Tsirkin 1 sibling, 2 replies; 22+ messages in thread From: Michael S. Tsirkin @ 2009-08-20 7:03 UTC (permalink / raw) To: Alex Williamson; +Cc: avi, kvm, virtualization, gregory.haskins On Tue, Aug 18, 2009 at 03:23:02PM -0600, Alex Williamson wrote: > On Tue, Aug 18, 2009 at 3:11 PM, Alex Williamson<alex.williamson@hp.com> wrote: > > On Tue, Aug 18, 2009 at 3:04 PM, Michael S. Tsirkin<mst@redhat.com> wrote: > >> Did you assign ip address in host by any chance? You don't want that. > > > > Nope, just up on the host, no IP: > > > > eth10 Link encap:Ethernet HWaddr 00:17:a4:77:a4:08 > > inet6 addr: fe80::217:a4ff:fe77:a408/64 Scope:Link > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:22446487 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:4529008 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:1492187453 (1.3 GiB) TX bytes:2972806236 (2.7 GiB) > > Memory:fbae0000-fbb00000 > > > > Hmm, I lose the dupe and get pretty respectable tcp_rr rates if I use > the host as my target IP, is the issue maybe isolated to off-box > communication? I think the duplicates are our best hint that something's wrong at this point. Let's try to see where do they come from. What is it exactly that you see? This ping is external box to guest, correct? Is it the external box that gets duplicates or the guest? What happens when you ping the other way? What does tcpdump show on both sides when you ping? A couple of extra datapoints to check: - What if you assign a different IP to the host (in the same subnet) and try external guest to host? - Is the card in promisc mode? What if you disable promisc mode? Also, it seems that you have an external bridge that sends your outgoing packets back to you. Is that right? Thanks! > tcp_stream is still worse than userspace though. > > Alex ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [PATCHv3 0/4] qemu-kvm: vhost net support 2009-08-20 7:03 ` Michael S. Tsirkin @ 2009-08-20 22:05 ` Alex Williamson 2009-08-20 22:05 ` Alex Williamson 1 sibling, 0 replies; 22+ messages in thread From: Alex Williamson @ 2009-08-20 22:05 UTC (permalink / raw) To: Michael S. Tsirkin; +Cc: avi, kvm, virtualization On Thu, Aug 20, 2009 at 1:03 AM, Michael S. Tsirkin<mst@redhat.com> wrote: > > I think the duplicates are our best hint that something's wrong at this > point. Let's try to see where do they come from. > > What is it exactly that you see? # ping 10.100.100.74 PING 10.100.100.74 (10.100.100.74) 56(84) bytes of data. 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=0.263 ms 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=0.358 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=0.394 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=0.478 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=0.626 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=0.727 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=0.834 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=0.909 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=0.997 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.08 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.12 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.18 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.29 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.38 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.46 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.55 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.56 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.65 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.68 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.70 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.83 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.89 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.95 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.98 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.08 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.22 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.27 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.31 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.44 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.50 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.51 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.57 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.63 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.76 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.81 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.84 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.90 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.94 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.02 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.06 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.09 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.15 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.17 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.24 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.28 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.35 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.37 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.44 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.47 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.54 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.57 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.64 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.67 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.75 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.77 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.84 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.87 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.94 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.98 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=4.04 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=4.07 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=4.15 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=4.17 ms (DUP!) From 10.91.73.253 icmp_seq=1 Time to live exceeded 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=4.26 ms (DUP!) ^C --- 10.100.100.74 ping statistics --- 1 packets transmitted, 1 received, +63 duplicates, +1 errors, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.263/2.481/4.266/1.147 ms > This ping is external box to guest, > correct? Either direction, external box->guest or guest->external box > Is it the external box that gets duplicates or the guest? > What happens when you ping the other way? > What does tcpdump show on both sides when you ping? ping -c 1 guest (10.100.100.74) -> external (10.91.73.252) (these are on the same subnet) guest: 15:29:51.342545 IP 10.100.100.74 > 10.91.73.252: ICMP echo request, id 64778, seq 1, length 64 15:29:51.342716 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.342734 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.342799 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.342835 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.342909 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.342955 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.343004 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.343043 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.343105 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.343151 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.343277 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.343293 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.343355 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.343403 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.343524 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.343550 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.343604 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.343654 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.343770 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.343795 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.343857 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.343898 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.343968 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.343980 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.344052 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.344103 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.344225 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.344250 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.344302 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.344351 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.344470 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.344495 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.344550 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.344599 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.344689 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.344709 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.344749 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.344798 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.344890 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.344910 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.344949 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.344997 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.345061 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.345100 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.345153 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.345207 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.345295 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.345315 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.345352 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.345402 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.345491 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.345510 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.345552 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.345601 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.345692 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.345712 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.345790 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.345806 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.345867 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.345886 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.345947 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.345996 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.346083 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.346103 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 external: 15:24:25.892748 IP 10.100.100.74 > 10.91.73.252: ICMP echo request, id 64778, seq 1, length 64 15:24:25.892770 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:24:25.896254 IP 10.91.73.253 > 10.91.73.252: ICMP time exceeded in-transit, length 92 (note 253 is the IP address of eth0 on the KVM host... odd) ping -c 1 external (10.91.73.252) -> guest (10.100.100.74) external: 15:28:38.278291 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:28:38.278590 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.278760 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.278881 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.279024 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.279064 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.279157 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.279180 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.279299 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.279319 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.279361 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.279457 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.279478 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.279567 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.279612 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.279693 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.279738 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.279786 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.279877 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.279991 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.280000 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.280085 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.280105 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.280173 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.280202 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.280228 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.280271 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.280312 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.280401 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.280447 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.280534 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.280548 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.280581 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.280634 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.280766 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.280773 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.280805 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.280855 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.280902 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.280934 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.281014 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.281064 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.281113 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.281159 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.281215 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.281253 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.281300 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.281344 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.281408 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.281447 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.281503 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.281542 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.281644 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.281670 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.281723 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.281763 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.281816 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.281847 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.281918 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.281937 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.282059 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.282086 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.282153 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.282159 IP 10.91.73.253 > 10.91.73.252: ICMP time exceeded in-transit, length 92 15:28:38.282175 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.282204 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 guest: 15:34:03.722851 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.722880 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.723023 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.723050 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.723155 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.723165 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.723305 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.723316 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.723340 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.723349 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.723442 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.723452 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.723469 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.723478 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.723578 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.723588 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.723613 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.723623 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.723639 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.723658 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.723744 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.723753 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.723768 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.723776 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.723855 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.723864 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.723907 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.723916 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.723971 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.723981 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.724004 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.724013 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.724067 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.724078 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.724161 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.724171 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.724249 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.724258 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.724275 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.724284 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.724362 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.724371 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.724393 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.724402 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.724457 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.724467 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.724491 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.724500 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.724529 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.724538 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.724561 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.724570 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.724599 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.724608 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.724663 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.724683 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.724726 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.724737 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.724783 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.724806 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.724838 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.724848 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.724882 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.724891 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.724917 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.724925 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.725015 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.725027 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.725063 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.725080 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.725084 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.725102 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.725136 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.725156 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.725186 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.725199 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.725222 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.725230 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.725296 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.725308 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.725352 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.725360 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.725408 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.725416 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.725442 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.725450 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.725497 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.725505 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.725537 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.725545 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.725577 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.725596 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.725629 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.725637 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.725691 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.725701 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.725737 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.725744 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.725777 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.725797 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.725829 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.725837 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.725913 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.725924 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.725961 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.725969 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.726009 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.726016 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.726050 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.726058 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.726100 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.726107 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.726136 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.726143 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.726176 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.726195 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.726228 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.726235 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.726333 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.726343 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.726378 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.726385 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.726424 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.726431 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.726465 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.726473 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.726505 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.726512 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 > A couple of extra datapoints to check: > - What if you assign a different IP to the host (in the same subnet) and > try external guest to host? I'm not sure what you mean by external guest. If I change the IP of the host, nothing changes except the time exceeed messages seen by the external system have the new IP. > - Is the card in promisc mode? What if you disable promisc mode? No, I'm using the physical MAC in the guest to avoid promisc. > Also, it seems that you have an external bridge that sends your outgoing > packets back to you. Is that right? Not that I'm aware of. My config is simply: eth0 - host nic eth10 - vhost nic I can ifdown eth0 and switch the host to eth10 and don't get duplicate packets on host<->external pings. Thanks, Alex _______________________________________________ Virtualization mailing list Virtualization@lists.linux-foundation.org https://lists.linux-foundation.org/mailman/listinfo/virtualization ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [PATCHv3 0/4] qemu-kvm: vhost net support 2009-08-20 7:03 ` Michael S. Tsirkin 2009-08-20 22:05 ` Alex Williamson @ 2009-08-20 22:05 ` Alex Williamson 2009-08-23 19:45 ` Michael S. Tsirkin 2009-08-23 19:45 ` Michael S. Tsirkin 1 sibling, 2 replies; 22+ messages in thread From: Alex Williamson @ 2009-08-20 22:05 UTC (permalink / raw) To: Michael S. Tsirkin; +Cc: avi, kvm, virtualization, gregory.haskins On Thu, Aug 20, 2009 at 1:03 AM, Michael S. Tsirkin<mst@redhat.com> wrote: > > I think the duplicates are our best hint that something's wrong at this > point. Let's try to see where do they come from. > > What is it exactly that you see? # ping 10.100.100.74 PING 10.100.100.74 (10.100.100.74) 56(84) bytes of data. 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=0.263 ms 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=0.358 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=0.394 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=0.478 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=0.626 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=0.727 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=0.834 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=0.909 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=0.997 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.08 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.12 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.18 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.29 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.38 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.46 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.55 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.56 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.65 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.68 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.70 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.83 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.89 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.95 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.98 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.08 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.22 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.27 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.31 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.44 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.50 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.51 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.57 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.63 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.76 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.81 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.84 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.90 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.94 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.02 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.06 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.09 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.15 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.17 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.24 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.28 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.35 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.37 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.44 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.47 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.54 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.57 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.64 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.67 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.75 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.77 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.84 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.87 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.94 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.98 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=4.04 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=4.07 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=4.15 ms (DUP!) 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=4.17 ms (DUP!) From 10.91.73.253 icmp_seq=1 Time to live exceeded 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=4.26 ms (DUP!) ^C --- 10.100.100.74 ping statistics --- 1 packets transmitted, 1 received, +63 duplicates, +1 errors, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.263/2.481/4.266/1.147 ms > This ping is external box to guest, > correct? Either direction, external box->guest or guest->external box > Is it the external box that gets duplicates or the guest? > What happens when you ping the other way? > What does tcpdump show on both sides when you ping? ping -c 1 guest (10.100.100.74) -> external (10.91.73.252) (these are on the same subnet) guest: 15:29:51.342545 IP 10.100.100.74 > 10.91.73.252: ICMP echo request, id 64778, seq 1, length 64 15:29:51.342716 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.342734 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.342799 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.342835 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.342909 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.342955 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.343004 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.343043 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.343105 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.343151 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.343277 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.343293 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.343355 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.343403 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.343524 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.343550 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.343604 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.343654 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.343770 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.343795 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.343857 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.343898 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.343968 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.343980 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.344052 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.344103 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.344225 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.344250 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.344302 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.344351 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.344470 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.344495 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.344550 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.344599 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.344689 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.344709 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.344749 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.344798 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.344890 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.344910 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.344949 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.344997 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.345061 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.345100 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.345153 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.345207 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.345295 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.345315 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.345352 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.345402 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.345491 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.345510 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.345552 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.345601 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.345692 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.345712 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.345790 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.345806 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.345867 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.345886 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.345947 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.345996 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.346083 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:29:51.346103 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 external: 15:24:25.892748 IP 10.100.100.74 > 10.91.73.252: ICMP echo request, id 64778, seq 1, length 64 15:24:25.892770 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id 64778, seq 1, length 64 15:24:25.896254 IP 10.91.73.253 > 10.91.73.252: ICMP time exceeded in-transit, length 92 (note 253 is the IP address of eth0 on the KVM host... odd) ping -c 1 external (10.91.73.252) -> guest (10.100.100.74) external: 15:28:38.278291 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:28:38.278590 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.278760 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.278881 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.279024 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.279064 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.279157 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.279180 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.279299 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.279319 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.279361 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.279457 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.279478 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.279567 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.279612 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.279693 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.279738 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.279786 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.279877 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.279991 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.280000 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.280085 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.280105 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.280173 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.280202 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.280228 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.280271 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.280312 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.280401 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.280447 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.280534 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.280548 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.280581 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.280634 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.280766 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.280773 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.280805 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.280855 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.280902 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.280934 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.281014 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.281064 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.281113 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.281159 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.281215 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.281253 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.281300 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.281344 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.281408 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.281447 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.281503 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.281542 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.281644 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.281670 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.281723 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.281763 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.281816 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.281847 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.281918 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.281937 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.282059 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.282086 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.282153 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.282159 IP 10.91.73.253 > 10.91.73.252: ICMP time exceeded in-transit, length 92 15:28:38.282175 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:28:38.282204 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 guest: 15:34:03.722851 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.722880 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.723023 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.723050 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.723155 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.723165 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.723305 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.723316 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.723340 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.723349 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.723442 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.723452 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.723469 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.723478 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.723578 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.723588 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.723613 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.723623 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.723639 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.723658 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.723744 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.723753 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.723768 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.723776 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.723855 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.723864 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.723907 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.723916 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.723971 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.723981 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.724004 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.724013 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.724067 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.724078 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.724161 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.724171 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.724249 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.724258 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.724275 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.724284 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.724362 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.724371 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.724393 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.724402 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.724457 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.724467 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.724491 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.724500 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.724529 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.724538 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.724561 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.724570 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.724599 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.724608 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.724663 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.724683 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.724726 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.724737 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.724783 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.724806 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.724838 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.724848 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.724882 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.724891 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.724917 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.724925 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.725015 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.725027 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.725063 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.725080 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.725084 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.725102 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.725136 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.725156 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.725186 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.725199 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.725222 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.725230 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.725296 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.725308 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.725352 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.725360 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.725408 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.725416 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.725442 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.725450 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.725497 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.725505 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.725537 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.725545 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.725577 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.725596 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.725629 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.725637 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.725691 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.725701 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.725737 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.725744 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.725777 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.725797 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.725829 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.725837 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.725913 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.725924 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.725961 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.725969 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.726009 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.726016 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.726050 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.726058 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.726100 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.726107 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.726136 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.726143 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.726176 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.726195 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.726228 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.726235 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.726333 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.726343 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.726378 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.726385 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.726424 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.726431 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.726465 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.726473 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 15:34:03.726505 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id 30800, seq 1, length 64 15:34:03.726512 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id 30800, seq 1, length 64 > A couple of extra datapoints to check: > - What if you assign a different IP to the host (in the same subnet) and > try external guest to host? I'm not sure what you mean by external guest. If I change the IP of the host, nothing changes except the time exceeed messages seen by the external system have the new IP. > - Is the card in promisc mode? What if you disable promisc mode? No, I'm using the physical MAC in the guest to avoid promisc. > Also, it seems that you have an external bridge that sends your outgoing > packets back to you. Is that right? Not that I'm aware of. My config is simply: eth0 - host nic eth10 - vhost nic I can ifdown eth0 and switch the host to eth10 and don't get duplicate packets on host<->external pings. Thanks, Alex ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [PATCHv3 0/4] qemu-kvm: vhost net support 2009-08-20 22:05 ` Alex Williamson @ 2009-08-23 19:45 ` Michael S. Tsirkin 2009-08-23 19:45 ` Michael S. Tsirkin 1 sibling, 0 replies; 22+ messages in thread From: Michael S. Tsirkin @ 2009-08-23 19:45 UTC (permalink / raw) To: Alex Williamson; +Cc: avi, kvm, virtualization OK, there is a small issue with networking setup here, but otherwise it looks like we'll have to debug it in vhost ... Forgot to ask - dmesg does not show anything interesting, does it? On Thu, Aug 20, 2009 at 04:05:04PM -0600, Alex Williamson wrote: > On Thu, Aug 20, 2009 at 1:03 AM, Michael S. Tsirkin<mst@redhat.com> wrote: > > > > I think the duplicates are our best hint that something's wrong at this > > point. Let's try to see where do they come from. > > > > What is it exactly that you see? > > # ping 10.100.100.74 > PING 10.100.100.74 (10.100.100.74) 56(84) bytes of data. > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=0.263 ms > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=0.358 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=0.394 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=0.478 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=0.626 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=0.727 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=0.834 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=0.909 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=0.997 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.08 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.12 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.18 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.29 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.38 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.46 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.55 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.56 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.65 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.68 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.70 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.83 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.89 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.95 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.98 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.08 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.22 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.27 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.31 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.44 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.50 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.51 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.57 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.63 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.76 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.81 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.84 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.90 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.94 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.02 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.06 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.09 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.15 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.17 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.24 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.28 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.35 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.37 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.44 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.47 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.54 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.57 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.64 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.67 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.75 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.77 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.84 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.87 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.94 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.98 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=4.04 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=4.07 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=4.15 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=4.17 ms (DUP!) > >From 10.91.73.253 icmp_seq=1 Time to live exceeded > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=4.26 ms (DUP!) > ^C > --- 10.100.100.74 ping statistics --- > 1 packets transmitted, 1 received, +63 duplicates, +1 errors, 0% > packet loss, time 0ms > rtt min/avg/max/mdev = 0.263/2.481/4.266/1.147 ms > > > This ping is external box to guest, > > correct? > > Either direction, external box->guest or guest->external box Yes, one way you get duplicate replies, the other way duplicate requests. > > Is it the external box that gets duplicates or the guest? > > What happens when you ping the other way? > > What does tcpdump show on both sides when you ping? > > ping -c 1 guest (10.100.100.74) -> external (10.91.73.252) (these are > on the same subnet) > > guest: > 15:29:51.342545 IP 10.100.100.74 > 10.91.73.252: ICMP echo request, id > 64778, seq 1, length 64 > 15:29:51.342716 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.342734 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.342799 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.342835 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.342909 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.342955 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.343004 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.343043 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.343105 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.343151 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.343277 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.343293 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.343355 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.343403 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.343524 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.343550 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.343604 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.343654 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.343770 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.343795 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.343857 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.343898 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.343968 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.343980 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.344052 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.344103 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.344225 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.344250 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.344302 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.344351 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.344470 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.344495 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.344550 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.344599 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.344689 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.344709 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.344749 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.344798 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.344890 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.344910 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.344949 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.344997 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.345061 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.345100 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.345153 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.345207 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.345295 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.345315 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.345352 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.345402 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.345491 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.345510 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.345552 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.345601 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.345692 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.345712 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.345790 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.345806 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.345867 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.345886 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.345947 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.345996 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.346083 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.346103 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 OK, but now, could you please run tcpdump -i eth10 on host so that we can check whether these duplicates arrived from outside? > external: > 15:24:25.892748 IP 10.100.100.74 > 10.91.73.252: ICMP echo request, id > 64778, seq 1, length 64 > 15:24:25.892770 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:24:25.896254 IP 10.91.73.253 > 10.91.73.252: ICMP time exceeded > in-transit, length 92 > (note 253 is the IP address of eth0 on the KVM host... odd) This might mean you enabled ipv4 forwarding on KVM host, so it tried to forward the packet on and could not. Try disabling it? > ping -c 1 external (10.91.73.252) -> guest (10.100.100.74) > > external: > 15:28:38.278291 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:28:38.278590 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.278760 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.278881 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.279024 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.279064 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.279157 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.279180 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.279299 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.279319 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.279361 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.279457 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.279478 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.279567 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.279612 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.279693 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.279738 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.279786 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.279877 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.279991 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.280000 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.280085 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.280105 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.280173 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.280202 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.280228 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.280271 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.280312 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.280401 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.280447 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.280534 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.280548 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.280581 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.280634 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.280766 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.280773 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.280805 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.280855 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.280902 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.280934 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.281014 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.281064 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.281113 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.281159 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.281215 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.281253 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.281300 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.281344 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.281408 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.281447 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.281503 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.281542 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.281644 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.281670 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.281723 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.281763 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.281816 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.281847 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.281918 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.281937 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.282059 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.282086 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.282153 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.282159 IP 10.91.73.253 > 10.91.73.252: ICMP time exceeded > in-transit, length 92 > 15:28:38.282175 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.282204 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > > guest: > 15:34:03.722851 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.722880 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.723023 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.723050 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 So, it is again the guest that gets duplicates. If it's a bug in vhost, it's a problem on RX path. > 15:34:03.723155 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.723165 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.723305 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.723316 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.723340 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.723349 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.723442 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.723452 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.723469 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.723478 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.723578 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.723588 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.723613 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.723623 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.723639 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.723658 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.723744 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.723753 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.723768 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.723776 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.723855 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.723864 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.723907 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.723916 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.723971 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.723981 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.724004 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.724013 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.724067 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.724078 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.724161 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.724171 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.724249 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.724258 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.724275 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.724284 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.724362 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.724371 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.724393 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.724402 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.724457 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.724467 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.724491 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.724500 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.724529 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.724538 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.724561 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.724570 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.724599 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.724608 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.724663 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.724683 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.724726 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.724737 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.724783 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.724806 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.724838 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.724848 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.724882 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.724891 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.724917 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.724925 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.725015 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.725027 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.725063 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.725080 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.725084 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.725102 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.725136 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.725156 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.725186 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.725199 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.725222 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.725230 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.725296 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.725308 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.725352 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.725360 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.725408 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.725416 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.725442 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.725450 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.725497 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.725505 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.725537 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.725545 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.725577 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.725596 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.725629 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.725637 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.725691 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.725701 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.725737 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.725744 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.725777 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.725797 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.725829 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.725837 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.725913 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.725924 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.725961 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.725969 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.726009 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.726016 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.726050 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.726058 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.726100 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.726107 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.726136 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.726143 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.726176 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.726195 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.726228 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.726235 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.726333 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.726343 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.726378 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.726385 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.726424 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.726431 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.726465 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.726473 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.726505 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.726512 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 So, to eliminate networking setup issues, could you please use Or's patch to map raw networking device to virtio in userspace? (Don't forget to add promisc=n otherwise it'll set your card in promisc mode). > > A couple of extra datapoints to check: > > - What if you assign a different IP to the host (in the same subnet) and > > try external guest to host? > > I'm not sure what you mean by external guest. If I change the IP of > the host, nothing changes except the time exceeed messages seen by the > external system have the new IP. Sorry, I just meant ping from external to KVM host. But based on this data I do not expect any dups. > > - Is the card in promisc mode? What if you disable promisc mode? > > No, I'm using the physical MAC in the guest to avoid promisc. > > > Also, it seems that you have an external bridge that sends your outgoing > > packets back to you. Is that right? > > Not that I'm aware of. My config is simply: > > eth0 - host nic > eth10 - vhost nic > > I can ifdown eth0 and switch the host to eth10 and don't get duplicate > packets on host<->external pings. Thanks, > > Alex ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [PATCHv3 0/4] qemu-kvm: vhost net support 2009-08-20 22:05 ` Alex Williamson 2009-08-23 19:45 ` Michael S. Tsirkin @ 2009-08-23 19:45 ` Michael S. Tsirkin 1 sibling, 0 replies; 22+ messages in thread From: Michael S. Tsirkin @ 2009-08-23 19:45 UTC (permalink / raw) To: Alex Williamson; +Cc: avi, kvm, virtualization, gregory.haskins OK, there is a small issue with networking setup here, but otherwise it looks like we'll have to debug it in vhost ... Forgot to ask - dmesg does not show anything interesting, does it? On Thu, Aug 20, 2009 at 04:05:04PM -0600, Alex Williamson wrote: > On Thu, Aug 20, 2009 at 1:03 AM, Michael S. Tsirkin<mst@redhat.com> wrote: > > > > I think the duplicates are our best hint that something's wrong at this > > point. Let's try to see where do they come from. > > > > What is it exactly that you see? > > # ping 10.100.100.74 > PING 10.100.100.74 (10.100.100.74) 56(84) bytes of data. > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=0.263 ms > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=0.358 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=0.394 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=0.478 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=0.626 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=0.727 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=0.834 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=0.909 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=0.997 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.08 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.12 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.18 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.29 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.38 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.46 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.55 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.56 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.65 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.68 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.70 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.83 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.89 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.95 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=1.98 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.08 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.22 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.27 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.31 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.44 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.50 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.51 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.57 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.63 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.76 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.81 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.84 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.90 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=2.94 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.02 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.06 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.09 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.15 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.17 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.24 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.28 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.35 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.37 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.44 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.47 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.54 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.57 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.64 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.67 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.75 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.77 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.84 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.87 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.94 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=3.98 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=4.04 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=4.07 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=4.15 ms (DUP!) > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=4.17 ms (DUP!) > >From 10.91.73.253 icmp_seq=1 Time to live exceeded > 64 bytes from 10.100.100.74: icmp_seq=1 ttl=64 time=4.26 ms (DUP!) > ^C > --- 10.100.100.74 ping statistics --- > 1 packets transmitted, 1 received, +63 duplicates, +1 errors, 0% > packet loss, time 0ms > rtt min/avg/max/mdev = 0.263/2.481/4.266/1.147 ms > > > This ping is external box to guest, > > correct? > > Either direction, external box->guest or guest->external box Yes, one way you get duplicate replies, the other way duplicate requests. > > Is it the external box that gets duplicates or the guest? > > What happens when you ping the other way? > > What does tcpdump show on both sides when you ping? > > ping -c 1 guest (10.100.100.74) -> external (10.91.73.252) (these are > on the same subnet) > > guest: > 15:29:51.342545 IP 10.100.100.74 > 10.91.73.252: ICMP echo request, id > 64778, seq 1, length 64 > 15:29:51.342716 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.342734 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.342799 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.342835 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.342909 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.342955 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.343004 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.343043 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.343105 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.343151 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.343277 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.343293 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.343355 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.343403 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.343524 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.343550 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.343604 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.343654 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.343770 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.343795 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.343857 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.343898 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.343968 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.343980 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.344052 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.344103 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.344225 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.344250 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.344302 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.344351 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.344470 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.344495 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.344550 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.344599 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.344689 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.344709 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.344749 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.344798 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.344890 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.344910 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.344949 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.344997 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.345061 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.345100 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.345153 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.345207 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.345295 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.345315 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.345352 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.345402 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.345491 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.345510 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.345552 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.345601 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.345692 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.345712 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.345790 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.345806 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.345867 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.345886 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.345947 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.345996 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.346083 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:29:51.346103 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 OK, but now, could you please run tcpdump -i eth10 on host so that we can check whether these duplicates arrived from outside? > external: > 15:24:25.892748 IP 10.100.100.74 > 10.91.73.252: ICMP echo request, id > 64778, seq 1, length 64 > 15:24:25.892770 IP 10.91.73.252 > 10.100.100.74: ICMP echo reply, id > 64778, seq 1, length 64 > 15:24:25.896254 IP 10.91.73.253 > 10.91.73.252: ICMP time exceeded > in-transit, length 92 > (note 253 is the IP address of eth0 on the KVM host... odd) This might mean you enabled ipv4 forwarding on KVM host, so it tried to forward the packet on and could not. Try disabling it? > ping -c 1 external (10.91.73.252) -> guest (10.100.100.74) > > external: > 15:28:38.278291 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:28:38.278590 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.278760 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.278881 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.279024 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.279064 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.279157 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.279180 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.279299 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.279319 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.279361 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.279457 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.279478 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.279567 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.279612 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.279693 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.279738 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.279786 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.279877 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.279991 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.280000 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.280085 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.280105 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.280173 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.280202 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.280228 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.280271 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.280312 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.280401 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.280447 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.280534 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.280548 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.280581 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.280634 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.280766 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.280773 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.280805 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.280855 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.280902 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.280934 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.281014 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.281064 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.281113 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.281159 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.281215 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.281253 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.281300 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.281344 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.281408 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.281447 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.281503 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.281542 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.281644 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.281670 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.281723 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.281763 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.281816 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.281847 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.281918 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.281937 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.282059 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.282086 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.282153 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.282159 IP 10.91.73.253 > 10.91.73.252: ICMP time exceeded > in-transit, length 92 > 15:28:38.282175 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:28:38.282204 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > > guest: > 15:34:03.722851 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.722880 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.723023 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.723050 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 So, it is again the guest that gets duplicates. If it's a bug in vhost, it's a problem on RX path. > 15:34:03.723155 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.723165 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.723305 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.723316 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.723340 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.723349 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.723442 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.723452 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.723469 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.723478 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.723578 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.723588 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.723613 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.723623 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.723639 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.723658 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.723744 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.723753 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.723768 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.723776 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.723855 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.723864 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.723907 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.723916 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.723971 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.723981 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.724004 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.724013 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.724067 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.724078 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.724161 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.724171 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.724249 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.724258 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.724275 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.724284 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.724362 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.724371 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.724393 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.724402 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.724457 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.724467 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.724491 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.724500 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.724529 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.724538 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.724561 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.724570 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.724599 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.724608 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.724663 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.724683 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.724726 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.724737 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.724783 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.724806 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.724838 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.724848 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.724882 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.724891 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.724917 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.724925 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.725015 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.725027 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.725063 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.725080 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.725084 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.725102 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.725136 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.725156 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.725186 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.725199 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.725222 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.725230 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.725296 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.725308 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.725352 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.725360 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.725408 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.725416 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.725442 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.725450 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.725497 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.725505 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.725537 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.725545 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.725577 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.725596 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.725629 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.725637 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.725691 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.725701 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.725737 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.725744 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.725777 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.725797 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.725829 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.725837 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.725913 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.725924 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.725961 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.725969 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.726009 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.726016 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.726050 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.726058 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.726100 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.726107 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.726136 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.726143 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.726176 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.726195 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.726228 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.726235 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.726333 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.726343 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.726378 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.726385 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.726424 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.726431 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.726465 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.726473 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 > 15:34:03.726505 IP 10.91.73.252 > 10.100.100.74: ICMP echo request, id > 30800, seq 1, length 64 > 15:34:03.726512 IP 10.100.100.74 > 10.91.73.252: ICMP echo reply, id > 30800, seq 1, length 64 So, to eliminate networking setup issues, could you please use Or's patch to map raw networking device to virtio in userspace? (Don't forget to add promisc=n otherwise it'll set your card in promisc mode). > > A couple of extra datapoints to check: > > - What if you assign a different IP to the host (in the same subnet) and > > try external guest to host? > > I'm not sure what you mean by external guest. If I change the IP of > the host, nothing changes except the time exceeed messages seen by the > external system have the new IP. Sorry, I just meant ping from external to KVM host. But based on this data I do not expect any dups. > > - Is the card in promisc mode? What if you disable promisc mode? > > No, I'm using the physical MAC in the guest to avoid promisc. > > > Also, it seems that you have an external bridge that sends your outgoing > > packets back to you. Is that right? > > Not that I'm aware of. My config is simply: > > eth0 - host nic > eth10 - vhost nic > > I can ifdown eth0 and switch the host to eth10 and don't get duplicate > packets on host<->external pings. Thanks, > > Alex ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [PATCHv3 0/4] qemu-kvm: vhost net support 2009-08-18 21:23 ` Alex Williamson 2009-08-20 7:03 ` Michael S. Tsirkin @ 2009-08-20 7:03 ` Michael S. Tsirkin 1 sibling, 0 replies; 22+ messages in thread From: Michael S. Tsirkin @ 2009-08-20 7:03 UTC (permalink / raw) To: Alex Williamson; +Cc: avi, kvm, virtualization On Tue, Aug 18, 2009 at 03:23:02PM -0600, Alex Williamson wrote: > On Tue, Aug 18, 2009 at 3:11 PM, Alex Williamson<alex.williamson@hp.com> wrote: > > On Tue, Aug 18, 2009 at 3:04 PM, Michael S. Tsirkin<mst@redhat.com> wrote: > >> Did you assign ip address in host by any chance? You don't want that. > > > > Nope, just up on the host, no IP: > > > > eth10 Link encap:Ethernet HWaddr 00:17:a4:77:a4:08 > > inet6 addr: fe80::217:a4ff:fe77:a408/64 Scope:Link > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:22446487 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:4529008 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:1492187453 (1.3 GiB) TX bytes:2972806236 (2.7 GiB) > > Memory:fbae0000-fbb00000 > > > > Hmm, I lose the dupe and get pretty respectable tcp_rr rates if I use > the host as my target IP, is the issue maybe isolated to off-box > communication? I think the duplicates are our best hint that something's wrong at this point. Let's try to see where do they come from. What is it exactly that you see? This ping is external box to guest, correct? Is it the external box that gets duplicates or the guest? What happens when you ping the other way? What does tcpdump show on both sides when you ping? A couple of extra datapoints to check: - What if you assign a different IP to the host (in the same subnet) and try external guest to host? - Is the card in promisc mode? What if you disable promisc mode? Also, it seems that you have an external bridge that sends your outgoing packets back to you. Is that right? Thanks! > tcp_stream is still worse than userspace though. > > Alex ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [PATCHv3 0/4] qemu-kvm: vhost net support 2009-08-18 21:11 ` Alex Williamson 2009-08-18 21:23 ` Alex Williamson 2009-08-18 21:23 ` Alex Williamson @ 2009-08-23 19:22 ` Michael S. Tsirkin 2009-08-25 1:38 ` Alex Williamson 2009-08-25 1:38 ` Alex Williamson 2009-08-23 19:22 ` Michael S. Tsirkin 3 siblings, 2 replies; 22+ messages in thread From: Michael S. Tsirkin @ 2009-08-23 19:22 UTC (permalink / raw) To: Alex Williamson; +Cc: avi, kvm, virtualization, gregory.haskins On Tue, Aug 18, 2009 at 03:11:04PM -0600, Alex Williamson wrote: > On Tue, Aug 18, 2009 at 3:04 PM, Michael S. Tsirkin<mst@redhat.com> wrote: > > Did you assign ip address in host by any chance? You don't want that. > > Nope, just up on the host, no IP: > > eth10 Link encap:Ethernet HWaddr 00:17:a4:77:a4:08 > inet6 addr: fe80::217:a4ff:fe77:a408/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:22446487 errors:0 dropped:0 overruns:0 frame:0 > TX packets:4529008 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:1492187453 (1.3 GiB) TX bytes:2972806236 (2.7 GiB) > Memory:fbae0000-fbb00000 Just had a different, but slightly similar problem when the host running qemu had forwarding enabled. Is it possible your host is forwarding the packets somewhere else, and that's why we get the dupes? sysctl -w net.ipv4.conf.all.forwarding=0 -- MST ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [PATCHv3 0/4] qemu-kvm: vhost net support 2009-08-23 19:22 ` Michael S. Tsirkin @ 2009-08-25 1:38 ` Alex Williamson 2009-08-25 1:38 ` Alex Williamson 1 sibling, 0 replies; 22+ messages in thread From: Alex Williamson @ 2009-08-25 1:38 UTC (permalink / raw) To: Michael S. Tsirkin; +Cc: avi, kvm, virtualization On Sun, Aug 23, 2009 at 1:22 PM, Michael S. Tsirkin<mst@redhat.com> wrote: > > Just had a different, but slightly similar problem when the host running > qemu had forwarding enabled. Is it possible your host is forwarding the > packets somewhere else, and that's why we get the dupes? > sysctl -w net.ipv4.conf.all.forwarding=0 Yes! This seems to be the problem. As expected, I can just disable forwarding on eth10 and the duplicates disappear. Thanks, Alex ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [PATCHv3 0/4] qemu-kvm: vhost net support 2009-08-23 19:22 ` Michael S. Tsirkin 2009-08-25 1:38 ` Alex Williamson @ 2009-08-25 1:38 ` Alex Williamson 1 sibling, 0 replies; 22+ messages in thread From: Alex Williamson @ 2009-08-25 1:38 UTC (permalink / raw) To: Michael S. Tsirkin; +Cc: avi, kvm, virtualization, gregory.haskins On Sun, Aug 23, 2009 at 1:22 PM, Michael S. Tsirkin<mst@redhat.com> wrote: > > Just had a different, but slightly similar problem when the host running > qemu had forwarding enabled. Is it possible your host is forwarding the > packets somewhere else, and that's why we get the dupes? > sysctl -w net.ipv4.conf.all.forwarding=0 Yes! This seems to be the problem. As expected, I can just disable forwarding on eth10 and the duplicates disappear. Thanks, Alex ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [PATCHv3 0/4] qemu-kvm: vhost net support 2009-08-18 21:11 ` Alex Williamson ` (2 preceding siblings ...) 2009-08-23 19:22 ` Michael S. Tsirkin @ 2009-08-23 19:22 ` Michael S. Tsirkin 3 siblings, 0 replies; 22+ messages in thread From: Michael S. Tsirkin @ 2009-08-23 19:22 UTC (permalink / raw) To: Alex Williamson; +Cc: avi, kvm, virtualization On Tue, Aug 18, 2009 at 03:11:04PM -0600, Alex Williamson wrote: > On Tue, Aug 18, 2009 at 3:04 PM, Michael S. Tsirkin<mst@redhat.com> wrote: > > Did you assign ip address in host by any chance? You don't want that. > > Nope, just up on the host, no IP: > > eth10 Link encap:Ethernet HWaddr 00:17:a4:77:a4:08 > inet6 addr: fe80::217:a4ff:fe77:a408/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:22446487 errors:0 dropped:0 overruns:0 frame:0 > TX packets:4529008 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:1492187453 (1.3 GiB) TX bytes:2972806236 (2.7 GiB) > Memory:fbae0000-fbb00000 Just had a different, but slightly similar problem when the host running qemu had forwarding enabled. Is it possible your host is forwarding the packets somewhere else, and that's why we get the dupes? sysctl -w net.ipv4.conf.all.forwarding=0 -- MST ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [PATCHv3 0/4] qemu-kvm: vhost net support 2009-08-18 20:54 ` Alex Williamson 2009-08-18 21:04 ` Michael S. Tsirkin @ 2009-08-18 21:04 ` Michael S. Tsirkin 1 sibling, 0 replies; 22+ messages in thread From: Michael S. Tsirkin @ 2009-08-18 21:04 UTC (permalink / raw) To: Alex Williamson; +Cc: avi, kvm, virtualization On Tue, Aug 18, 2009 at 02:54:23PM -0600, Alex Williamson wrote: > On Mon, Aug 17, 2009 at 6:37 AM, Michael S. Tsirkin<mst@redhat.com> wrote: > > This adds support for vhost-net virtio kernel backend. > > > > This is RFC, but works without issues for me. > > I got this to build by syncing up some headers in kvm/include/linux, > but it doesn't seem to be working quite right. I have an unused > e1000e nic in my system (eth10,00:17:a4:77:a4:08) that I ifconfig up, > then launch a VM with the option: > > -net nic,model=virtio,macaddr=00:17:a4:77:a4:08,vhost=eth10 > > The virtio nic is functional in the guest, but it gets packet dupes on > ping, which is likely contributing to the poor performance, roughly > 1/3rd of virtio-net userspace for tcp_stream and tcp_rr. I think I > have all the offload option disabled on the nic in the host. Any idea > what I might be doing wrong? This seems quite a bit off of the udp_rr > results you posted. Thanks, > > Alex Did you assign ip address in host by any chance? You don't want that. -- MST ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [PATCHv3 0/4] qemu-kvm: vhost net support 2009-08-17 12:37 [PATCHv3 0/4] qemu-kvm: vhost net support Michael S. Tsirkin ` (2 preceding siblings ...) 2009-08-18 20:54 ` Alex Williamson @ 2009-08-18 20:54 ` Alex Williamson 3 siblings, 0 replies; 22+ messages in thread From: Alex Williamson @ 2009-08-18 20:54 UTC (permalink / raw) To: Michael S. Tsirkin; +Cc: avi, kvm, virtualization On Mon, Aug 17, 2009 at 6:37 AM, Michael S. Tsirkin<mst@redhat.com> wrote: > This adds support for vhost-net virtio kernel backend. > > This is RFC, but works without issues for me. I got this to build by syncing up some headers in kvm/include/linux, but it doesn't seem to be working quite right. I have an unused e1000e nic in my system (eth10,00:17:a4:77:a4:08) that I ifconfig up, then launch a VM with the option: -net nic,model=virtio,macaddr=00:17:a4:77:a4:08,vhost=eth10 The virtio nic is functional in the guest, but it gets packet dupes on ping, which is likely contributing to the poor performance, roughly 1/3rd of virtio-net userspace for tcp_stream and tcp_rr. I think I have all the offload option disabled on the nic in the host. Any idea what I might be doing wrong? This seems quite a bit off of the udp_rr results you posted. Thanks, Alex ^ permalink raw reply [flat|nested] 22+ messages in thread
* [PATCHv3 0/4] qemu-kvm: vhost net support @ 2009-08-17 12:37 Michael S. Tsirkin 0 siblings, 0 replies; 22+ messages in thread From: Michael S. Tsirkin @ 2009-08-17 12:37 UTC (permalink / raw) To: avi, kvm, virtualization This adds support for vhost-net virtio kernel backend. This is RFC, but works without issues for me. Still needs to be split up, tested and benchmarked properly, but posting it here in case people want to test drive the kernel bits I posted. Changes since v2: - minor fixes - added patch to build on RHEL5.3 Changes since v1: - rebased on top of 9dc275d9d660fe1cd64d36102d600885f9fdb88a Michael S. Tsirkin (4): qemu-kvm: move virtio-pci.o to near pci.o virtio: move features to an inline function qemu-kvm: vhost-net implementation qemu-kvm: add compat eventfd Makefile.hw | 2 +- Makefile.target | 3 +- compat/sys/eventfd.h | 13 ++++ configure | 1 + hw/vhost_net.c | 181 ++++++++++++++++++++++++++++++++++++++++++++++++++ hw/vhost_net.h | 30 ++++++++ hw/virtio-balloon.c | 2 +- hw/virtio-blk.c | 2 +- hw/virtio-console.c | 2 +- hw/virtio-net.c | 34 +++++++++- hw/virtio-pci.c | 43 +++++++++++- hw/virtio.c | 19 ----- hw/virtio.h | 38 ++++++++++- net.c | 6 ++- net.h | 1 + qemu-kvm.c | 8 -- qemu-kvm.h | 9 +++ 17 files changed, 353 insertions(+), 41 deletions(-) create mode 100644 compat/sys/eventfd.h create mode 100644 hw/vhost_net.c create mode 100644 hw/vhost_net.h ^ permalink raw reply [flat|nested] 22+ messages in thread
end of thread, other threads:[~2009-08-25 1:38 UTC | newest] Thread overview: 22+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2009-08-17 12:37 [PATCHv3 0/4] qemu-kvm: vhost net support Michael S. Tsirkin 2009-08-17 12:48 ` Avi Kivity 2009-08-17 12:48 ` Avi Kivity 2009-08-18 20:54 ` Alex Williamson 2009-08-18 21:04 ` Michael S. Tsirkin 2009-08-18 21:11 ` Alex Williamson 2009-08-18 21:11 ` Alex Williamson 2009-08-18 21:23 ` Alex Williamson 2009-08-18 21:23 ` Alex Williamson 2009-08-20 7:03 ` Michael S. Tsirkin 2009-08-20 22:05 ` Alex Williamson 2009-08-20 22:05 ` Alex Williamson 2009-08-23 19:45 ` Michael S. Tsirkin 2009-08-23 19:45 ` Michael S. Tsirkin 2009-08-20 7:03 ` Michael S. Tsirkin 2009-08-23 19:22 ` Michael S. Tsirkin 2009-08-25 1:38 ` Alex Williamson 2009-08-25 1:38 ` Alex Williamson 2009-08-23 19:22 ` Michael S. Tsirkin 2009-08-18 21:04 ` Michael S. Tsirkin 2009-08-18 20:54 ` Alex Williamson -- strict thread matches above, loose matches on Subject: below -- 2009-08-17 12:37 Michael S. Tsirkin
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.