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
It should not print out warnings if the vmx data is in the vagrant configuration
Actual behavior
What actually happened?
==> wb: Preparing network adapters...
WARNING: The VMX file for this box contains a setting that is automatically overwritten by Vagrant
WARNING: when started. Vagrant will stop overwriting this setting in an upcoming release which may
WARNING: prevent proper networking setup. Below is the detected VMX setting:
WARNING:
WARNING: ethernet0.pcislotnumber = "32"
WARNING:
WARNING: If networking fails to properly configure, it may require this VMX setting. It can be manually
WARNING: applied via the Vagrantfile:
WARNING:
WARNING: Vagrant.configure(2) do |config|
WARNING: config.vm.provider :vmare_fusion do |vmware|
WARNING: vmware.vmx["ethernet0.pcislotnumber"] = "32"
WARNING: end
WARNING: end
WARNING: The VMX file for this box contains a setting that is automatically overwritten by Vagrant
WARNING: when started. Vagrant will stop overwriting this setting in an upcoming release which may
WARNING: prevent proper networking setup. Below is the detected VMX setting:
WARNING:
WARNING: ethernet1.pcislotnumber = "33"
WARNING:
WARNING: If networking fails to properly configure, it may require this VMX setting. It can be manually
WARNING: applied via the Vagrantfile:
WARNING:
WARNING: Vagrant.configure(2) do |config|
WARNING: config.vm.provider :vmare_fusion do |vmware|
WARNING: vmware.vmx["ethernet1.pcislotnumber"] = "33"
WARNING: end
WARNING: end
==> wb: Starting the VMware VM...
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.
ghost
locked and limited conversation to collaborators
Apr 2, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This warning message is very loud and I need a way to silence it to avoid scaring my users.
Vagrant version
1.9.1
vagrant-vmware-fusion plugin version 4.0.18
Host operating system
OS X 10.11
Guest operating system
Ubuntu 14.04
Vagrantfile
Expected behavior
It should not print out warnings if the vmx data is in the vagrant configuration
Actual behavior
What actually happened?
References
Related to #8095
The text was updated successfully, but these errors were encountered: