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

Re: [Xen-users] unstable network problem

To: Tim Durack <tdurack@xxxxxxxxx>
Subject: Re: [Xen-users] unstable network problem
From: Nivedita Singhvi <niv@xxxxxxxxxx>
Date: Tue, 09 Aug 2005 15:18:18 -0700
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 09 Aug 2005 22:16:41 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <9e246b4d050809112474679607@xxxxxxxxxxxxxx>
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>
References: <9e246b4d050809112474679607@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 0.8 (X11/20041020)
Tim Durack wrote:
txqueuelen didn't work here either.

For what it's worth, here's what the capture looks like for Dom0 -> guest:

For a temporary workaround, could you disable checksumming:

ethtool -K tx off

in each domain?

thanks,
Nivedita


tethereal -i eth0
device eth0 entered promiscuous mode
Capturing on eth0
  0.000000  192.168.1.1 -> 192.168.1.2  TCP 59135 > ssh [SYN] Seq=0
Ack=0 Win=5840 Len=0 MSS=1460 TSV=122820 TSER=0 WS=2
  0.002181  192.168.1.2 -> 192.168.1.1  TCP ssh > 59135 [SYN, ACK]
Seq=0 Ack=1 Win=5792 Len=0 MSS=1460 TSV=115220 TSER=122820 WS=1
  0.003497  192.168.1.1 -> 192.168.1.2  TCP 59135 > ssh [ACK] Seq=1
Ack=1 Win=5840 Len=0 TSV=122820 TSER=115220
  0.010001  192.168.1.2 -> 192.168.1.1  SSH Server Protocol:
SSH-2.0-OpenSSH_4.1p1 Debian-6
  0.010472  192.168.1.1 -> 192.168.1.2  TCP 59135 > ssh [ACK] Seq=1
Ack=32 Win=5840 Len=0 TSV=122821 TSER=115221
  0.010478  192.168.1.1 -> 192.168.1.2  SSH Client Protocol:
SSH-2.0-OpenSSH_4.1p1 Debian-6
  0.215968  192.168.1.1 -> 192.168.1.2  SSHv2 [TCP Retransmission]
Client: Unknown (46)[Unreassembled Packet [incorrect TCP checksum]]
  0.635966  192.168.1.1 -> 192.168.1.2  SSHv2 [TCP Retransmission]
Client: Unknown (46)
  1.475967  192.168.1.1 -> 192.168.1.2  SSHv2 [TCP Retransmission]
Client: Unknown (46)
  3.155992  192.168.1.1 -> 192.168.1.2  SSHv2 [TCP Retransmission]
Client: Unknown (46)
5.466528 192.168.1.2 -> fe:ff:ff:ff:ff:ff ARP Who has 192.168.1.1? Tell 192.168.1.2
  5.466572  192.168.1.1 -> 192.168.1.2  ARP 192.168.1.1 is at fe:ff:ff:ff:ff:ff
  6.515988  192.168.1.1 -> 192.168.1.2  SSHv2 [TCP Retransmission]
Encrypted request packet len=31
 13.235996  192.168.1.1 -> 192.168.1.2  SSHv2 [TCP Retransmission]
Encrypted request packet len=31


Interestingly if I build two guests I can ssh between them just fine.

Tim:>

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




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