Cannot Open VM .vmx File about mech HOT 8 CLOSED

Okay excellent! I imagine we shouldn't overwrite any values if we see that there is any ethernet interface.

from mech.

Looks like this is an issue with VMRun/packer-windows not mech.

from mech.

I would agree, but maybe you can share your VMWare version?

Perhaps there is a config that's not understood?

from mech.

VMWare Fusion 10.0.1

It appears that pulling out:

ethernet0.addresstype=generated
ethernet0.bsdname=en0
ethernet0.connectiontype=nat
ethernet0.displayname=Ethernet
ethernet0.linkstatepropagation.enable=FALSE
ethernet0.pcislotnumber=32
ethernet0.present=TRUE
ethernet0.virtualdev=e1000
ethernet0.wakeonpcktrcv=FALSE

Is allowing VMRun to read it.

from mech.

This may actually be an issue in mech because I believe mech writes that to guarantee there's an interface there.

Can you try adding spaces between the ='s and see if that fixes it?

from mech.

ethernet0.addresstype = generated
ethernet0.bsdname = en0
ethernet0.connectiontype = nat
ethernet0.displayname = Ethernet
ethernet0.linkstatepropagation.enable = FALSE
ethernet0.pcislotnumber = 32
ethernet0.present = TRUE
ethernet0.virtualdev = e1000
ethernet0.wakeonpcktrcv = FALSE

Did not work. I'll continue playing with it as I see what you're talking about.

from mech.

Ok. Switching it to

ethernet1.addresstype=generated
ethernet1.bsdname=en0
ethernet1.connectiontype=nat
ethernet1.displayname=Ethernet
ethernet1.linkstatepropagation.enable=FALSE
ethernet1.pcislotnumber=32
ethernet1.present=TRUE
ethernet1.virtualdev=e1000
ethernet1.wakeonpcktrcv=FALSE

Fixed it as I already had ethernet0 items in my .vmx file.

from mech.

This should be closed by ed10e6f.

Thanks for using mech!

from mech.