How do I specify Network Adapter to be vmxnet3 in Fusion?

[admin]

Hi,

I am runnning a Cent-OS VM in Fusion that won't boot if a vNIC is anything other than vmxnet3.

When I add an adapter through Fusion UI it creates an e1000 type and I can't find a way to modify this.

Guessing I probably need to edit .vmx directly, but I'd like to know exactly what I need to add.

Thanks.

[continuum · Accepted solution]

You now have
ethernet*.virtualDev = "e1000"

possible other settings are
ethernet*.virtualDev = "vlance" - thats the PCnet32
ethernet*.virtualDev = "vmxnet" - thats the old vmxnet-card
ethernet*.virtualDev = "vmxnet3" - thats what you want
ethernet*.virtualDev = "e1000e" - a newer version of the E1000 which uses an PCI-express slot

if you do not specify ethernet*.virtualDev you get the default "vlance"

[WoodyZ]

Wow, it really makes you wonder when a VMware Employee has to ask how to modify a VMware Product!

[continuum]

Thats exactly what I thought ...
Maybe he works in a derpartment where indepth technical insight into the products is regarded as contra-productive ? 

[WoodyZ]

ROFLMAO

[admin]

Lol, fair call... except for a few mitigating factors:

1) I don't work there anymore - they let me go 'cos I couldn't configure Fusion .

2) I tried my old VM colleagues first, and none of them knew either.

3) That suggestion doesn't work - it was the first thing I tried.

[continuum]

... did not work ?
If you changed the vmx while the VM was powered off it should work ...
Can you show us the vmware.log after you changed to vmxnet3 ? - there are a few possible reasons why the change may be ineffective and the log should show why

[admin]

Sorry continuum,

Classic "I have a problem and you should all know what I did" forum posting mistake there

Here's my steps:

Shutdown VM.

Add Adapter.

Quit Fusion.

Edit .vmx and change:

ethernet2.virtualDev = "e1000" to ethernet2.virtualDev = "vmxnet3"

Restart Fusion.

VM now shows as "Loading..." in UI and clicking on 'Settings..' gives an "internal error". Nothing is logged.

**UPDATE**

Okay, my bad - should've known better than to trust my text editor. Followed same steps above using nano instead, and voila!

Cheers continuum kudos coming your way for making me continue troubleshooting my methodology out of sheer embarrassment.

[continuum]

You are welcome
by the way ... your reply:
> 1) I don't work there anymore - they let me go 'cos I couldn't configure Fusion
was good

[NielsGrove]

This also does the trick when working in VMware Workstation (14 Pro) 🙂

[dude64]

It works for me in Workstation 14 too. Anyone test jumbo frame support in Workstation using vmxnet3 yet?

Thanks,

dude64

[MrWonderful1961]

Didn't this exist as a dropdown selection box at some point in VMware Fusion's history??