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
2015-01-12 17:32:09 +00:00
The Vagrant VMware provider can be installed using the standard plugin
installation procedure. VMware Fusion users should run:
2013-09-03 18:08:28 +00:00
2015-01-12 17:32:09 +00:00
```text
$ vagrant plugin install vagrant-vmware-fusion
```
2013-09-03 18:08:28 +00:00
2015-01-12 17:32:09 +00:00
VMware Workstation users should run:
2013-09-03 18:08:28 +00:00
2015-01-12 17:32:09 +00:00
```text
$ vagrant plugin install vagrant-vmware-workstation
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
The Vagrant VMware plugins are commercial products provided by
[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 >
After installing the correct Vagrant VMware product plugin for your system, you
will need to install the license. For VMware Fusion users:
```text
$ vagrant plugin license vagrant-vmware-fusion ~/license.lic
```
For VMware Workstation users:
```text
$ vagrant plugin license vagrant-vmware-workstation ~/license.lic
```
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:
```text
$ vagrant plugin list
```
If the license is not installed correctly, you will see an error message.
## Frequently Asked Questions
**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
2015-08-25 16:41:53 +00:00
license upgrade eligibility by visiting the [License Upgrade Center ](http://license.hashicorp.com/upgrade/vmware2015 )
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: I accidentally bought the wrong Vagrant VMware plugin, can I switch?**< br >
Sure! Even though the Vagrant VMware Fusion plugin and the Vagrant VMware
Workstation plugin are different products, they are the same price and fall
under the same EULA. As such, we can transfer the license for you. Please
[contact support ](mailto:support@hashicorp.com?subject=Transfer License ).
**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
install command. For VMware Fusion:
```text
2013-09-03 18:08:28 +00:00
$ vagrant plugin install vagrant-vmware-fusion
```
2015-01-12 17:32:09 +00:00
For VMWare Workstation:
```text
$ vagrant plugin install vagrant-vmware-workstation
```
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
2016-01-19 18:08:53 +00:00
plugins, please [contact support ](/support.html ). To
2015-01-12 17:32:09 +00:00
expedite the support process, please include the
2016-01-19 18:08:53 +00:00
[Vagrant debug output ](/docs/other/debugging.html ) as a Gist or pastebin if
2015-01-12 17:32:09 +00:00
applicable. This will help us more quickly diagnose your issue.