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: "Known Issues - VMware Provider"
|
2016-01-19 18:08:53 +00:00
|
|
|
sidebar_current: "providers-vmware-known-issues"
|
|
|
|
description: |-
|
2018-02-20 19:56:40 +00:00
|
|
|
This page tracks some known issues or limitations of the VMware provider.
|
2016-01-19 18:08:53 +00:00
|
|
|
Note that none of these are generally blockers to using the provider, but
|
|
|
|
are good to know.
|
2013-09-03 18:08:28 +00:00
|
|
|
---
|
|
|
|
|
|
|
|
# Known Issues
|
|
|
|
|
2018-02-20 19:56:40 +00:00
|
|
|
This page tracks some known issues or limitations of the VMware provider.
|
2013-09-03 18:08:28 +00:00
|
|
|
Note that none of these are generally blockers to using the provider, but
|
|
|
|
are good to know.
|
|
|
|
|
2018-02-20 19:56:40 +00:00
|
|
|
## 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.
|
|
|
|
|
2013-09-03 18:08:28 +00:00
|
|
|
## Forwarded Ports Failing in Workstation on Windows
|
|
|
|
|
2016-01-19 18:08:53 +00:00
|
|
|
VMware Workstation has a bug on Windows where forwarded ports do not work
|
2013-09-03 18:08:28 +00:00
|
|
|
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.
|
|
|
|
|
2016-01-19 18:08:53 +00:00
|
|
|
This issue has been reported to VMware, but a fix has not been released yet.
|