vagrant-packet 0.1.2 → 0.1.3

data/vendor/bundle/ruby/2.4.0/bundler/gems/vagrant-04f7215b5e3f/website/source/docs/virtualbox/networking.html.md

@@ -1,58 +0,0 @@
----
-layout: "docs"
-page_title: "Networking - VirtualBox Provider"
-sidebar_current: "providers-virtualbox-networking"
-description: |-
-  The Vagrant VirtualBox provider supports using the private network as a
-  VirtualBox internal network. By default, private networks are host-only
-  networks, because those are the easiest to work with.
----
-
-# Networking
-
-## VirtualBox Internal Network
-
-The Vagrant VirtualBox provider supports using the private network as a
-VirtualBox [internal network](https://www.virtualbox.org/manual/ch06.html#network_internal).
-By default, private networks are host-only networks, because those are the
-easiest to work with. However, internal networks can be enabled as well.
-
-To specify a private network as an internal network for VirtualBox
-use the `virtualbox__intnet` option with the network. The `virtualbox__`
-(double underscore) prefix tells Vagrant that this option is only for the
-VirtualBox provider.
-
-```ruby
-Vagrant.configure("2") do |config|
-  config.vm.network "private_network", ip: "192.168.50.4",
-    virtualbox__intnet: true
-end
-```
-
-Additionally, if you want to specify that the VirtualBox provider join
-a specific internal network, specify the name of the internal network:
-
-```ruby
-Vagrant.configure("2") do |config|
-  config.vm.network "private_network", ip: "192.168.50.4",
-    virtualbox__intnet: "mynetwork"
-end
-```
-
-## VirtualBox NIC Type
-
-You can specify a specific NIC type for the created network interface
-by using the `nic_type` parameter. This is not prefixed by `virtualbox__`
-for legacy reasons, but is VirtualBox-specific.
-
-This is an advanced option and should only be used if you know what
-you are using, since it can cause the network device to not work at all.
-
-Example:
-
-```ruby
-Vagrant.configure("2") do |config|
-  config.vm.network "private_network", ip: "192.168.50.4",
-    nic_type: "virtio"
-end
-```

data/vendor/bundle/ruby/2.4.0/bundler/gems/vagrant-04f7215b5e3f/website/source/docs/virtualbox/usage.html.md

@@ -1,19 +0,0 @@
----
-layout: "docs"
-page_title: "Usage - VirtualBox Provider"
-sidebar_current: "providers-virtualbox-usage"
-description: |-
-  The Vagrant VirtualBox provider is used just like any other provider. Please
-  read the general basic usage page for providers.
----
-
-# Usage
-
-The Vagrant VirtualBox provider is used just like any other provider. Please
-read the general [basic usage](/docs/providers/basic_usage.html) page for
-providers.
-
-The value to use for the `--provider` flag is `virtualbox`.
-
-The Vagrant VirtualBox provider does not support parallel execution at this
-time. Specifying the `--parallel` option will have no effect.

data/vendor/bundle/ruby/2.4.0/bundler/gems/vagrant-04f7215b5e3f/website/source/docs/vmware/boxes.html.md

@@ -1,148 +0,0 @@
----
-layout: "docs"
-page_title: "Box Format - VMware Provider"
-sidebar_current: "providers-vmware-boxes"
-description: |-
-  As with every Vagrant provider, the Vagrant VMware providers have a custom box
-  format.
----
-
-# Boxes
-
-As with [every Vagrant provider](/docs/providers/basic_usage.html), the
-Vagrant VMware providers have a custom box format.
-
-This page documents the format so that you can create your own base boxes.
-Note that currently you must make these base boxes by hand. A future release
-of Vagrant will provide additional mechanisms for automatically creating such
-images.
-
-<div class="alert alert-info">
-  <strong>Note:</strong> This is a reasonably advanced topic that
-  a beginning user of Vagrant does not need to understand. If you are
-  just getting started with Vagrant, skip this and use an available
-  box. If you are an experienced user of Vagrant and want to create
-  your own custom boxes, this is for you.
-</div>
-
-Prior to reading this page, please understand the
-[basics of the box file format](/docs/boxes/format.html).
-
-## Contents
-
-A VMware base box is a compressed archive of the necessary contents
-of a VMware "vmwarevm" file. Here is an example of what is contained
-in such a box:
-
-```
-$ tree
-.
-|-- disk-s001.vmdk
-|-- disk-s002.vmdk
-|-- ...
-|-- disk.vmdk
-|-- metadata.json
-|-- precise64.nvram
-|-- precise64.vmsd
-|-- precise64.vmx
-|-- precise64.vmxf
-
-0 directories, 17 files
-```
-
-The files that are strictly required for a VMware machine to function are:
-nvram, vmsd, vmx, vmxf, and vmdk files.
-
-There is also the "metadata.json" file used by Vagrant itself. This file
-contains nothing but the defaults which are documented on the
-[box format](/docs/boxes/format.html) page.
-
-When bringing up a VMware backed machine, Vagrant copies all of the contents
-in the box into a privately managed "vmwarevm" folder, and uses the first
-"vmx" file found to control the machine.
-
-<div class="alert alert-info">
-  <strong>Vagrant 1.8 and higher support linked clones</strong>. Prior versions
-  of Vagrant do not support linked clones. For more information on
-  linked clones, please see the documentation.
-</div>
-
-## VMX Whitelisting
-
-Settings in the VMX file control the behavior of the VMware virtual machine
-when it is booted. In the past Vagrant has removed the configured network
-device when creating a new instance and inserted a new configuration. With
-the introduction of ["predictable network interface names"][iface-names] this
-approach can cause unexpected behaviors or errors with VMware Vagrant boxes.
-While some boxes that use the predictable network interface names are configured
-to handle the VMX modifications Vagrant makes, it is better if Vagrant does
-not make the modification at all.
-
-Vagrant will now warn if a whitelisted setting is detected within a Vagrant
-box VMX file. If it is detected, a warning will be shown alerting the user
-and providing a configuration snippet. The configuration snippet can be
-used in the Vagrantfile if Vagrant fails to start the virtual machine.
-
-### Making compatible boxes
-
-These are the VMX settings the whitelisting applies to:
-
-* `ethernet*.pcislotnumber`
-
-If the newly created box does not depend on Vagrant's existing behavior of
-modifying this setting, it can disable Vagrant from applying the modification
-by adding a Vagrantfile to the box with the following content:
-
-```ruby
-Vagrant.configure("2") do |config|
-  ["vmware_workstation", "vmware_fusion"].each do |vmware_provider|
-    config.vm.provider(vmware_provider) do |vmware|
-      vmware.whitelist_verified = true
-    end
-  end
-end
-```
-
-This will prevent Vagrant from displaying a warning to the user as well as
-disable the VMX settings modifications.
-
-## Installed Software
-
-Base boxes for VMware should have the following software installed, as
-a bare minimum:
-
-* SSH server with key-based authentication setup. If you want the box to
-  work with default Vagrant settings, the SSH user must be set to accept
-  the [insecure keypair](https://github.com/hashicorp/vagrant/blob/master/keys/vagrant.pub)
-  that ships with Vagrant.
-
-* [VMware Tools](https://kb.vmware.com/kb/340) so that things such as shared
-  folders can function. There are many other benefits to installing the tools,
-  such as improved networking performance.
-
-## Optimizing Box Size
-
-Prior to packaging up a box, you should shrink the hard drives as much as
-possible. This can be done with `vmware-vdiskmanager` which is usually
-found in `/Applications/VMware Fusion.app/Contents/Library` for VMware Fusion. You first
-want to defragment then shrink the drive. Usage shown below:
-
-```
-$ vmware-vdiskmanager -d /path/to/main.vmdk
-...
-$ vmware-vdiskmanager -k /path/to/main.vmdk
-...
-```
-
-## Packaging
-
-Remove any extraneous files from the "vmwarevm" folder
-and package it. Be sure to compress the tar with gzip (done below in a
-single command) since VMware hard disks are not compressed by default.
-
-```
-$ cd /path/to/my/vm.vmwarevm
-$ tar cvzf custom.box ./*
-```
-
-[iface-names]: https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/

data/vendor/bundle/ruby/2.4.0/bundler/gems/vagrant-04f7215b5e3f/website/source/docs/vmware/configuration.html.md

@@ -1,124 +0,0 @@
----
-layout: "docs"
-page_title: "Configuration- VMware Provider"
-sidebar_current: "providers-vmware-configuration"
-description: |-
-  While Vagrant VMware providers are a drop-in replacement for VirtualBox, there
-  are some additional features that are exposed that allow you to more finely
-  configure VMware-specific aspects of your machines.
----
-
-# Configuration
-
-While Vagrant VMware Desktop provider is a drop-in replacement for VirtualBox, there
-are some additional features that are exposed that allow you to more finely
-configure VMware-specific aspects of your machines.
-
-Configuration settings for the provider are set in the Vagrantfile:
-
-```ruby
-Vagrant.configure("2") do |config|
-  config.vm.box = "my-box"
-  config.vm.provider "vmware_desktop" do |v|
-    v.gui = true
-  end
-end
-```
-
-## Provider settings
-
-* `clone_directory` (string) - Path for storing VMware clones. This value can
-  also be set using the `VAGRANT_VMWARE_CLONE_DIRECTORY` environment variable.
-  This defaults to `./.vagrant`
-* `enable_vmrun_ip_lookup` (bool) - Use vmrun to discover guest IP address.
-  This defaults to `true`
-* `functional_hgfs` (bool) - HGFS is functional within the guest.
-  This defaults to detected capability of the guest
-* `unmount_default_hgfs` (bool) - Unmount the default HGFS mount point within the guest.
-  This defaults to `false`
-* `gui` (bool) - Launch guest with a GUI.
-  This defaults to `false`
-* `ssh_info_public` (bool) - Use the public IP address for SSH connections to guest.
-  This defaults to `false`
-* `verify_vmnet` (bool) - Verify vmnet devices health before usage.
-  This defaults to `true`
-* `linked_clone` (bool) - Use linked clones instead of full copy clones.
-  This defaults to `true`
-* `vmx` (hash) - VMX key/value pairs to set or unset. If the value is `nil`, the key will
-  be deleted.
-* `whitelist_verified` (bool, symbol) - Flag that VMware box has been properly configured
-  for whitelisted VMX settings. `true` if verified, `false` if unverified, `:disable_warning`
-  to silence whitelist warnings.
-* `port_forward_network_pause` - Number of seconds to pause after applying port forwarding
-  configuration. This allows guest time to acquire DHCP address if previous address is
-  dropped when VMware network services are restarted.
-  This defaults to `0`
-* `utility_port` (integer) - Listen port of the Vagrant VMware Utility service.
-  This defaults to `9922`
-* `utility_certificate_path` (string) - Path to the Vagrant VMware Utility service
-  certificates directory.
-  The default value is dependent on the host
-
-### VM Clone Directory
-
-By default, the VMware provider will clone the VMware VM in the box
-to the ".vagrant" folder relative to the folder where the Vagrantfile is.
-Usually, this is fine. For some people, for example those who use a
-differential backup software such as Time Machine, this is very annoying
-because you cannot regularly ignore giant virtual machines as part of backups.
-
-The directory where the provider clones the virtual machine can be
-customized by setting the `VAGRANT_VMWARE_CLONE_DIRECTORY` environmental
-variable. This does not need to be unique per project. Each project will
-get a different sub-directory within this folder. Therefore, it is safe to
-set this systemwide.
-
-### Linked Clones
-
-By default new machines are created using a linked clone to the base
-box. This reduces the time and required disk space incurred by directly
-importing the base box.
-
-Linked clones are based on a master VM, which is generated by importing the
-base box only once the first time it is required. For the linked clones only
-differencing disk images are created where the parent disk image belongs to
-the master VM. To disable linked clones:
-
-```ruby
-config.vm.provider "vmware_desktop" do |v|
-  v.linked_clone = false
-end
-```
-
-### VMX Customization
-
-If you want to add or remove specific keys from the VMX file, you can do
-that:
-
-```ruby
-config.vm.provider "vmware_desktop" do |v|
-  v.vmx["custom-key"]  = "value"
-  v.vmx["another-key"] = nil
-end
-```
-
-In the example above, the "custom-key" key will be set to "value" and the
-"another-key" key will be removed from the VMX file.
-
-VMX customization is done as the final step before the VMware machine is
-booted, so you have the ability to possibly undo or misconfigure things
-that Vagrant has set up itself.
-
-VMX is an undocumented format and there is no official reference for
-the available keys and values. This customization option is exposed for
-people who have knowledge of exactly what they want.
-
-The most common keys people look for are setting memory and CPUs.
-The example below sets both:
-
-```ruby
-config.vm.provider "vmware_desktop" do |v|
-  v.vmx["memsize"] = "1024"
-  v.vmx["numvcpus"] = "2"
-end
-```

data/vendor/bundle/ruby/2.4.0/bundler/gems/vagrant-04f7215b5e3f/website/source/docs/vmware/index.html.md

@@ -1,37 +0,0 @@
----
-layout: "docs"
-page_title: "VMware Provider"
-sidebar_current: "providers-vmware"
-description: |-
-  HashiCorp develops an official VMware Fusion and VMware Workstation provider
-  for Vagrant. This provider allows Vagrant to power VMware based machines and
-  take advantage of the improved stability and performance that VMware software
-  offers.
----
-
-# VMware
-
-[HashiCorp](https://www.hashicorp.com) develops an official
-[VMware Fusion](https://www.vmware.com/products/fusion/overview.html)
-and [VMware Workstation](https://www.vmware.com/products/workstation/) 
-[provider](/docs/providers/) for Vagrant. This provider allows
-Vagrant to power VMware based machines and take advantage of the
-improved stability and performance that VMware software offers.
-
-Learn more about the VMware providers on the
-[VMware provider](/vmware) page on
-the Vagrant website.
-
-This provider is a drop-in replacement for VirtualBox, meaning that every
-VirtualBox feature that Vagrant supports is fully functional in VMware as
-well. However, there are some VMware-specific things such as box formats,
-configurations, etc. that are documented here.
-
-For the most up-to-date information on compatibility and supported versions of
-VMware Fusion and VMware Workstation, please visit the
-[Vagrant VMware product page](/vmware). Please note
-that VMware Fusion and VMware Workstation are third-party products that must be
-purchased and installed separately prior to using the provider.
-
-Use the navigation to the left to find a specific VMware topic to read
-more about.

data/vendor/bundle/ruby/2.4.0/bundler/gems/vagrant-04f7215b5e3f/website/source/docs/vmware/installation.html.md

@@ -1,150 +0,0 @@
----
-layout: "docs"
-page_title: "Installation - VMware Provider"
-sidebar_current: "providers-vmware-installation"
-description: |-
-  The Vagrant VMware provider can be installed using the standard plugin
-  installation procedure.
----
-
-# Installation
-
-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.
-
-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).
-
-Next, install the Vagrant VMware provider plugin using the standard plugin
-installation procedure:
-
-```shell
-$ vagrant plugin install vagrant-vmware-desktop
-```
-
-For more information on plugin installation, please see the
-[Vagrant plugin usage documentation](/docs/plugins/usage.html).
-
-The Vagrant VMware plugin is a commercial product provided by
-[HashiCorp](https://www.hashicorp.com) and **require the purchase of a license**
-to operate. To purchase a license, please visit the
-[Vagrant VMware provider](/vmware#buy-now) page. Upon
-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.
-
-<div class="alert alert-warning">
-  <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 Vagrant VMware Desktop plugin for your system, you
-will need to install the license:
-
-```shell
-$ vagrant plugin license vagrant-vmware-desktop ~/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:
-
-```shell
-$ 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. If you're a Windows user, you may skip this
-step as well.
-
-The path `~/.vagrant.d/gems/*/vagrant-vmware-{fusion,workstation}`
-should no longer exist. The gem `vagrant-vmware-desktop` may 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}
-```
-
-## 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
-```
-
-## 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
-your copy from disk. Vagrant copies the license into its structure for reference
-on boot.
-
-**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
-license upgrade eligibility by visiting the [License Upgrade Center](https://license.hashicorp.com/upgrade/vmware)
-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
-install command:
-
-```shell
-$ vagrant plugin install vagrant-vmware-desktop
-```
-
-## Support
-If you have any issues purchasing, installing, or using the Vagrant VMware
-plugins, please [contact support](mailto:support@hashicorp.com). To
-expedite the support process, please include the
-[Vagrant debug output](/docs/other/debugging.html) as a Gist if
-applicable. This will help us more quickly diagnose your issue.

data/vendor/bundle/ruby/2.4.0/bundler/gems/vagrant-04f7215b5e3f/website/source/docs/vmware/kernel-upgrade.html.md

@@ -1,61 +0,0 @@
----
-layout: "docs"
-page_title: "Kernel Upgrade - VMware Provider"
-sidebar_current: "providers-vmware-kernel-upgrade"
-description: |-
-  If as part of running your Vagrant environment with VMware, you perform
-  a kernel upgrade, it is likely that the VMware guest tools will stop working.
-  This breaks features of Vagrant such as synced folders and sometimes
-  networking as well.
----
-
-# Kernel Upgrade
-
-If as part of running your Vagrant environment with VMware, you perform
-a kernel upgrade, it is likely that the VMware guest tools will stop working.
-This breaks features of Vagrant such as synced folders and sometimes
-networking as well.
-
-This page documents how to upgrade your kernel and keep your guest tools
-functioning. If you are not planning to upgrade your kernel, then you can safely
-skip this page.
-
-## Enable Auto-Upgrade of VMware Tools
-
-If you are running a common OS, VMware tools can often auto-upgrade themselves.
-This setting is disabled by default. The Vagrantfile settings below will
-enable auto-upgrading:
-
-```ruby
-# Ensure that VMWare Tools recompiles kernel modules
-# when we update the linux images
-$fix_vmware_tools_script = <<SCRIPT
-sed -i.bak 's/answer AUTO_KMODS_ENABLED_ANSWER no/answer AUTO_KMODS_ENABLED_ANSWER yes/g' /etc/vmware-tools/locations
-sed -i 's/answer AUTO_KMODS_ENABLED no/answer AUTO_KMODS_ENABLED yes/g' /etc/vmware-tools/locations
-SCRIPT
-
-Vagrant.configure("2") do |config|
-  # ...
-
-  config.vm.provision "shell", inline: $fix_vmware_tools_script
-end
-```
-
-Note that this does not work for every OS, so `vagrant up` with the above
-settings, do a kernel upgrade, and do a `vagrant reload`. If HGFS (synced
-folders) and everything appears to be working, great! If not, then read on...
-
-## Manually Reinstalling VMware Tools
-
-At this point, you will have to manually reinstall VMware tools. The best
-source of information for how to do this is the
-[VMware documentation](https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1018414).
-
-There are some gotchas:
-
-  * Make sure you have the kernel headers properly installed. This varies
-    by distro but is generally a package available via the package manager.
-
-  * Watch the installation output carefully. Even if HGFS (synced folders)
-    support failed to build, the installer will output that installing VMware
-    tools was successful. Read the output to find any error messages.

data/vendor/bundle/ruby/2.4.0/bundler/gems/vagrant-04f7215b5e3f/website/source/docs/vmware/known-issues.html.md

@@ -1,35 +0,0 @@
----
-layout: "docs"
-page_title: "Known Issues - VMware Provider"
-sidebar_current: "providers-vmware-known-issues"
-description: |-
-  This page tracks some known issues or limitations of the VMware provider.
-  Note that none of these are generally blockers to using the provider, but
-  are good to know.
----
-
-# Known Issues
-
-This page tracks some known issues or limitations of the VMware provider.
-Note that none of these are generally blockers to using the provider, but
-are good to know.
-
-## Network disconnect
-
-When Vagrant applies port forwarding rules while bring up a guest instance,
-other running VMware VMs may experience a loss of network connectivity. The
-cause of this connectivity issue is the restarting of the VMware NAT service
-to apply new port forwarding rules. Since new rules cannot be applied to the
-NAT service while it is running, it is required to restart the service, which
-results in the loss of connectivity.
-
-## Forwarded Ports Failing in Workstation on Windows
-
-VMware Workstation has a bug on Windows where forwarded ports do not work
-properly. Vagrant actually works around this bug and makes them work. However,
-if you run the virtual network editor on Windows, the forwarded ports will
-suddenly stop working.
-
-In this case, run `vagrant reload` and things will begin working again.
-
-This issue has been reported to VMware, but a fix has not been released yet.

data/vendor/bundle/ruby/2.4.0/bundler/gems/vagrant-04f7215b5e3f/website/source/docs/vmware/usage.html.md

@@ -1,39 +0,0 @@
----
-layout: "docs"
-page_title: "Usage - VMware Provider"
-sidebar_current: "providers-vmware-usage"
-description: |-
-  The Vagrant VMware providers are used just like any other provider. Please
-  read the general basic usage page for providers.
----
-
-# Usage
-
-The Vagrant VMware provider is used just like any other provider. Please
-read the general [basic usage](/docs/providers/basic_usage.html) page for
-providers.
-
-The value to use for the `--provider` flag is `vmware_desktop`. For compatibility
-with older versions of the plugin, `vmware_fusion` can be used for VMware
-Fusion, and `vmware_workstation` for VMware Workstation.
-
-The Vagrant VMware provider does not support parallel execution at this time.
-Specifying the `--parallel` option will have no effect.
-
-To get started, create a new `Vagrantfile` that points to a VMware box:
-
-```ruby
-# vagrant init hashicorp/precise64
-Vagrant.configure("2") do |config|
-  config.vm.box = "hashicorp/precise64"
-end
-```
-
-Then run:
-
-```shell
-$ vagrant up --provider vmware_desktop
-```
-
-This will download and bring up a new VMware Fusion/Workstation virtual machine
-in Vagrant.