cannot permanently change config file

[louis14]

I use vmware workstation pro 12 and a guest windows 10. I use this in combination with gns3: a network emulation program.(the windows 10 vm is connected to a switch and router emulation)

If I start the windows 10 guest in my gns3 and I look to the vm in vmware: in device manager of windows 10 is the ethernet controller under "other devices" and the driver is not installed.

And there is no ethernet adapter in control panel->network->adapter

In settings of vmware after booting windows 10 is the network adapter "custom vmnet2"

To get the infrastructure working I must remove the ethernet controller in device manager.Shut down windows 10.Edit the windows 10 vmware config file: add a line:

ethernet0.virtualDev = "e1000"

restart windows 10 and then there is a working network adapter in control panel-network->adapter

But after the restart vmware has removed the line I added to the config file which means when I reboot the windows 10 guest: again : the adapter is removed in control panel

How can I prevent that vmware removes that line?

[sjesse]

Make sure vmware tools is installed, but also remove the network controller in workstation and re add it there, windows should see a new network adapter and install the correct drivers. The e1000 drivers I think are in windows by default so something is weird with that network adapter I believe.

[continuum]

Please show us the freshly edited vmx-file - and for comparison show the version that it gets reverted to.
looks like you use some invalid entries ....

[towo2099]

Only shutting down the vm is not enougth. As long, as the VMware application is running with the vm loaded in the gui, all manual edit in the vmx file is useless.

[yanw]

For Win10 Guest, VMware Workstation should use e1000e as the default vNic type and the e1000/e1000e driver should be proviced by the Windows system, make sure that your Win10 guest has such network drivers bundled.

If you want to edit and save the vmx configuration, make sure that there is no .lck file in the VM's folder.

[louis14]

Hi thanks for your answers.

I have closed my vmware application before editing my config file of my windows 10 guest and again after starting my vmware guest: the line I added (ethernet0.virtualDev = "e1000") was removed from my config file which means after my next reboot of my guest my network adapter disappaered.

There was no lck file in the directory of the vm gust when I edited the config file.

I add the edited config (config1) file and the reverted (config2) config file after booting the guest.

[louis14]

The network adapter on the windows 10 guest is (after adding the line) : intel (R) Pro/1000 MT

[wila]

Hi,

It's not removed, it is in a different location (check out line 104)

You only added a line with ethernet0.virtualDev, while VMware Workstation needs to have more ethernet0 settings for that to work.

At line 104 I see this:

ethernet0.virtualdev = "e1000"

ethernet0.addresstype = "generated"

ethernet0.present = "TRUE"

ethernet0.generatedaddressoffset = "0"

ethernet0.connectiontype = "custom"

ethernet0.vnet = "VMnet2"

ethernet0.pciSlotNumber = "37"

ethernet0.generatedAddress = "00:0c:29:1f:3b:d6"

So it's there, just not at the end of the file anymore.

--

Wil

[louis14]

Thank you wil,

I used "search" function in notebook but with "up" instead of "down", that was the cause I did not find "e1000".

My config3 config file is the file I used after the shutdown of my windows 10 guest.

Now it seems after the shutdown, vmware has removed all the "ethernet" lines.

config3 must be the same as config1.

[louis14]

The cause of the removal is the application gns3.

I can shutdown the guest in the application gns3 and I can shutdown the guest in vmware itself.

When I shutdown the guest in vmware itself: the ethernet lines are still there but when I then stop the guest in gns3 (which is infact already stopped, but not yet in gns3) the ethernet lines are removed from the config file.

The normal way is: only click "stop" in gns3: which shuts down the guest in vmware.

[wila]

Sounds like gns3 is keeping an old incorrect cached version of your vmx file then and overwrites the original vmx when you stop.

Not sure why they decided to do that, sounds a bit funky to me.

--

Wil