From owner-freebsd-xen@FreeBSD.ORG Fri Jun 20 09:55:10 2014 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 069257A0 for ; Fri, 20 Jun 2014 09:55:10 +0000 (UTC) Received: from SMTP02.CITRIX.COM (smtp02.citrix.com [66.165.176.63]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.citrix.com", Issuer "Cybertrust Public SureServer SV CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 511A72B46 for ; Fri, 20 Jun 2014 09:55:08 +0000 (UTC) X-IronPort-AV: E=Sophos;i="5.01,513,1400025600"; d="scan'208";a="145378281" Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 20 Jun 2014 09:55:00 +0000 Received: from [127.0.0.1] (10.80.16.47) by smtprelay.citrix.com (10.13.107.78) with Microsoft SMTP Server id 14.3.181.6; Fri, 20 Jun 2014 05:54:59 -0400 Message-ID: <53A404EF.4070400@citrix.com> Date: Fri, 20 Jun 2014 11:54:55 +0200 From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Karl Pielorz , Subject: Re: re. pr188261 - any way I can investigate further? References: <7B689F2C8C07F01AD552CA61@Mail-PC.tdx.co.uk> In-Reply-To: <7B689F2C8C07F01AD552CA61@Mail-PC.tdx.co.uk> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-DLP: MIA1 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jun 2014 09:55:10 -0000 On 18/06/14 15:11, Karl Pielorz wrote: > > Hi, > > I submitted a PR a while ago (pr188261) - or now, Bugzilla > > > I've updated this recently - as I found doing 'ifconfig xn0 -txcsum' on > a "client" will fix the issue, for just that client - but I'm still > unable to fix the 'router' VM in such a way as all clients don't need a > fix. > > I have a test system setup with all this now (and all of 9.2-S, 10-S, > and 11-Current have the issue) - is anyone able to point me in the right > direction of what I can do to investigate this further? (i.e. debug > things, packet captures, etc. etc.) > > We could really do with getting this fixed - we use FreeBSD as routers > on a few systems - as as they move to Xen we end up having to either > setup 2 pools (and be very, very careful about what machines we put on > each) in order to avoid this - or face running them in HVM mode for > which the performance is very, very poor. I suggest that you try to bring this to freebsd-net, I certainly don't have the network skills to know what's going on, maybe someone can provide more insight there which could help track this down (I can certainly help as much as possible with the Xen part). If not I will try to get a look, but I cannot tell when is that going to happen, I've got my plate quite full right now. Roger.