Date: Sat, 12 May 2007 11:47:25 -0700 From: Bert JW Regeer <xistence@0x58.com> To: Darren Reed <darrenr@hub.freebsd.org>, current@freebsd.org, hackers@freebsd.org Subject: Re: Experiences with 7.0-CURRENT and vmware. Message-ID: <D776CEB1-3073-468C-87F6-B85A821D9E9A@0x58.com> In-Reply-To: <20070510125445.GA5460@hub.freebsd.org> References: <20070510111326.GA94093@hub.freebsd.org> <20070510132153.A91312@fledge.watson.org> <20070510125445.GA5460@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail-5-972466620 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed On May 10, 2007, at 5:54 AM, Darren Reed 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. > I always set my VMWare to expose an intel e1000 card, which gets probed correctly by almost all systems, even Windows with the Intel drivers installed. In your .vmx file you should find a line like this: ethernet0.virtualDev="e1000" If VMWare is to give an em device, if you remove that line it should default back to lnc driver. That being said, I have had no performance problems with the em driver on FreeBSD 6.0 in VMWare, and have not had the timeout problems you mentioned. > Darren Bert JW Regeer --Apple-Mail-5-972466620--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D776CEB1-3073-468C-87F6-B85A821D9E9A>