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@lists.xensource.com
http://lists.xensource.com/xen-users
> Is use a Windows Server 2003 R2 x64 on XEN with the 0.9.10 PV driversfrom> 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 >I see exactly this problem with SMP but not on UP. I assume you are running with vcpus > 1? James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
This is correct. If I try to add the cpu cores manually (cpus = "0,1"), nothing changed. Markus -- Q-MEX Networks Inh. Markus Plischke Grenzstraße 4 28832 Achim Tel: +49 (0) 4636 18700 49 Fax: +49 (0) 4202 889574 Email: info@q-mex.net http://www.q-mex.net -----Original Message----- From: James Harper [mailto:james.harper@bendigoit.com.au] Sent: Saturday, July 12, 2008 12:36 PM To: Markus Plischke; Xen-users@lists.xensource.com Subject: RE: [Xen-users] Problems with round trip times> Is use a Windows Server 2003 R2 x64 on XEN with the 0.9.10 PV driversfrom> 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 >I see exactly this problem with SMP but not on UP. I assume you are running with vcpus > 1? James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users