MacOS Big Sur / VMWare Fusion / DHCPD Leases / Mac Address Wrong?

[ekristen]

I couldn't find a better place to ask the question or bring up the issue ...

On cloned vmx of windows 10, the ethernet adapter gets a "generated" mac address from packer and it gets a "generated" if you manually create a full clone.

In both cases the VM gets an IP from the MacOS DHCPD instance and you can see the lease in the /var/db/dhcpd_leases file BUT the mac address is just wrong.

Examples:

• cloned via vmware fusion UI
  • host reports 00:0c:29:50:da:5e / 192.168.12.29
  • vmware reports 0:c:29:5:e5:6e (short form) / 192.168.12.29

After my 30+ testing this, it suddenly started working, and I'm not sure why. Anyone have a theory or know why this behavior exists. It doesn't appear to be packer specific, but given packer is one of the primary programmatic ways to interact with fusion, I suspect people here would have see it or would know how to troubleshoot.

[tenthirtyam]

cc @nywilken @lbajolet-hashicorp for transfer

[lbajolet-hashicorp]

Transferring now, it seems this is a duplicate of https://github.com/hashicorp/packer-plugin-vmware/issues/185 though?

[tenthirtyam]

Duplicate of #109