Date: Tue, 6 Aug 2013 07:03:54 +0200 From: Joel Dahl <joel@freebsd.org> To: Bryan Venteicher <bryanv@daemoninthecloset.org> Cc: current@freebsd.org Subject: Re: [CFT] VMware vmxnet3 ethernet driver Message-ID: <20130806050354.GB18861@devbox.vnode.local> In-Reply-To: <1174186801.993.1375743121722.JavaMail.root@daemoninthecloset.org> References: <1050637258.686.1375660230986.JavaMail.root@daemoninthecloset.org> <601099152.721.1375661537866.JavaMail.root@daemoninthecloset.org> <20130805202039.GA18861@devbox.vnode.local> <1174186801.993.1375743121722.JavaMail.root@daemoninthecloset.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Aug 05, 2013 at 05:52:01PM -0500, Bryan Venteicher wrote: > > > ----- Original Message ----- > > I have ~100 FreeBSD 8/9 VMs in my vSphere 5.1 environment, all using the > > VMware tools package from VMware. Everything has been running great for > > years. > > (we skipped vSphere 5.0). Why should I use this vmxnet driver instead of the > > VMware tools driver or the emulated e1000? > > > > They are out of tree and subject to rotting. I had to use the patches > at [1] to even get them to compile on 9.1 and -current. I don't think > VMware puts much engineering resources behind it; Perhaps not, but they do support FreeBSD. I've started several support cases with FreeBSD-specific problems and they've fixed all so far. Are you aiming at completely replacing VMware tools, or just the device drivers? -- Joel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130806050354.GB18861>