Be clear which hypervisors are supported (#15281)

* Update windows-install.md

* Remove another unsupported hypervisor (#15280)

desktop/install/windows-install.md

@@ -54,7 +54,7 @@ Your Windows machine must meet the following requirements to successfully instal
   - 4GB system RAM
   - BIOS-level hardware virtualization support must be enabled in the
     BIOS settings. For more information, see
-    [Virtualization](../troubleshoot/topics.md).
+    [Virtualization](../troubleshoot/topics.md#virtualization).
 
 - Download and install the [Linux kernel update package](https://docs.microsoft.com/windows/wsl/wsl2-kernel){: target="_blank" rel="noopener" class="_"}.
 
@@ -76,7 +76,7 @@ Your Windows machine must meet the following requirements to successfully instal
   - 4GB system RAM
   - BIOS-level hardware virtualization support must be enabled in the
     BIOS settings. For more information, see
-    [Virtualization](../troubleshoot/topics.md).
+    [Virtualization](../troubleshoot/topics.md#virtualization).
 
 </div>
 </div>
@@ -89,9 +89,9 @@ Containers and images created with Docker Desktop are shared between all
 user accounts on machines where it is installed. This is because all Windows
 accounts use the same VM to build and run containers. Note that it is not possible to share containers and images between user accounts when using the Docker Desktop WSL 2 backend.
 
-Nested virtualization scenarios, such as running Docker Desktop on a
-VMWare or Parallels instance might work, but there are no guarantees. For
-more information, see [Running Docker Desktop in a VM or VDI environment](../vm-vdi.md).
+Running Docker Desktop inside a VMware ESXi or Azure VM is supported for Docker Business customers.
+It requires enabling nested virtualization on the hypervisor first.
+For more information, see [Running Docker Desktop in a VM or VDI environment](../vm-vdi.md).
 
 ### About Windows containers
 

desktop/vm-vdi.md

@@ -14,9 +14,9 @@ To run Docker Desktop in a virtual desktop environment, it is essential nested v
 
 >Note
 >
-> Support for running Docker Desktop on a virtual desktop is only available to Docker Business customers. 
+> Support for running Docker Desktop on a virtual desktop is available to Docker Business customers, on VMware ESXi or Azure VMs only.
 
-The support available from Docker extends to installing and running Docker Desktop inside the VM, once the nested virtualization is set up correctly. For more information on Docker Desktop support, see [Get support](support.md).
+The support available from Docker extends to installing and running Docker Desktop inside the VM, once the nested virtualization is set up correctly. The only hypervisors we have successfully tested are VMware ESXi and Azure, and there is no support for other VMs. For more information on Docker Desktop support, see [Get support](support.md).
 
 For troubleshooting problems and intermittent failures that are outside of Docker's control, you should contact your hypervisor vendor. Each hypervisor vendor offers different levels of support. For example, Microsoft supports running nested Hyper-V both on-prem and on Azure, with some version constraints. This may not be the case for VMWare ESXi.
 
@@ -35,9 +35,6 @@ You may also need to [configure some network settings](https://www.vembu.com/blo
 
 ### Enable nested virtualization on Microsoft Hyper-V
 
-Nested virtualization is supported by Microsoft for running Hyper-V inside a VM running on a Hyper-V host, in Azure or on-prem (Hyper-V on Hyper-V).
+Nested virtualization is supported by Microsoft for running Hyper-V inside an Azure VM.
 
 For Azure virtual machines, [check that the VM size chosen supports nested virtualization](https://docs.microsoft.com/en-us/azure/virtual-machines/sizes). Microsoft provides [a helpful list on Azure VM sizes](https://docs.microsoft.com/en-us/azure/virtual-machines/acu) and highlights the sizes that currently support nested virtualization. For internal testing, we used D4s_v5 machines. We recommend this specification or above for optimal performance of Docker Desktop.
-
-For on-prem virtual machines, check the constraints on the host VM operating system and [follow the steps documented by Microsoft](https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/user-guide/nested-virtualization).
-