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] ping in hvm domain not working correctly

To: <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] ping in hvm domain not working correctly
From: "Artur Linhart - Linux communication" <AL.LINUX@xxxxxxxxxxx>
Date: Mon, 23 Jul 2007 16:57:56 +0200
Delivery-date: Mon, 23 Jul 2007 07:55:57 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcfNOZImeVssUhQxQ+273AT7LCzpgQ==

Hello,

 

            I have found a strange behavior if pinging from the HVM domain (windows). I reproduced this behavior on different physical machines once in DomU Windows 2003 Server Enterprise x64 R2 and once in Windows 2000 advanced server (both with latest patches).

On both machines the ping response times seem to be generated randomly if running the OS instance as DomU (also negative response times are generated or received within the ICMP) – this could mean the ICMP packets are not delivered correctly by xen to DomU?

 

If the remote host cannot beaccessed, then the timeout comes correctlz. Onlz in the case the pinged host exists and answers such strange behavior occurs.

 

            Does anybody met this problem and what can be the resolution for this?

 

            With best regards

 

                        Archie

 

P.S.     Output of ping from the DomU:

 

C:\Documents and Settings\Administrator>ping www.linux.org

 

Pinging www.linux.org [198.182.196.56] with 32 bytes of data:

 

Reply from 198.182.196.56: bytes=32 time=5131ms TTL=51

Reply from 198.182.196.56: bytes=32 time=-8870ms TTL=51

Reply from 198.182.196.56: bytes=32 time=9185ms TTL=51

Reply from 198.182.196.56: bytes=32 time=-8995ms TTL=51

 

Ping statistics for 198.182.196.56:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 5131ms, Maximum =  -8870ms, Average =  1073740936ms

 

C:\Documents and Settings\Administrator>ping www.linux.org

 

Pinging www.linux.org [198.182.196.56] with 32 bytes of data:

 

Reply from 198.182.196.56: bytes=32 time=14239ms TTL=51

Reply from 198.182.196.56: bytes=32 time=-9624ms TTL=51

Reply from 198.182.196.56: bytes=32 time=-14019ms TTL=51

Reply from 198.182.196.56: bytes=32 time=-4163ms TTL=51

 

Ping statistics for 198.182.196.56:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 14239ms, Maximum =  -4163ms, Average =  1073738432ms

 

C:\Documents and Settings\Administrator>ping www.linux.org

 

Pinging www.linux.org [198.182.196.56] with 32 bytes of data:

 

Reply from 198.182.196.56: bytes=32 time=127ms TTL=51

Reply from 198.182.196.56: bytes=32 time=11026ms TTL=51

Reply from 198.182.196.56: bytes=32 time=-10796ms TTL=51

Reply from 198.182.196.56: bytes=32 time=-15530ms TTL=51

 

Ping statistics for 198.182.196.56:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 127ms, Maximum =  -10796ms, Average =  1073738030ms

 

C:\Documents and Settings\Administrator>

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>