Open mjturner opened 6 years ago
I am also experiencing this issue.
Hello
Vagrant will check on the default path for the installer, this is by design.
We will be updating the documentation to reflect this.
Basically the installer goes to /Applications, and the plugin check there.
I've upgraded Vagrant to 2.0.0, the vagrant-vmware-fusion plugin to 5.0.1 and VMware Fusion to 10.x and Vagrant can no longer find VMware as it's not installed in /Applications. It appears as if the VAGRANT_VMWARE_FUSION_APP environment variable is being ignored. Earlier versions of the plugin also displayed a more meaningful error message indicating that VMware couldn't be found.
My configuration worked fine with Vagrant < 2.0 and VMware 8.x.
Vagrant version
Vagrant 2.0.0 (vagrant-vmware-fusion 5.0.1 plugin)
Host operating system
macOS 10.12.6
Guest operating system
N/A
Vagrantfile
N/A
Debug output
https://gist.github.com/mjturner/a33bb93e41853d85da6f0514eec2da33
Expected behavior
Vagrant should start
Actual behavior
Running
vagrant
displays the following error is displayed:Reinstalling the plugin doesn't solve the issue.
Debug output shows the following line:
I have the $VAGRANT_VMWARE_FUSION_APP environment variable set:
The same setup worked with earlier versions of Vagrant and the VMware Fusion Plugin (and is still documented as supported). Creating a symlink into
/Applications
solves the issue and Vagrant runs as normal.Steps to reproduce
/Applications
VAGRANT_VMWARE_FUSION_APP
environment variable as per the Vagrant documentation.vagrant
References