kern/104377: [carp] [patch] CARP interface doesn't go up on VmWare

Antony Mawer fbsd-net at mawer.org
Tue Dec 5 12:29:57 PST 2006


On 5/12/2006 9:48 PM, Gleb Smirnoff wrote:
> On Tue, Dec 05, 2006 at 12:30:27PM +0200, Ari Suutari wrote:
> A> >If interface, that went down, had reported its state then CARP
> A> >would had noticed that and would had lowered its priority, 
> A> >gave up mastering, and became backup. This will be redundant.
> A> 
> A>    Is it impossible to add link state reporting to lnc driver ?
> A>    I think this would be the perfect fix and acceptable by
> A>    everyone.
> 
> You are 100% right :)


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!

Cheers
Antony


More information about the freebsd-net mailing list