Date: Sat, 7 May 2016 23:28:08 +0200 From: Sydney Meyer <syd.meyer@gmail.com> To: freebsd-xen@freebsd.org Subject: Re: xn ethernet issues as DOMU under NetBSD DOM0 Message-ID: <9C3BC090-7320-4BCC-9F54-F9DFE29E3A26@gmail.com> In-Reply-To: <C4D720DD281F6740AC917B82741E9AD2AB27D9A0@505MBX1.corp.vnw.com> References: <C4D720DD281F6740AC917B82741E9AD2AB27BC39@505MBX1.corp.vnw.com> <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
Hello, i don't know if this helps or is related to the problem, but i = also had/have trouble with networking on FreeBSD DomUs, particularly = with packet forwarding. For this purpose i'm running NetBSD 7.0 as a = virtual router, because OpenBSD 5.9 seems to have the same problem. = Perhaps this might help you narrow down the issue. See also: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D188261 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D154428 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D197344 > On May 7, 2016, at 18:11, Stephen Jones = <StephenJo@LivingComputerMuseum.org> wrote: >=20 > 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. >=20 >> Or have you already tried that? >=20 > This morning I've tried building a kernel without the TCP_OFFLOAD = option. When booting the new system, I see this in dmesg: >=20 > 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! >=20 > Ifconfig -v xn0 looks like: >=20 > xn0: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 = mtu 1500 > options=3D403<RXCSUM,TXCSUM,LRO> >=20 > 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. >=20 > Are there any other kernel/sysctl parameters I should be disabling? >=20 > 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 > _______________________________________________ > freebsd-xen@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-xen > To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9C3BC090-7320-4BCC-9F54-F9DFE29E3A26>