2013-09-03 18:08:28 +00:00
---
2016-01-19 18:08:53 +00:00
layout: "docs"
2013-09-06 16:50:43 +00:00
page_title: "Installation - VMware Provider"
2016-01-19 18:08:53 +00:00
sidebar_current: "providers-vmware-installation"
description: |-
The Vagrant VMware provider can be installed using the standard plugin
installation procedure.
2013-09-03 18:08:28 +00:00
---
# Installation
2018-03-23 20:07:07 +00:00
If you are upgrading from the Vagrant VMware Workstation or Vagrant
VMware Fusion plugins, please halt or destroy all VMware VMs currently
being managed by Vagrant. Then continue with the instructions below.
2018-02-20 19:56:40 +00:00
Installation of the Vagrant VMware provider requires two steps. First the
Vagrant VMware Utility must be installed. This can be done by downloading
and installing the correct system package from the [Vagrant VMware Utility
downloads page](/vmware/downloads.html).
2013-09-03 18:08:28 +00:00
2018-02-20 19:56:40 +00:00
Next, install the Vagrant VMware provider plugin using the standard plugin
installation procedure:
2013-09-03 18:08:28 +00:00
2018-02-20 19:56:40 +00:00
```shell
$ vagrant plugin install vagrant-vmware-desktop
2013-09-03 18:08:28 +00:00
```
2015-01-12 17:32:09 +00:00
For more information on plugin installation, please see the
2016-01-19 18:08:53 +00:00
[Vagrant plugin usage documentation ](/docs/plugins/usage.html ).
2015-01-12 17:32:09 +00:00
2018-02-20 19:56:40 +00:00
The Vagrant VMware plugin is a commercial product provided by
2015-01-12 17:32:09 +00:00
[HashiCorp ](https://www.hashicorp.com ) and **require the purchase of a license**
to operate. To purchase a license, please visit the
2016-01-19 18:08:53 +00:00
[Vagrant VMware provider ](/vmware#buy-now ) page. Upon
2015-01-12 17:32:09 +00:00
purchasing a license, you will receive a license file in your inbox. Download
this file and save it to a temporary location on your computer.
2016-01-19 18:08:53 +00:00
< div class = "alert alert-warning" >
2015-01-12 17:32:09 +00:00
< strong > Warning!< / strong > You cannot use your VMware product license as a
Vagrant VMware plugin license. They are separate commercial products, each
requiring their own license.
< / div >
2018-02-20 19:56:40 +00:00
After installing the Vagrant VMware Desktop plugin for your system, you
will need to install the license:
2015-01-12 17:32:09 +00:00
2018-02-20 19:56:40 +00:00
```shell
$ vagrant plugin license vagrant-vmware-desktop ~/license.lic
2015-01-12 17:32:09 +00:00
```
The first parameter is the name of the plugin, and the second parameter is the
path to the license file on disk. Please be sure to replace `~/license.lic`
with the path where you temporarily saved the downloaded license file to disk.
After you have installed the plugin license, you may remove the temporary file.
To verify the license installation, run:
2018-02-20 19:56:40 +00:00
```shell
$ vagrant
2015-01-12 17:32:09 +00:00
```
If the license is not installed correctly, you will see an error message.
2018-03-27 21:58:13 +00:00
## 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
2018-03-27 22:00:19 +00:00
new machine, you may skip this step. If you're a Windows user, you may skip this
step as well.
2018-03-27 21:58:13 +00:00
2018-03-27 22:00:19 +00:00
The path `~/.vagrant.d/gems/*/vagrant-vmware-{fusion,workstation}`
should no longer exist. The gem `vagrant-vmware-desktop` may exist since this
2018-03-27 21:58:13 +00:00
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}
```
2018-03-27 23:51:18 +00:00
## Updating the Vagrant VMware Desktop plugin
The Vagrant VMware Desktop plugin can be updated directly from Vagrant. Run the
following command to update Vagrant to the latest version of the Vagrant VMware
Desktop plugin:
```shell
$ vagrant plugin update vagrant-vmware-desktop
```
2015-01-12 17:32:09 +00:00
## Frequently Asked Questions
2019-01-07 18:52:40 +00:00
**Q: Can Vagrant VMWare Plugin work without internet?**< br >
No, Vagrant VMWare plugin requires a new license every 6 weeks. Vagrant will try to renew the
license automatically. If you are on an environment without internet, after 4 weeks Vagrant will emit a warning,
2019-01-08 19:59:21 +00:00
and after 6 weeks, the VMWare plugin will stop working. You can install a new license to reactive vagrant.
2019-01-07 18:52:40 +00:00
2015-01-12 17:32:09 +00:00
**Q: I purchased a Vagrant VMware plugin license, but I did not receive an email?**< br >
First, please check your JUNK or SPAM folders. Since the license comes from an
automated system, it might have been flagged as spam by your email provider. If
you do not see the email there, please [contact support ](mailto:support@hashicorp.com?subject=License Not Received )
and include the original order number.
**Q: Do I need to keep the Vagrant VMware plugin license file on disk?**< br >
After you have installed the Vagrant VMware plugin license, it is safe to remove
2015-01-12 17:34:40 +00:00
your copy from disk. Vagrant copies the license into its structure for reference
on boot.
2015-01-12 17:32:09 +00:00
**Q: I lost my original email, where can I download my Vagrant VMware plugin license again?**< br >
Please [contact support ](mailto:support@hashicorp.com?subject=Lost My License&body=Hello support! I seem to have misplaced my Vagrant VMware license. Could you please send it to me? Thanks! ). **Note:**
please contact support using the email address with which you made the
original purchase. If you use an alternate email, you will be asked to verify
that you are the owner of the requested license.
**Q: I upgraded my VMware product and now my license is invalid?**< br >
The Vagrant VMware plugin licenses are valid for specific VMware product
versions at the time of purchase. When new versions of VMware products are
released, significant changes to the plugin code are often required to support
this new version. For this reason, you may need to upgrade your current license
to work with the new version of the VMware product. Customers can check their
2018-02-20 19:56:40 +00:00
license upgrade eligibility by visiting the [License Upgrade Center ](https://license.hashicorp.com/upgrade/vmware )
2015-01-12 17:32:09 +00:00
and entering the email address with which they made the original purchase.
Your existing license will continue to work with all previous versions of the
VMware products. If you do not wish to update at this time, you can rollback
your VMware installation to an older version.
**Q: Why is the Vagrant VMware plugin not working with my trial version of VMware Fusion/Workstation?**< br >
The Vagrant VMware Fusion and Vagrant VMware Workstation plugins are not
compatible with trial versions of the VMware products. We apologize for the
inconvenience.
**Q: How do I upgrade my currently installed Vagrant VMware plugin?**< br >
You can update the Vagrant VMware plugin to the latest version by re-running the
2018-02-20 19:56:40 +00:00
install command:
2015-01-12 17:32:09 +00:00
2018-02-20 19:56:40 +00:00
```shell
$ vagrant plugin install vagrant-vmware-desktop
2013-09-03 18:08:28 +00:00
```
2015-01-12 17:32:09 +00:00
## Support
If you have any issues purchasing, installing, or using the Vagrant VMware
2017-03-28 01:19:52 +00:00
plugins, please [contact support ](mailto:support@hashicorp.com ). To
2015-01-12 17:32:09 +00:00
expedite the support process, please include the
2017-03-28 01:19:52 +00:00
[Vagrant debug output ](/docs/other/debugging.html ) as a Gist if
2015-01-12 17:32:09 +00:00
applicable. This will help us more quickly diagnose your issue.