public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Dor Laor <dlaor@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: Sven Rudolph <Sven_Rudolph@drewag.de>,
	kvm@vger.kernel.org, "Roedel, Joerg" <Joerg.Roedel@amd.com>
Subject: Re: Windows 2003: ping -n doesn't wait
Date: Sat, 24 Jan 2009 01:53:46 +0200	[thread overview]
Message-ID: <497A588A.40209@redhat.com> (raw)
In-Reply-To: <20090123205512.GA3911@amt.cnet>

Marcelo Tosatti wrote:
> On Tue, Jan 20, 2009 at 03:53:06PM +0100, Sven Rudolph wrote:
>   
>> Hello,
>>
>> first the facts required by bug reporting guidelines:
>>
>> - two Quad-Core AMD Opteron(tm) Processors 2352
>> - kvm-83 (both kernel and userland)
>> - Host kernel: 2.6.28.1, x86_64 
>> - guest:
>>   - 4 CPUs assigned to this guest (-smp 4)
>>   - Microsoft Windows 2003 Server, Standard Edition, Service Pack 2
>> - qemu command line:
>>   qemu-system-x86_64 -m 4096 -boot c -hda hda.dat -smp 4 \
>>     -net nic,macaddr=00:50:56:24:0b:37,model=virtio \
>>     -net tap,ifname=vm03,script=no,downscript=no
>>
>> The problem: When running "ping -n 3 localhost" on the guest it should
>> wait one second between each ping request and the time needed should
>> be non-negative and below 10 ms. Instead, ping does not actually wait
>> between sending the packets, and the time for the requests ist often
>> displayed to be too large or negative. Simple examples:
>>
>>   [WinNT] ping -n 3 localhost
>>
>>   Ping wird ausgefhrt fr localhost [127.0.0.1] mit 32 Bytes Daten:
>>
>>   Antwort von 127.0.0.1: Bytes=32 Zeit=-465ms TTL=128
>>   Antwort von 127.0.0.1: Bytes=32 Zeit=-613ms TTL=128
>>   Antwort von 127.0.0.1: Bytes=32 Zeit=-465ms TTL=128
>>     
>
> Sven, Dor,
>
> Can you try to use the AMD CPU drivers for Windows? 
>
> Take a look at http://forums.citrix.com/thread.jspa?threadID=93813
>
> http://www.therightstuff.de/2007/06/05/The-Case-Of-The-Negative-Ping.aspx
>
> I don't doubt the KVM tsc syncing code for AMD is not involved, though.
>
>   
Installing AMD's driver for powerNow solves this issue.
Joerg, can you please supply us some explanations?
Thanks,
Dor
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>   


  reply	other threads:[~2009-01-23 23:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-20 14:53 Windows 2003: ping -n doesn't wait Sven Rudolph
2009-01-21 14:05 ` Dor Laor
2009-01-23 16:45   ` Marcelo Tosatti
2009-01-23 20:55 ` Marcelo Tosatti
2009-01-23 23:53   ` Dor Laor [this message]
2009-01-26 17:09   ` Sven Rudolph

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=497A588A.40209@redhat.com \
    --to=dlaor@redhat.com \
    --cc=Joerg.Roedel@amd.com \
    --cc=Sven_Rudolph@drewag.de \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox