From 754bbf7a25a8dda49b5d08ef0d0443bbf5af0e36 Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Sun, 7 Apr 2024 13:41:34 -0500 Subject: new repository --- devdocs/vagrant/vmware%2Fknown-issues.html | 6 ++++++ 1 file changed, 6 insertions(+) create mode 100644 devdocs/vagrant/vmware%2Fknown-issues.html (limited to 'devdocs/vagrant/vmware%2Fknown-issues.html') diff --git a/devdocs/vagrant/vmware%2Fknown-issues.html b/devdocs/vagrant/vmware%2Fknown-issues.html new file mode 100644 index 00000000..ee179d50 --- /dev/null +++ b/devdocs/vagrant/vmware%2Fknown-issues.html @@ -0,0 +1,6 @@ +

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.

+

+ © 2010–2018 Mitchell Hashimoto
Licensed under the MPL 2.0 License.
+ https://www.vagrantup.com/docs/vmware/known-issues.html +

+
-- cgit v1.2.3