-
Notifications
You must be signed in to change notification settings - Fork 1.4k
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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 Fusion 11 support #976
Comments
This will require me to upgrade my VMware set up (Which is fine) and release a new base box. The current solution should be to downgrade back to a compatible version of VMware. I realize this isn't the best option but I'm not able to affect change here until I return home Friday afternoon. |
Yeah, I downgraded back to version 10 and everything works again. I guess the message for unsupported version should be updated, since version 10 works. |
Thanks for the update. |
@svpernova09 any update on this front? |
No update yet. I've been working on features for the new base box version which will also ship at the same time as a major version bump for Homestead. Both Settler & Homestead releases will be major version bumps since we'll be changing the default PHP version. The next base box version will be v7.0.0 and will be built with the latest version of Fusion at the time. |
Versions
Host operating system
macOS Mojave 10.14.1
Homestead.yaml
Vagrant destroy & up output
Expected behavior
It should be able to run
vagrant up
command and build the VM.Actual behavior
It failed to run because it is saying that the provider only supports VMware Fusion 8 or lower. Just FYI I was successfully running
vmware_fusion
provider with VMware Fusion 10 for quite a while now.Steps to reproduce
The text was updated successfully, but these errors were encountered: