AWS workspaces: Added nested virtualization support and troubleshooting guide
Summary
Documentation updated to reflect support for nested virtualization on Windows/Linux WorkSpaces, including Docker usage guidance and troubleshooting steps.
Security assessment
The change introduces feature enablement and operational guidance for nested virtualization. No security vulnerabilities, configurations, or incidents are addressed.
Evidence
+Nested virtualization is now supported on Windows WorkSpaces. Enable nested virtualization to use Docker Desktop on your Windows WorkSpace. For more information, see [Nested virtualization for WorkSpaces Personal](https://docs.aws.amazon.com/workspaces/latest/adminguide/nested-virtualization.html). We recommend using a Power bundle with 4 vCPU or higher for optimal Docker Desktop performance.
Diff
diff --git a/workspaces/latest/adminguide/amazon-workspaces-troubleshooting.md b/workspaces/latest/adminguide/amazon-workspaces-troubleshooting.md index 40ba12047..47ae620c0 100644 --- a//workspaces/latest/adminguide/amazon-workspaces-troubleshooting.md +++ b//workspaces/latest/adminguide/amazon-workspaces-troubleshooting.md @@ -368,0 +369,2 @@ The following information can help you troubleshoot specific issues with your Wo + * Troubleshooting nested virtualization + @@ -1022 +1024,3 @@ Deleting a WorkSpace is a permanent action and cannot be undone. The WorkSpace u -Nested virtualization (including the use of Docker) is not supported on Windows WorkSpaces. For more information, see the [ Docker documentation](https://docs.docker.com/docker-for-windows/troubleshoot/#running-docker-desktop-in-nested-virtualization-scenarios). +Nested virtualization is now supported on Windows WorkSpaces. Enable nested virtualization to use Docker Desktop on your Windows WorkSpace. For more information, see [Nested virtualization for WorkSpaces Personal](https://docs.aws.amazon.com/workspaces/latest/adminguide/nested-virtualization.html). We recommend using a Power bundle with 4 vCPU or higher for optimal Docker Desktop performance. + +If Docker Desktop still won't start after enabling nested virtualization, verify that the **Nested Virtualization** field shows `Enabled` in the **Summary** section of the Amazon WorkSpaces console, or run the AWS CLI `describe-workspaces` command and confirm that `NestedVirtualizationEnabled` is set to `true`. @@ -1026 +1030,21 @@ Nested virtualization (including the use of Docker) is not supported on Windows -To use Docker on Linux WorkSpaces, make sure that the CIDR blocks used by Docker don't overlap with the CIDR blocks used in the two elastic network interfaces (ENIs) associated with the WorkSpace. If you encounter problems with using Docker on Linux WorkSpaces, contact Docker for assistance. +Nested virtualization is now supported on Linux WorkSpaces. Enable nested virtualization to use Docker on your Linux WorkSpace. For more information, see [Nested virtualization for WorkSpaces Personal](https://docs.aws.amazon.com/workspaces/latest/adminguide/nested-virtualization.html). The WorkSpace reboots after enabling nested virtualization. Make sure that the CIDR blocks used by Docker don't overlap with the CIDR blocks used in the two elastic network interfaces (ENIs) associated with the WorkSpace. We recommend using a Power bundle with 4 vCPU or higher for optimal Docker performance. + +If Docker doesn't work after enabling nested virtualization, verify that the **Nested Virtualization** field shows `Enabled` in the **Summary** section of the Amazon WorkSpaces console, or run the AWS CLI `describe-workspaces` command and confirm that `NestedVirtualizationEnabled` is set to `true`. Also confirm that your WorkSpace is using the DCV (WSP) protocol. + +### Troubleshooting nested virtualization + +###### Enable Nested Virtualization is not visible in the Actions menu + +The **Enable Nested Virtualization** option is not available on GPU WorkSpaces or on WorkSpaces running older operating systems such as Windows Server 2016 or Windows 10. Validate that your WorkSpace meets the prerequisites described in [Nested virtualization for WorkSpaces Personal](https://docs.aws.amazon.com/workspaces/latest/adminguide/nested-virtualization.html). + +###### My WorkSpace reboots after enabling nested virtualization + +This is expected behavior. A reboot is required to enable nested virtualization on the WorkSpace. + +###### Docker Desktop or WSL2 won't start after enabling nested virtualization + +Verify that the **Nested Virtualization** field shows `Enabled` in the **Summary** section of the Amazon WorkSpaces console, or run the AWS CLI `describe-workspaces` command and confirm that `NestedVirtualizationEnabled` is set to `true`. Also confirm that your WorkSpace is using the DCV (WSP) protocol. + +###### My AutoStop WorkSpace performs a full reboot instead of hibernating + +This is a known limitation on WorkSpaces running Windows Server 2025, Windows 11 24H2, or Windows 11 25H2 with nested virtualization enabled. When the AutoStop timeout is reached, the WorkSpace performs a full reboot instead of hibernating, and in-memory data is not preserved. If you require hibernation behavior, use an AlwaysOn WorkSpace instead. To disable nested virtualization, choose **Actions** , **Disable Nested Virtualization** , or use the AWS CLI `modify-workspace-properties` command with `NestedVirtualizationEnabled` set to `false`.