Date: Tue, 10 May 2016 15:48:33 +0100 From: Wei Liu <wei.liu2@citrix.com> To: Stephen Jones <StephenJo@LivingComputerMuseum.org> Cc: "'K. Macy'" <kmacy@freebsd.org>, 'Miguel C' <miguelmclara@gmail.com>, "wei.liu2@citrix.com" <wei.liu2@citrix.com>, "'freebsd-xen@freebsd.org'" <freebsd-xen@freebsd.org> Subject: Re: xn ethernet issues as DOMU under NetBSD DOM0 Message-ID: <20160510144833.GJ12241@citrix.com> In-Reply-To: <C4D720DD281F6740AC917B82741E9AD2AB27D9A0@505MBX1.corp.vnw.com> References: <20160503072441.qgqgaw52sijybg4a@mac> <C4D720DD281F6740AC917B82741E9AD2AB27C045@505MBX1.corp.vnw.com> <20160503093211.hkmbbqr6t2fbxqqa@mac> <C4D720DD281F6740AC917B82741E9AD2AB27C2AA@505MBX1.corp.vnw.com> <CAHM0Q_NefH4zbtRY8MB5_90r=FCZAmki=riogNbktxyzSzLXFw@mail.gmail.com> <C4D720DD281F6740AC917B82741E9AD2AB27C323@505MBX1.corp.vnw.com> <CADGo8CXsWJ%2B9AroeOXvruWLiuLiAUd%2BPu687Vp=g789EJtDFPw@mail.gmail.com> <CAHM0Q_MO_pFSnLYtmikxL1qWOETO4avd0%2BaOEn%2B7=nZTT3_tuw@mail.gmail.com> <C4D720DD281F6740AC917B82741E9AD2AB27C4EC@505MBX1.corp.vnw.com> <C4D720DD281F6740AC917B82741E9AD2AB27D9A0@505MBX1.corp.vnw.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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: <Virtual Network Interface> 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<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 > options=403<RXCSUM,TXCSUM,LRO> > > 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160510144833.GJ12241>