-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VMware Workstation 16 does not generate netmap.conf during installation #10009
Comments
Hello, thanks for reaching out! We will take a look once we get a chance. |
Hi @sylviamoss ! Since this isn't a problem with Packer directly, I'm not sure if including more verbose output would actually help here, but let me know if you think otherwise. The problem is that the newest version of VMware Workstation on Linux (and maybe Windows - I haven't tested) doesn't generate a file that Packer requires for building a box. I'm not sure what the ideal fix would be. Maybe ask VMware why this behavior changed, or maybe Packer can somehow dynamically create this file if it doesn't exist? |
Also missing vmnetdhcp conf file as well. I tried doing a touch /etc/vmware/netmap.conf and rerunning packer, but then it complained about vmnetdhcp conf file next. I stopped at that point and reinstalled VMware Workstation 15.5.6 |
Hello there, thanks for opening, I could repro on ubuntu; it looks like this file has moved or no longer exists 🤔 . So yeah in the meantime I'd remain on 15.5 ! |
Hello again, looks like the update process did not recreate that Edit > Virtual Network Editor (type password) > Save. Maybe it's a bug in the vmware installer or updater. |
@azr interesting! I wonder what the equivalent is from the CLI |
|
This worked for me, and now testing on VMware Workstation 16 Pro |
…etworkmapping configuration. Some instances of VMWare will not generate the networkmapping configuration (netmap.conf) at the time of installation. To deal with this issue, we check for the networkmapping file first, and then fallback to the networking file which also might exist and contain the interface information that we require. This fixes issue hashicorp#10009.
…etworkmapping configuration. Some instances of VMWare will not generate the networkmapping configuration (netmap.conf) at the time of installation. To deal with this issue, we check for the networkmapping file first, and then fallback to the networking file which also might exist and contain the interface information that we require. This fixes issue hashicorp#10009.
…etworkmapping configuration. Some instances of VMWare will not generate the networkmapping configuration (netmap.conf) at the time of installation. To deal with this issue, we check for the networkmapping file first, and then fallback to the networking file which also might exist and contain the interface information that we require. This fixes issue hashicorp#10009.
Hey, do you guys see a /etc/vmware/networking file? that looks something like:
Also, do y'all know if the same issue exists on Windows? |
Added a fallback to both the player and workstation drivers from the vmware builder when trying to determine the network-mapping configuration
To test @arizvisa 's fix, you can either retrieve binaries from here: https://app.circleci.com/pipelines/github/hashicorp/packer/9308/workflows/0273bfdc-bd14-4ce9-9069-2fac24ddbfe4/jobs/111047/artifacts or you can build the linked PR locally. Or you can wait until tomorrow's "nightly" release. |
…etworkmapping configuration. Some instances of VMWare will not generate the networkmapping configuration (netmap.conf) at the time of installation. To deal with this issue, we check for the networkmapping file first, and then fallback to the networking file which also might exist and contain the interface information that we require. This fixes issue #10009.
This issue has been automatically migrated to hashicorp/packer-plugin-vmware#4 because it looks like an issue with that plugin. If you believe this is not an issue with the plugin, please reply to hashicorp/packer-plugin-vmware#4. |
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
While not a bug with Packer specifically, Packer relies on this file to build vmware-iso boxes successfully. Beginning with VMware Workstation 16 for Linux, a netmap.conf file is not generated during the installation of VMware
Reproduction Steps
Could not find netmap conf file: /etc/vmware/netmap.conf
error messagePacker version
1.6.3
Simplified Packer Buildfile
https://github.com/clong/DetectionLab/blob/master/Packer/windows_2016.json
Operating system and Environment details
Ubuntu 18.04, x64
Log Fragments and crash.log files
The text was updated successfully, but these errors were encountered: