X-Git-Url: https://vilimpoc.org/repos/dotfiles/blobdiff_plain/4776737b67f1d3e04d18dc4622e7bfb120f74e11..325b494c6241dcc4dc1cb7436ee84ac105b318eb:/setup-windows.bat?ds=inline

diff --git a/setup-windows.bat b/setup-windows.bat
index 23f2ff9..a6bc8ea 100644
--- a/setup-windows.bat
+++ b/setup-windows.bat
@@ -347,6 +347,12 @@ if not "%ERRORLEVEL%"=="0" call :winget NASM NASM.NASM
 @rem This is also what makes setup-windows-7-test-env.bat unreachable from an
 @rem ARM64 host: it prepares a Windows 7 *x86* guest, and neither VirtualBox nor
 @rem Hyper-V on ARM64 can run one.
+@rem
+@rem Nor is it installed when this Windows is itself a virtual machine, which the
+@rem planner reads from the firmware's SMBIOS strings: the test VMs belong on the
+@rem physical host, and nesting VirtualBox inside a guest needs nested
+@rem virtualization the outer hypervisor usually does not offer. The plan marks it
+@rem -NotInVM, with that reason, and names the hypervisor it found.
 call :winget VirtualBox Oracle.VirtualBox
 
 @rem ---------------------------------------------------------------------------