Merge pull request #3959 from chrislovecnm/vsphere-ipv4-documentation-updates

Update docs to reflect vsphere provider only supporting IPv4 addresses

website/source/docs/providers/vsphere/index.html.markdown

@@ -17,7 +17,8 @@ The provider needs to be configured with the proper credentials before it can be
 Use the navigation to the left to read about the available resources.
 
 ~> **NOTE:** The VMware vSphere Provider currently represents _initial support_
-and therefore may undergo significant changes as the community improves it.
+and therefore may undergo significant changes as the community improves it. This
+provider at this time only supports IPv4 addresses on virtual machines.
 
 ## Example Usage
 
@@ -72,7 +73,7 @@ In addition, the following environment variables are used in tests, and must be
  * VSPHERE\_TEMPLATE
 
 The following environment variables depend on your vSphere environment:
-	
+
  * VSPHERE\_DATACENTER
  * VSPHERE\_CLUSTER
  * VSPHERE\_RESOURCE\_POOL

website/source/docs/providers/vsphere/r/virtual_machine.html.markdown

@@ -55,7 +55,7 @@ The following arguments are supported:
 Network interfaces support the following attributes:
 
 * `label` - (Required) Label to assign to this network interface
-* `ip_address` - (Optional) Static IP to assign to this network interface. Interface will use DHCP if this is left blank.
+* `ip_address` - (Optional) Static IP to assign to this network interface. Interface will use DHCP if this is left blank. Currently only IPv4 IP addresses are supported.
 * `subnet_mask` - (Optional) Subnet mask to use when statically assigning an IP.
 
 <a id="disks"></a>