Date: Wed, 04 Apr 2018 20:17:14 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 215737] [bhyve] utilizing virtio-net truncates jumbo frames at 4084 bytes length Message-ID: <bug-215737-27103-ezudlouPnt@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-215737-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-215737-27103@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215737 --- Comment #9 from Harald Schmalzbauer <bugzilla.freebsd@omnilan.de> --- (In reply to P Kern from comment #8) *offtopic, vmxnet3 specific only, nothing PR related in this comment*: It's correct that if_vmx(4) does not mention MTU or "jumbo" frames, but I w= as quiet sure it _does_ support 9k frames =E2=80=93 just verified positive (st= able/11 on ESXi6.5)! if_vmx(4) has been improved over the time, but it still lacks ALTQ support. And vmx3f(4) is still a bit more efficient. Else, if_vmx(4) is featurewise on par with vmx3f(4). Unfortunately vmx3f(4) isn't supported by VMware any longer. I made a patch which allows vmx3f(4) to be compiled on FreeBSD-11, and it a= lso seems to be stable _without_ ALTQ. ALTQ causes panics!!! Unfortunately my skills/time don't last to fix. Here's the compile-patch in case somebody wants to take over: ftp://ftp.omnilan.de/pub/FreeBSD/OmniLAN/vmware-esxi_kernel-modules/10.1.5/= FreeBSD-11_vmxnet3-Tools_10.1.5-source.patch -harry --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-215737-27103-ezudlouPnt>