[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Strange networking issues

  • To: Simon Pearson <simon@xxxxxxxxxxxxx>
  • From: Nico Kadel-Garcia <nkadel@xxxxxxxxx>
  • Date: Sun, 15 Apr 2007 11:32:10 +0100
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Sun, 15 Apr 2007 03:29:25 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=NG3s2pfV69UtnP3esIYaOFR1NwKywkZviIxYKiiajo+hPV5ZL8MTcJmTHJU/uhN8xTIH5cEWTspIoQ28wUge8SnLm6IDXsTVJbPI3jCTGMs2Vtx4xU/2DXjZMpBNx34JY7dsBr7eonbu+l3vU5WL3NiXJXHTwQXIIwkWF5NVth0=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Simon Pearson wrote:
I have recently installed Xen 3.0.3 from Debian binaries (Etch) which
was very painless and made the installation process very simple. I was
very impressed.

Having setup/configured Xen for 3 domUs, using xen-tools to setup the
machines, so far so good; that is until one of the guest domains
encounters a slight load. Upon a domU encountering load (e.g. an rsync, make, ...) network
performance becomes poor, and ICMP works as proof of concept; whilst the
domU is under load, every ping consistently rises to 30-80ms - and this
is just pinging the dom0 IP from a domU! Note that I initially thought
this could have been a NIC issue as eth0 is a tg3-based NIC, however
swapping the cat5 over to eth1 (e100-based NIC) the problem still
exists. I am using bridging.
I wonder if you're RAM strapped and swapping like mad? rsync over SSH, for example, is a serious load.

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.