haskal
/
vagrant
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Update installation.html.md

This commit is contained in:
Mitchell Hashimoto 2018-03-27 14:58:13 -07:00 committed by GitHub
parent bd4eeb5f4f
commit 5b70ada5d9
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 25 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
website/source/docs/vmware/installation.html.md
View File

@ -61,6 +61,31 @@ $ vagrant
If the license is not installed correctly, you will see an error message.
## Upgrading to v1.x
It is **extremely important** that the VMware plugin is upgraded to 1.0.0 or
above. This release resolved critical security vulnerabilities. To learn more,
please [read our release announcement](https://www.hashicorp.com/blog/introducing-the-vagrant-vmware-desktop-plugin).
After upgrading, please verify that the following paths are empty. The upgrade
process should remove these for you, but for security reasons it is important
to double check. If you're a new user or installing the VMware provider on a
new machine, you may skip this step.
Specifically, the path `~/.vagrant.d/gems/*/vagrant-vmware-{fusion,workstation}`
should no longer exist. The gem `vagrant-vmware-desktop` will exist since this
is the name of the new plugin. If the old directories exist, remove them. An
example for a Unix-like shell is shown below:
```shell
# Check if they exist and verify that they're the correct paths as shown below.
$ ls ~/.vagrant.d/gems/*/vagrant-vmware-{fusion,workstation}
...
# Remove them
$ rm -rf ~/.vagrant.d/gems/*/vagrant-vmware-{fusion,workstation}
```
## Frequently Asked Questions
**Q: I purchased a Vagrant VMware plugin license, but I did not receive an email?**<br>