From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Subject: Re: Strange network behaviour Date: Wed, 05 Dec 2007 15:13:10 +0100 Message-ID: <4756B1F6.5080102@eliteserver.biz> References: <4755D859.4090805@eliteserver.biz> <47567D6D.8060802@qumranet.com> <47567FC7.9040106@eliteserver.biz> <475680E8.4060508@qumranet.com> <475689E0.5020901@eliteserver.biz> <4756A538.1050303@qumranet.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Return-path: In-Reply-To: <4756A538.1050303-atKUWr5tajBWk0Htik3J/w@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org Sure, here the ping results from the host to the guest atm of the peaks: 64 bytes from postfix (195.24.77.173): icmp_seq=347 ttl=64 time=10.6 ms 64 bytes from postfix (195.24.77.173): icmp_seq=348 ttl=64 time=11.6 ms 64 bytes from postfix (195.24.77.173): icmp_seq=349 ttl=64 time=11.6 ms 64 bytes from postfix (195.24.77.173): icmp_seq=350 ttl=64 time=465 ms 64 bytes from postfix (195.24.77.173): icmp_seq=351 ttl=64 time=455 ms 64 bytes from postfix (195.24.77.173): icmp_seq=352 ttl=64 time=349 ms 64 bytes from postfix (195.24.77.173): icmp_seq=353 ttl=64 time=314 ms 64 bytes from postfix (195.24.77.173): icmp_seq=354 ttl=64 time=483 ms 64 bytes from postfix (195.24.77.173): icmp_seq=355 ttl=64 time=871 ms 64 bytes from postfix (195.24.77.173): icmp_seq=357 ttl=64 time=1889 ms 64 bytes from postfix (195.24.77.173): icmp_seq=358 ttl=64 time=1635 ms 64 bytes from postfix (195.24.77.173): icmp_seq=359 ttl=64 time=1973 ms 64 bytes from postfix (195.24.77.173): icmp_seq=360 ttl=64 time=1796 ms 64 bytes from postfix (195.24.77.173): icmp_seq=361 ttl=64 time=1961 ms 64 bytes from postfix (195.24.77.173): icmp_seq=362 ttl=64 time=2029 ms 64 bytes from postfix (195.24.77.173): icmp_seq=363 ttl=64 time=1994 ms 64 bytes from postfix (195.24.77.173): icmp_seq=364 ttl=64 time=1689 ms 64 bytes from postfix (195.24.77.173): icmp_seq=365 ttl=64 time=932 ms 64 bytes from postfix (195.24.77.173): icmp_seq=366 ttl=64 time=899 ms 64 bytes from postfix (195.24.77.173): icmp_seq=367 ttl=64 time=752 ms 64 bytes from postfix (195.24.77.173): icmp_seq=368 ttl=64 time=860 ms 64 bytes from postfix (195.24.77.173): icmp_seq=369 ttl=64 time=483 ms 64 bytes from postfix (195.24.77.173): icmp_seq=370 ttl=64 time=244 ms 64 bytes from postfix (195.24.77.173): icmp_seq=371 ttl=64 time=7.89 ms 64 bytes from postfix (195.24.77.173): icmp_seq=372 ttl=64 time=5.98 ms 64 bytes from postfix (195.24.77.173): icmp_seq=373 ttl=64 time=6.31 ms The peaks started @ +/- 14:53:39 and ended @ +/- 14:53:59 You can download the trace file at: http://www.eliteserver.biz/trace2.tar.gz Avi Kivity schrieb: > Mike wrote: > >> You can download the requested trace at >> http://www.eliteserver.biz/trace.tar.gz >> >> the peaks were around 12:04:30 >> >> >> > > Can you rerun, this time with additional options '-x -s 80' to strace > (so I can identify the pings from random broadcast noise on the > network). Also please run ping on the host itself, so I get regular > timing without jitter from the Internet. > > > ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4