Maurice Volaski wrote:
At 5:02 PM +0800 4/8/10, Min Miles Xu wrote:
Hi Maurice,
Did you notice how much time it took for the ping request packet to
arrive at the Windows machine and how much time for the echo packet?
And could you run the dtrace script in the attachment while you ping?
Just type "dtrace -s e1000g_tx.d"
At first, running ping from the OpenSolaris VM doesn't display
anything. Eventually, it does like so
64 bytes from thevaultinternal (172.16.1.2): icmp_seq=7944.
time=1549727.719 ms
64 bytes from thevaultinternal (172.16.1.2): icmp_seq=7947.
time=1547915.398 ms
64 bytes from thevaultinternal (172.16.1.2): icmp_seq=7951.
time=1546165.354 ms
64 bytes from thevaultinternal (172.16.1.2): icmp_seq=7952.
time=1546227.851 ms
64 bytes from thevaultinternal (172.16.1.2): icmp_seq=7954.
time=1545352.856 ms
64 bytes from thevaultinternal (172.16.1.2): icmp_seq=7955.
time=1545415.344 ms
On the Windows side, I see the pings being received and replied to.
This suggests to me it's the same problem described in the other
thread. And if you are right about that, it implies that even if I
could try a different NIC, it might still exhibit this behavior.
What's puzzling is why I can't seem to trigger it by running multiple
rsh threads and why many other users aren't experiencing it. It's not
a new problem. I've seen in way earlier builds, possibly b110!
Hmm, according to the dtrace output, it takes no more than 1799 ms for a
kernel's ICMP round-trip. But the ping output showed approaching 100
times longer. It seems to be something wrong inside the VM. Does
somebody else have any ideas?
Miles
_______________________________________________
networking-discuss mailing list
[email protected]
