1.4 KiB
| layout | page_title | sidebar_current | description |
|---|---|---|---|
| docs | Known Issues - VMware Provider | providers-vmware-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. |
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.