WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Problems with round trip times

To: "Xen-users@xxxxxxxxxxxxxxxxxxx" <Xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] Problems with round trip times
From: Markus Plischke <m.plischke@xxxxxxxxx>
Date: Fri, 11 Jul 2008 15:42:45 +0200
Accept-language: de-DE, en-US
Acceptlanguage: de-DE, en-US
Cc:
Delivery-date: Fri, 11 Jul 2008 06:43:23 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcjjW//cGCmh58StRbasYpYC4cxDwA==
Thread-topic: Problems with round trip times
Is use a Windows Server 2003 R2 x64 on XEN with the 0.9.10 PV drivers from 
James.
But with and without these driver I have the same problem:


C:\Program Files\Support Tools>ping 172.16.1.3

Pinging 172.16.1.3 with 32 bytes of data:

Reply from 172.16.1.3: bytes=32 time=24317ms TTL=128
Reply from 172.16.1.3: bytes=32 time<1ms TTL=128
Reply from 172.16.1.3: bytes=32 time<1ms TTL=128
Reply from 172.16.1.3: bytes=32 time<1ms TTL=128

Ping statistics for 172.16.1.3:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 24317ms, Average = 6079ms

C:\Program Files\Support Tools>ping 172.16.1.3

Pinging 172.16.1.3 with 32 bytes of data:

Reply from 172.16.1.3: bytes=32 time<1ms TTL=128
Reply from 172.16.1.3: bytes=32 time=24317ms TTL=128
Reply from 172.16.1.3: bytes=32 time=24317ms TTL=128
Reply from 172.16.1.3: bytes=32 time=24317ms TTL=128

Ping statistics for 172.16.1.3:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 24317ms, Average = 18237ms


172.16.1.3 is not a XEN Domain.


How can I fix this problem? It is a Clock problem that i can fix with the 
"independent_wallclock" Option?


Kind Regards

Markus Plischke



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>