From owner-freebsd-xen@FreeBSD.ORG Mon Feb 17 09:46:29 2014 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B90481B9 for ; Mon, 17 Feb 2014 09:46:29 +0000 (UTC) Received: from mail.tdx.com (mail.tdx.com [62.13.128.18]) by mx1.freebsd.org (Postfix) with ESMTP id 55CE01991 for ; Mon, 17 Feb 2014 09:46:28 +0000 (UTC) Received: from Mail-PC.tdx.co.uk (storm.tdx.co.uk [62.13.130.251]) (authenticated bits=0) by mail.tdx.com (8.14.3/8.14.3/) with ESMTP id s1H9kJct083975 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 17 Feb 2014 09:46:20 GMT Date: Mon, 17 Feb 2014 09:46:20 +0000 From: Karl Pielorz To: =?UTF-8?Q?Roger_Pau_Monn=C3=A9?= , freebsd-xen@freebsd.org Subject: Re: Xen PV Networking issue - disable PV NIC in XENHVM FreeBSD? Message-ID: In-Reply-To: <52FA5BEA.6030307@citrix.com> References: <52F8FE87.1010705@citrix.com> <72C34BC121BD5A0FBDAEFA37@Mail-PC.tdx.co.uk> <52FA5BEA.6030307@citrix.com> X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.17 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: Mon, 17 Feb 2014 09:46:29 -0000 --On 11 February 2014 18:20 +0100 Roger Pau Monn=C3=A9 = =20 wrote: > You could try to disable the following: > > ifconfig xnX -rxcsum -txcsum -tso4 -lro As a follow-up to this, using: ifconfig xnX -rxcsum -txcsum Does actually fix the problem. I finally got a block of time to go through=20 all this stuff again the other day [it's amazing what difference actually=20 having a decent chunk of uninterrupted time makes!] You do need to be careful when setting this - as at one point, it seemed to = cause some kind of issue that may have flooded the network (if it did -=20 this would be the second time we've seen a XenServer DomU flood things by=20 jabbering the same packet over, and over). -Karl