RE: xn ethernet issues as DOMU under NetBSD DOM0

[Stephen Jones]

kmacy writes:
> That's starting to sound like a bug in NetBSD's netback driver. Particularly 
> since it doesn't happen with a Linux dom0 (AFAIK).

What would allow the net installs of both 10.3 and 11.0 to be successful but 
then the installed system to exhibit symptoms though?
___
freebsd-xen@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"

RE: xn ethernet issues as DOMU under NetBSD DOM0

[Stephen Jones]

> > >Can you try with a HEAD snapshot? netfront has been recently reworked [0], 
> > >so there's a chance it is already fixed there.
> > >
> > >Roger.
> > 
> > Okay, I just grabbed an iso out of: 
> > /pub/FreeBSD/snapshots/ISO-IMAGES/10.3 and did a fresh install on a domu, 
> > but had the same result.  The ISO was time stamped April 30th, did I use 
> > the right one?
> 
> Oh, no, the changes weren't backported to 10. You need to use a 11.0 (HEAD) 
> image, just pick the newer amd64 or i386 one from:
> 
> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/11.0/
> 
> Roger.

Thank you for that clarification.  OK, I've used 11.0 and did a fresh install, 
but I'm still having the same issue.  I should clarify that the net installs 
using 
the same virtual ethernet interface (maybe not the same netfront?) works great 
for both 10.3 and 11.0 installs.   What is the difference between
the installation kernel and the installed system xn driver?  
___
freebsd-xen@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"

RE: xn ethernet issues as DOMU under NetBSD DOM0

[Stephen Jones]

On Tue, May 3, 2016 at 3:11 PM, Miguel C  wrote:
> This was reported by me and others a few times its was actually fixed 
> in some 10.0 (current build at the time) but we could never track it, 
> however it always seemed related to tso, netbsd backhend (as I was 
> told back then) doesn't support at least tso, and In fact I had the 
> same issue with Windwos Guests but the PV drivers dev fixed it (and it 
> was indeed related to this)

kmacy writes:
> 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?
> else can...

On the DOMU, right?

I believe I did an ifconfig xn0 -tso on the 10.3 install after reading about it 
in the manpage, but did not see any improvements. 
I'll give it a shot with the 11 snapshot and see if that resolves the issue. 
___
freebsd-xen@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"

xn ethernet issues as DOMU under NetBSD DOM0

[Stephen Jones]

Hello, I'm seeing a problem with networking running under FreeBSD 10.3 as a XEN 
DOMU (HVM) on a NetBSD 7 XEN DOM0 (XEN45).
In searching the list archives, I did see mentions of there being an issue with 
scatter/gather with symptoms affecting
ssh connections in/out going and likely other network issues.  Are there sysctl 
parameters or other settings that could get
around this issue?

The ssh symptom (as reported by others) looks like this:

debug1: Local version string SSH-2.0-OpenSSH_6.8 NetBSD_Secure_Shell-20150403
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.2 
FreeBSD-20160310
debug1: match: OpenSSH_7.2 FreeBSD-20160310 pat OpenSSH* compat 0x0400
debug1: Remote is NON-HPN aware
debug1: mac 0x0, -1 -1
debug1: SSH2_MSG_KEXINIT sent
Bad packet length 168430090.
debug1: mac 0x0, -1 -1
ssh_dispatch_run_fatal: message authentication code incorrect


___
freebsd-xen@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"

RE: xn ethernet issues as DOMU under NetBSD DOM0

[Stephen Jones]

From: kmacy...@gmail.com [mailto:kmacy...@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!

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-...@netbsd.org
___
freebsd-xen@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"