From owner-freebsd-current@FreeBSD.ORG Thu May 10 20:38:40 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: by hub.freebsd.org (Postfix, from userid 680) id 8D5C816A405; Thu, 10 May 2007 20:38:40 +0000 (UTC) Date: Thu, 10 May 2007 20:38:40 +0000 From: Darren Reed To: Greg Larkin Message-ID: <20070510203840.GA73840@hub.freebsd.org> References: <20070510125445.GA5460@hub.freebsd.org> <001c01c79308$4fae8f90$0901a8c0@TWEETY> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <001c01c79308$4fae8f90$0901a8c0@TWEETY> User-Agent: Mutt/1.4.2.1i X-Mailman-Approved-At: Thu, 10 May 2007 23:27:02 +0000 Cc: 'Robert Watson' , current@freebsd.org Subject: Re: Experiences with 7.0-CURRENT and vmware. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 May 2007 20:38:40 -0000 On Thu, May 10, 2007 at 09:37:03AM -0400, Greg Larkin wrote: > > > But if if_em is probing, it suggests a VMware > > > change rather than a FreeBSD change, which you may be able > > > to revert by > > > telling it to expose a Lance-style device as opposed to an > > > Intel device. > > > > There's no way to choose the type of card vmware emulates. > > > Hi Darren, > > Have you tried modifying the .vmx file after you've created the VM? > For instance, I want to use the em driver with my FreeBSD 6.2 VMs, so > my .vmx file contains these lines: > > Ethernet0.virtualDev = "e1000" > Ethernet1.virtualDev = "e1000" > > I had to change them manually from: > > Ethernet0.virtualDev = "vlance" > Ethernet1.virtualDev = "vlance" > > Perhaps you can force the virtual devices to vlance, if they are not > already configured that way. I didn't know this existed in the .vmx file - there definately isn't a knob in the GUI for it. That said, this is of no help - the vlance device is not available when you're using a 64bit environment (I am), so I'm just going to need to wait for issues with the em driver to be worked out. Thanks for mentioning this. Cheers, Darren