Date: Tue, 13 Jun 2017 10:06:43 +0200 From: Harry Schmalzbauer <freebsd@omnilan.de> To: Peter Grehan <grehan@freebsd.org> Cc: "Rodney W. Grimes" <freebsd-rwg@pdx.rh.CN85.dnsmgr.net>, freebsd-virtualization@freebsd.org Subject: Re: VNC stuff Message-ID: <593F9D13.6040604@omnilan.de> In-Reply-To: <b5fbe0ff-9013-70ab-fc21-57aa9044ff18@freebsd.org> References: <201706130102.v5D125Xm053949@pdx.rh.CN85.dnsmgr.net> <b5fbe0ff-9013-70ab-fc21-57aa9044ff18@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Bezüglich Peter Grehan's Nachricht vom 13.06.2017 06:39 (localtime): > Hi Rod, > >> r302504 is not likely to be MFC'ed at this time, this is the e1000 >> driver >> and man page. This code has known issues at this time and is an action >> item list on the bhyve developers work list. > > The e1000 driver was MFC'd 11 months ago. The issues are currently > only with Windows - it works fine with Linux/*BSD/Solaris. I'm hoping > that the Windows issue can be fixed before 11.1. While we're at issues: virtio-net as one unresolved: [bhyve] utilizing virtio-net truncates jumbo frames at 4084 bytes length <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215737>; https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215737 Most likely this won't be able to fix in time for 11.1, but I wanted to point out, since users depending on jumbo frame to/from the guest, are forced to use the e1000, and if there are problems with different guests, there's no more option left for them. Thanks, -harry
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?593F9D13.6040604>