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] Large Network Traffic brings the server down

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Large Network Traffic brings the server down
From: Pepe Barbe <elventear@xxxxxxxxx>
Date: Wed, 20 Aug 2008 15:41:49 -0500
Delivery-date: Wed, 20 Aug 2008 13:43:18 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:from:to :content-type:content-transfer-encoding:mime-version:subject:date :x-mailer; bh=ZNx31Ht+UJjH9CTKSvgW5y0zfL1856lMSWZGc99wN5A=; b=JS1EnW06ySK3xF1gCgyUzcEmxqNa2pBUeSufHeFjRoLtgWhrzGH8RPnEGkvTA/TZx0 mDLmny+skkch4oplBiSSPZ7y94HImENwKVMLrqXBP+P79+pKiM5S7CAkPvkjv4Ivxj3S wbl/K2+he55ltj9KeSXQflrsGXUelfMBwsoqo=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:content-type:content-transfer-encoding :mime-version:subject:date:x-mailer; b=Yr1l0Z1p9D7EpMUOeOEC7pflvYtFVopMEtdVVEovUEL2UVtNAirXV++Mz5Gm6OO9x0 sBjRi+yurmqBCYPFJB7cs2/dlfLk4EGTPORNHj3HX6IA/jgp5F7ezVQ1cu4O+8qe0QPN 61wA+KlpYZWeRhZ3DYMaWgf4RfUk4tEqfbeCM=
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
Hello everyone,

I am having some problems serious problems with our Xen setup. I noticed the problem when doing an rsync from the dom0 to the WAN. Before I start explaining anything else, let me post a diagram of the my Xen setup topology to make things more explanatory. The letters before the NIC name mean:

pb: Bridge+Physical IF
v: Virtual IF
p: Physical IF

                        .-----.
                        . LAN .
                        '-----'
                           ^
                           |
                           |
.----------------. | .----------------. .----------------. | dom0 | | | domU | | domU | |----------------| | |----------------| |----------------| | | | | router | | DMZ | | | | | | | | | pb:eth0----v:eth0 v:eth1 ------- b:eth0 | | | | | | | | '----------------' | '-----p:eth2 ----' '----------------'
                           |                  |
                           |                  |
                           |                  |
        .----------------. |                  v
        |      domU      | |               .-----.
        |----------------| |               . WAN .
        | Local Server   | |               '-----'
        |               v:eth0
        |                |
        |                |
        '----------------'

Basically what happens is that the link between the dom0 and the domU:router dies; I've noticed that as we start the transfer, the ping delay time from the dom0 to the Wan starts to increase until a point of no return is reached; after which the traffic stops flowing all together. If I kill my large transfer before this point is reached, the link recovers and everything is back to normal.

I already had disabled TCP TX checksumming on all the virtual interfaces so it seems the problem is not related to this, although it behaves similarly as what other people have described.

When the link between the dom0 and domU:router is effectively killed, I attached to the router's console, via Xen, and verified it is up and still able to reach the WAN, which it was.

Other things I've noticed is that when the dom0 link dies is that it starts behaving erratically. I tried to destroy and create the domUs and some processes went into uninterruptible sleep, making it impossible to do anything with the server.

This server has been running since April/08 on Ubuntu 8.04. It has been running without mayor hiccups, after the main linux-xen fixes had been officially released by Ubuntu. I've done rsyncs not so long ago and the only thing that has changed is that our DSL was upgraded from 1.5 Mbps to 7 Mbps; I don't know if the speed change could be big enough to trigger this issue.

So, after the preamble, my questions are: Is this a known issue? Any workarounds? If not, any ideas on what to do to troubleshoot it?

Thanks,
Pepe

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

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