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] Lots of udp (multicast) packet loss in domU

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Lots of udp (multicast) packet loss in domU
From: Mike Kazmier <DaKaZ@xxxxxxxxx>
Date: Tue, 13 Jan 2009 00:42:04 +0000
Delivery-date: Mon, 12 Jan 2009 16:42:50 -0800
Dkim-signature: v=1; a=rsa-sha256; c=simple/simple; d=zenbe.com; s=mail; t=1231807325; bh=l2pfEjyDVfK6JPL8RkDILHR4U1ume10UT+o9FREWVEY=; h=Date:From:To:Message-Id:Subject:Mime-Version:Content-Type; b=hEdG gBHk5dP7yYEtI/bC3BiHit5DNvEBT8PzsQsEpoQ/LtKHPrDY/hVmSq1fjdS2sepjCaQ 8x0KArhBiTgxD7yrz+qxCJLXapNYhd3TXDoGKiO8FS0G5cXdUbFKGrtfBNWNFRnFka2 7x0w1YYiCbzdO7/BY1ESCV3Yk5hZ9oAH8=
Domainkey-signature: a=rsa-sha1; s=mail; d=zenbe.com; c=simple; q=dns; b=aAiOoVdLtM+KNG7+EdepVcSkEzLKD8e1USXR3eceHZEaBxAvbk1cjDPSR2zyT/MeF xMfsv9mP04ozXc0Z7XfRAWROhcP0JEOyfyAqvxyeCQ++LlOZuxDFI/vfeLMR+irhGCq gHDgkBDwIVePEgnGPWmJCUJTaM0cKWwqyCyuK7A=
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,

After a few of us have spent a week google'ing around for answers, I feel 
compelled to ask this question: how do I stop packet loss between my dom0 and 
domU?  We are currently running a xen-3.3.0 (and have tried with xen-3.2.1) on 
a Gentoo system with 2.6.18 kernel for both domU and dom0.  We have also tried 
a 2.6.25 kernel for dom0 with exactly the same results.

The goal is to run our multicast processing application in a domU with the 
BRIDGED configuration.  Note: we do not have any problem if we put the network 
interfaces into PCI Passthrough and use them exclusively in the domU, but that 
is less than ideal as occasionally other domU's need to communicate with those 
feeds.  

So, when we have little (sub 100 Mbps) of multicast traffic coming, everything 
is fine.  Over that, we start to see packet loss approaching 5%.  But the loss 
is only seen in the domU.  I can run our realtime analysis tool in the dom0 and 
domU at the same time, on the same multicast feed and found that in the dom0, 
all packets are accounted for.  Initially, I found a large number of dropped 
frames on the VIF interface, but after running " echo -n 256 > 
/sys/class/net/eth2/rxbuf_min " all reported errors have gone away (ie, dom0 
does not report dropping any packets) but we still see loss.

Any suggestions at all would be greatly appreciated.  I know we have something 
borked on our end since this white paper shows high domU udp performace: 
http://www.cesnet.cz/doc/techzpravy/2008/effects-of-virtualisation-on-network-processing
 - but at the same time a qoogle search shows tons of issues around UDP packet 
loss with Xen.  Any help would be greatly appreciaited.  

The hardware is an 8 core, 2.33 GHz penryn (Xeon) based system.  We have Intel 
quad GigE nics with the latest intel IGB drivers.  Here is the current domU 
config:

----------------------------------
# general
name    = "xenF";
memory  = 1024;
vcpus = 6;
builder = "linux";
on_poweroff = "destroy";
on_reboot = "restart";
on_crash = "restart";
cpu_weight = 1024  # xenF processes get 4 times default (256) priority threads
cpu_cap = 600  #Don't use more than 6 real CPUs

# This lets us use the xm console
extra = " console=xvc0 xencons=xvc0";

# booting
kernel  = "/boot/vmlinuz-2.6.18-xen-domU";

# virtual harddisk
disk = [ "file:/var/xen/domU-xenF,xvda1,w" ];
root = "/dev/xvda1 ro";

# virtual network
vif    = [ "bridge=xenbr0", "bridge=xenbr1", "bridge=xenbr2"]


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