From owner-freebsd-xen@freebsd.org Tue May 10 14:49:46 2016 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5583DB360CB for ; Tue, 10 May 2016 14:49:46 +0000 (UTC) (envelope-from prvs=9316acc9e=wei.liu2@citrix.com) 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 "Verizon Public SureServer CA G14-SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AB01C11FB; Tue, 10 May 2016 14:49:44 +0000 (UTC) (envelope-from prvs=9316acc9e=wei.liu2@citrix.com) X-IronPort-AV: E=Sophos;i="5.24,604,1454976000"; d="scan'208";a="359548379" Date: Tue, 10 May 2016 15:48:33 +0100 From: Wei Liu To: Stephen Jones CC: "'K. Macy'" , 'Miguel C' , "wei.liu2@citrix.com" , "'freebsd-xen@freebsd.org'" Subject: Re: xn ethernet issues as DOMU under NetBSD DOM0 Message-ID: <20160510144833.GJ12241@citrix.com> References: <20160503072441.qgqgaw52sijybg4a@mac> <20160503093211.hkmbbqr6t2fbxqqa@mac> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-DLP: MIA2 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.22 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: Tue, 10 May 2016 14:49:46 -0000 I've only gotten two emails on this, so forgive me if this has been discussed. On Sat, May 07, 2016 at 04:11:52PM +0000, Stephen Jones wrote: > From: kmacybsd@gmail.com [mailto:kmacybsd@gmail.com] On Behalf Of K. Macy > >That would explain it. If the Linux backend supports TSO, then netfront will of course advertise TSO. And >presumably there's no way to query the netback, since Xen is linux-centric. Assuming you haven't already I would >disable TSO. > > > Or have you already tried that? > > This morning I've tried building a kernel without the TCP_OFFLOAD option. When booting the new system, I see this in dmesg: > > xn0: at device/vif/0 on xenbusb_front0 > xn0: Ethernet address: 00:16:3e:00:00:30 > xn0: backend features: feature-sg feature-gso-tcp4 > xn_txeof: WARNING: response is -1! > This means the backend returns -1 for the tx request, but -1 is just a general error code so it doesn't reveal much. It would be interesting to see if there is anything shown on the backend side -- if netbsd's netback logs something. > Ifconfig -v xn0 looks like: > > xn0: flags=8843 metric 0 mtu 1500 > options=403 > > Pings work, ftp works (I was able to get the src.txz file off of ftp.freebsd.org to build the kernel) > ssh does not work (handshaking fails) but I can login via telnet. However, just about anything > that requires lots of output gets a bit clobbered. > > Are there any other kernel/sysctl parameters I should be disabling? > > It is almost working, but I need help to know if this is a netfront or a netback issue. If it is a NetBSD issue > I'll move the discussion over to port-xen@netbsd.org I think what you can do is to try the same kernel with a Linux backend. That would be a good way of telling which side is at fault. Wei.