Date: Thu, 7 Dec 2006 09:01:29 +0200 From: "Ari Suutari" <ari.suutari@syncrontech.com> To: "Antony Mawer" <fbsd-net@mawer.org>, "Gleb Smirnoff" <glebius@FreeBSD.org> Cc: net@FreeBSD.org Subject: Re: kern/104377: [carp] [patch] CARP interface doesn't go up on VmWare Message-ID: <010801c719cd$88ee09c0$6602a8c0@sad.syncrontech.com> References: <200612041538.kB4FcQjk073583@freefall.freebsd.org> <0eaa01c71835$f12055f0$6602a8c0@sad.syncrontech.com> <20061205100407.GB32700@cell.sick.ru> <100a01c71858$64b1efc0$6602a8c0@sad.syncrontech.com> <20061205104832.GD32700@cell.sick.ru> <4575D610.702@mawer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi,
>
>
> If you are running VMware 5.x, then you can use the em driver (Intel
> Pro/1000) instead, which is far more functional than the lnc driver. To
> do so:
>
> 1. Shutdown the VMware system
> 2. Locate the *.vmx file for your virtual machine
> 3. Open the *.vmx file in your favourite text editor
> 4. Add the following line:
>
> ethernet0.virtualDev = "e1000"
>
> 5. Save the file, and re-open the VM in VMware
> 6. Enjoy a more functional NIC under VMware!
Great ! I didn't know this. Well, I guess this problem
is solved then.
Thanks,
Ari S.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?010801c719cd$88ee09c0$6602a8c0>