dortania/macOS-VMware-Guide

Cannot run after changing ethernet address

tylerwolf35 opened this issue · 12 comments

I can not start the VM after changing the MAC address. I get the following error.

Error while powering on: Specify a static Ethernet address for 'ethernet0'.

Could not set up 'macAddress' for 'ethernet0'.

Module 'DevicePowerOn' power on failed.

Failed to start the virtual machine.

I am unsure how to fix this, I have tried multiple different MAC addresses from the site but have not had any luck.

Could you upload screenshots of those lines you edited from your .vmx file

Could you upload screenshots of those lines you edited from your .vmx file

1
2

You need to change "ethernet0.generatedAddress" to "ethernet0.Address". You also need to change "ethernet0.generatedAddressOffset" to "ethernet0.checkMACAddress"

You need to change "ethernet0.generatedAddress" to "ethernet0.Address". You also need to change "ethernet0.generatedAddressOffset" to "ethernet0.checkMACAddress"

Now I get the following error once booting the machine.
error

Boot to the macOS installer and run this command in Terminal nvram boot-args="-v"

Boot to the macOS installer and run this command in Terminal nvram boot-args="-v"

I am getting the same error. I am now redownloading the disk file and will try from there.

Boot to the macOS installer and run this command in Terminal nvram boot-args="-v"

I am getting the same error. I am now redownloading the disk file and will try from there.

I got the same error again with a fresh vmdk file.

Same error as: https://user-images.githubusercontent.com/47761974/108008580-ad843180-6fce-11eb-9f80-9c16743c5fbb.png
or a different error?
If it's different, upload a photo

Same error, I was able to revert the vmx file and login and ran the command and generated new values in the Clover Configurator, I have updated the file and have the same problem. At first it appears it will boot and then it reverts back to the vmware bootup screen and then I get the same error.
error

Also, in case it matters as I cannot use VirtualBox due to it I have Hyper-V enabled.

I appear to have fixed this by disabling Hyper-V.

Was just about to write the same thing. I will mark this issue as closed