5093f3120e
This is a big commit, and I apologize in advance for the future
git-blames all pointing to me. This commit does a few things:
1. Merges the website/docs and website/www repo into a single website repo
to be in line with other HashiCorp projects
2. Updates to use middleman-hashicorp
3. Converts less to scss to be in line with other projects
4. Updates page styles to be in line with other projects
5. Optimizes images
6. Prepare for S3 + Fastly deployment with scripts, etc.
7. Removes blog posts (they have been transferred to hashicorp.com with
redirects in place
8. Updated sitemap generation script for better SEO
9. Fixed many broken links
10. Add description to all fields
27 lines
947 B
Markdown
27 lines
947 B
Markdown
---
|
|
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 providers.
|
|
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 providers.
|
|
Note that none of these are generally blockers to using the provider, but
|
|
are good to know.
|
|
|
|
## 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.
|