Packer: VMWare-iso not connecting to Network

[DanielBo]

I am trying to deploy a CoreOS Image into an ESXi 6.5 Server.

The Issue i am facing is that the Machine is unable to connect to the "VM Network" on the ESXi Server.

Networkdevice says its connected if i set the following: "ethernet0.startConnected": "TRUE"

But if i look into the machines hardware configuration in the ESXi UI it says "connected: false"

As I wasn't able to find a proper documentation on the vmx_data, I manually created a coreOS machine on the Server and exported the configuration. Which leads to a ovf file. Then i converted the ovf file to a VMX Version of said machine and copied the configuration into my json. Linked as "Full Sample"

However this leads to the same behaviour as the reduced version. I provided both as I'm not sure if I'm missing something essential in either configuration.

The ESXi host is in default configuration. To minimize possible Sources of Error i have turned off the firewall of the Server is its not in productive use.

The Machine I used as a template works fine. Created by manually registering a machine on the host using the same image

And I am able to ping google from within the manually created machine. I am unable to do the same from the machine created by packer. I tried to do this by using the ESXi web interface to create a shell on the VM, while packer is waiting for the ssh connection to pop up.

LOG
https://gist.github.com/DanielBo/c2260a668b836ac2b90b448353a066fa

Reduced Sample
https://gist.github.com/DanielBo/cc4b31115a4a83f5ce145c4500e13b71

Full Sample
https://gist.github.com/DanielBo/c86e9d9943595d6d091d78ee4aaf34bf

[delassiops]

Hi,

Add inside "vmx_data"

"ethernet0.networkName": "VM Network",

thanks,

[SwampDragons]

I'm closing because it was never clear on this issue whether it was a usage question or a bug; if you are still trying to get this working, please reach out to our mailing list for help debugging networking.

[hashibot[bot]]

I'm going to lock this issue because it has been closed for _30 days_ ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.