xen-users
RE: [Xen-users] Problems with GPLPV network latency
Ive run the capture however on Dom0 nothing seems to be logged,
tcpdump -s0 -w dom0_vif.pcap arp
tcpdump: WARNING: peth0: no IPv4 address assigned
tcpdump: listening on peth0, link-type EN10MB (Ethernet), capture size
65535 bytes
^C53 packets captured
54 packets received by filter
0 packets dropped by kernel
I will email the DomU capture straight to you
Thanks
Ian
-----Original Message-----
From: James Harper [mailto:james.harper@xxxxxxxxxxxxxxxx]
Sent: 15 June 2010 00:13
To: Ian Tobin; Nick Couchman; xen-users@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-users] Problems with GPLPV network latency
In dom0:
tcpdump -s0 -w dom0_vif.pcap arp or icmp
Same filter in domU, whether you use tcpdump or wireshark
Then do a few pings etc.
James
> -----Original Message-----
> From: Ian Tobin [mailto:itobin@xxxxxxxxxxxxx]
> Sent: Tuesday, 15 June 2010 06:38
> To: Nick Couchman; James Harper; xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: RE: [Xen-users] Problems with GPLPV network latency
>
> Hi James,
>
> Can you tell me what info you need from the capture? i.e. any special
> command line options etc.
>
> FYI i have a windows 2003 DomU which is also seeing the same issue,
its
> that slow it took ages to download wireshark, i had to run the
constant
> ping so that it had connectivity, very odd.
>
> Im running with a Single cpu on the DomU.
>
> Thanks
>
> Ian
>
>
> -----Original Message-----
> From: Nick Couchman [mailto:Nick.Couchman@xxxxxxxxx]
> Sent: 08 June 2010 16:22
> To: James Harper; xen-users@xxxxxxxxxxxxxxxxxxx; Ian Tobin
> Subject: RE: [Xen-users] Problems with GPLPV network latency
>
> >
> > Are you really seeing high latency or just reported high latency? Eg
> > when it says 1200ms, does it really take an extra second?
>
> I'm seeing the high latency numbers reported in Windows, but not the
> actual latency. Must be the multi-CPU issue you mentioned, as I have
4
> vCPUs assigned to my domU.
>
> -Nick
>
>
>
>
> --------
>
> This e-mail may contain confidential and privileged material for the
> sole use of the intended recipient. If this email is not intended for
> you, or you are not responsible for the delivery of this message to
the
> intended recipient, please note that this message may contain SEAKR
> Engineering (SEAKR) Privileged/Proprietary Information. In such a
case,
> you are strictly prohibited from downloading, photocopying,
distributing
> or otherwise using this message, its contents or attachments in any
way.
> If you have received this message in error, please notify us
immediately
> by replying to this e-mail and delete the message from your mailbox.
> Information contained in this message that does not relate to the
> business of SEAKR is neither endorsed by nor attributable to SEAKR.
>
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|