You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried to create a Linux VM (Fedora) using packer, kickstart and VMware Fusion 12.2 Pro. The Linux VM should run in a separate network vmnet5 I created before in VMware Fusion. After kicking the VM gots an IP address from the NAT network (Share with my Mac). But according to the VM settings the network adapter has been configured to use vmnet5.
When looking into the .vmx file created I saw, that there's a parameter:
ethernet.bsdname=en0
which refers to the main ethernet adapter of the Mac. If I remove this line, the VM booted into the right network.
Reproduction Steps
Create a packer file fedora.json (see below)
Create necessary kickstart files and place them into path
Start packer builder:
PACKER_LOG=1 packer build fedora.json
Wait until VM is up and provides an emergency shell
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.
Overview of the Issue
I tried to create a Linux VM (Fedora) using packer, kickstart and VMware Fusion 12.2 Pro. The Linux VM should run in a separate network
vmnet5
I created before in VMware Fusion. After kicking the VM gots an IP address from the NAT network (Share with my Mac). But according to the VM settings the network adapter has been configured to usevmnet5
.When looking into the .vmx file created I saw, that there's a parameter:
which refers to the main ethernet adapter of the Mac. If I remove this line, the VM booted into the right network.
Reproduction Steps
fedora.json
(see below)ip a
Packer version
packer version
:Simplified Packer Template
Operating system and Environment details
MacOS Big Sur, 11.6
Log Fragments and crash.log files
Log files looked good, packer detected the network:
The text was updated successfully, but these errors were encountered: