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] W2K3 HVM with gplpv shows strange pings

To: xen-users@xxxxxxxxxxxxxxxxxxx, James Harper <james.harper@xxxxxxxxxxxxxxxx>
Subject: [Xen-users] W2K3 HVM with gplpv shows strange pings
From: Andreas Pflug <pgadmin@xxxxxxxxxxxxxxxxx>
Date: Mon, 18 May 2009 11:46:09 +0200
Cc:
Delivery-date: Mon, 18 May 2009 02:47:22 -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
User-agent: Thunderbird 2.0.0.21 (Windows/20090302)
I just migrated a W2K3 Server to a Xen HVM domain, using the gplpv
0.10.69 drivers.
Now ping shows strange results:

Pinging 127.0.0.1 with 32 bytes of data:

Reply from 127.0.0.1: bytes=32 time=23538ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time=-23538ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Same result with external addresses (which I checked first, when I found
that iScsiInitator doesn't work any more)

Apparently the xen pci driver also installs the "High precision event
timer", so I suspect a misbehaviour in the gplpv driver.

Any clues?

Regards,
Andreas


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

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