From owner-freebsd-current@FreeBSD.ORG  Tue Aug  6 05:04:02 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id 94B9628E
 for <current@freebsd.org>; Tue,  6 Aug 2013 05:04:02 +0000 (UTC)
 (envelope-from joel@freebsd.org)
Received: from mail.vnode.se (mail.vnode.se [212.247.52.13])
 by mx1.freebsd.org (Postfix) with ESMTP id 547C62797
 for <current@freebsd.org>; Tue,  6 Aug 2013 05:04:02 +0000 (UTC)
Received: from mail.vnode.se (localhost [127.0.0.1])
 by mail.vnode.se (Postfix) with ESMTP id 3BD65E3F07A;
 Tue,  6 Aug 2013 07:04:00 +0200 (CEST)
X-Virus-Scanned: amavisd-new at vnode.se
Received: from mail.vnode.se ([127.0.0.1])
 by mail.vnode.se (mail.vnode.se [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id B2Js5VfyWuWK; Tue,  6 Aug 2013 07:03:58 +0200 (CEST)
Received: from devbox.vnode.local (unknown [83.223.1.131])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mail.vnode.se (Postfix) with ESMTPSA id E6F31E3F079;
 Tue,  6 Aug 2013 07:03:57 +0200 (CEST)
Date: Tue, 6 Aug 2013 07:03:54 +0200
From: Joel Dahl <joel@freebsd.org>
To: Bryan Venteicher <bryanv@daemoninthecloset.org>
Subject: Re: [CFT] VMware vmxnet3 ethernet driver
Message-ID: <20130806050354.GB18861@devbox.vnode.local>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1174186801.993.1375743121722.JavaMail.root@daemoninthecloset.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: current@freebsd.org
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 05:04:02 -0000

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