From d4775ef1c06a7faa88aba81b5963ba3cc9ecc937 Mon Sep 17 00:00:00 2001 From: JP Cottin Date: Fri, 15 May 2026 01:19:07 -0700 Subject: [PATCH] README: point the Azure nested-virt link at the right Microsoft doc The previous link (`docs.microsoft.com/.../windows/nested-virtualization`) is the Windows feature page; the actual gating concern for running the emulator container on Azure is picking a VM size whose family supports nested virtualization. The Azure Compute Units table flags this per family, so point users there instead. Originally reported by @leesabuh in #285. --- README.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 3df51c4..df4da64 100644 --- a/README.md +++ b/README.md @@ -29,9 +29,8 @@ following requirements: - AWS provides [bare metal](https://aws.amazon.com/about-aws/whats-new/2019/02/introducing-five-new-amazon-ec2-bare-metal-instances/) instances that provide access to KVM. - - Azure: Follow these - [instructions](https://docs.microsoft.com/en-us/azure/virtual-machines/windows/nested-virtualization) - to enable nested virtualization. + - Azure: pick a [VM size that supports nested virtualization](https://learn.microsoft.com/en-us/azure/virtual-machines/acu) + (the `acu` table flags supported families). KVM is then available inside the VM. - GCE: Follow these [instructions](https://cloud.google.com/compute/docs/instances/enable-nested-virtualization-vm-instances) to enable nested virtualization.