From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Subject: Re: Strange network behaviour Date: Wed, 05 Dec 2007 12:22:08 +0100 Message-ID: <475689E0.5020901@eliteserver.biz> References: <4755D859.4090805@eliteserver.biz> <47567D6D.8060802@qumranet.com> <47567FC7.9040106@eliteserver.biz> <475680E8.4060508@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: <475680E8.4060508-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 You can download the requested trace at http://www.eliteserver.biz/trace.tar.gz the peaks were around 12:04:30 Mike Avi Kivity schrieb: > Mike wrote: > >> Avi Kivity schrieb: >> >> >>> Mike wrote: >>> >>> >>> >>>> Now I noticed a strange behaviour. >>>> I have a gameserver running in a guest os. No problems on performance >>>> side, really fast. >>>> The only thing, when I make a ping test after unspecific time periods I >>>> get this: (this peaks are even there if the gameserver isn't running) >>>> >>>> >>>> As you can see, no peaks. >>>> Example of start command from a guest: >>>> kvm -hda apache.img -hdb apache_storage.img -m 512 -boot c -net >>>> nic,vlan=0,macaddr=00:16:3e:00:00:01,model=rtl8139 -net tap -nographic >>>> -daemonize >>>> >>>> Here the pings from the guest started with the command line listed above: >>>> >>>> Reply from 195.24.77.171: bytes=32 time=37ms TTL=57 >>>> Reply from 195.24.77.171: bytes=32 time=37ms TTL=57 >>>> Reply from 195.24.77.171: bytes=32 time=97ms TTL=57 >>>> Reply from 195.24.77.171: bytes=32 time=60ms TTL=57 >>>> Reply from 195.24.77.171: bytes=32 time=186ms TTL=57 >>>> Reply from 195.24.77.171: bytes=32 time=363ms TTL=57 >>>> Reply from 195.24.77.171: bytes=32 time=368ms TTL=57 >>>> Reply from 195.24.77.171: bytes=32 time=972ms TTL=57 >>>> Reply from 195.24.77.171: bytes=32 time=673ms TTL=57 >>>> Reply from 195.24.77.171: bytes=32 time=1133ms TTL=57 >>>> Reply from 195.24.77.171: bytes=32 time=1198ms TTL=57 >>>> Reply from 195.24.77.171: bytes=32 time=1881ms TTL=57 >>>> Reply from 195.24.77.171: bytes=32 time=2341ms TTL=57 >>>> Reply from 195.24.77.171: bytes=32 time=2401ms TTL=57 >>>> >>>> >>>> >>>> >>> What guest are you running? >>> >>> 'kvm' isn't the name of the binary generated by make. Are you sure it >>> is actually the binary from kvm-55? >>> >>> >>> >>> >> I'm running debian etch with kernel Linux 2.6.18-5-486 #1 Tue Oct 2 >> 23:38:54 UTC 2007 i686 GNU/Linux >> as guest. All the guests are running this distr. >> My kvm is pointing to /usr/local/bin/qemu-system-x86_64 >> 2007-12-04 15:29 /usr/local/bin/qemu-system-x86_64 >> >> > > Ok. How long does it take for the latency to appear? If it isn't too > long, please run kvm with > > strace -fF -ttT -o /tmp/trace kvm ... > > Note the time that latency appears so we can correlate with the logs. > Be aware the logs can be quite large, so make sure you have some disk > space ready. > > > ------------------------------------------------------------------------- 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