Version
7.2.8
Host OS Type
Windows
Host OS name + version
Windows 11 Home 25H2 (build 26200.8655)
Host Architecture
x86
Guest OS Type
Linux
Guest Architecture
x86
Guest OS name + version
Debian 12
Component
API
What happened?
I cannot get any version newer than v7.1.10 to boot an existing VM or create a new one. I think this was working before so it may have been a recent MS update. I tried every possible way explained on the internet to disable VBS/HyperV but nothing works, so disabling that to get Virtualbox to work is not an option. I am fine with the green turtle and running in native-API mode because I want to use WSL, so I just want it to work with MS Hypervisor still enabled and without direct access to VT-x. My CPU is Intel 12th gen (Alder Lake) and VT-X is enabled in the BIOS. This happens on any VM, even if I try create a new one. It happens very early on in the boot process.
I had an AI agent analyze the log file and my Windows configuration and it's findings are detailed in the attachment. Using recompiler mode is far too slow to be useful other than for debug/troubleshoot, so that is not an option. Using virtualbox v7.1.10 gets me to green turtle (native-API) mode which is much faster. So that is all I want to try get working with v7.2.x
I also tried changing the number of processors to 1 and 3 just to confirm it was not related to that problem.
How can we reproduce this?
On latest fully updated Windows 11 Home with HyperV enabled, or disabled according to these instructions but still showing when viewing output of msinfo32 command, install Virtualbox and try create a VM or start an existing one.
ai_findings.md
VBox.log
Did you upload all of your necessary log files, screenshots, etc.?
After downgrading from virtualbox v7.2.8 to v7.1.10 the above VM works normally in native-API mode. I also tried several versions in between those two, such as 7.1.12, 7.1.14, 7.2.6 etc. but none worked.
Version
7.2.8
Host OS Type
Windows
Host OS name + version
Windows 11 Home 25H2 (build 26200.8655)
Host Architecture
x86
Guest OS Type
Linux
Guest Architecture
x86
Guest OS name + version
Debian 12
Component
API
What happened?
I cannot get any version newer than v7.1.10 to boot an existing VM or create a new one. I think this was working before so it may have been a recent MS update. I tried every possible way explained on the internet to disable VBS/HyperV but nothing works, so disabling that to get Virtualbox to work is not an option. I am fine with the green turtle and running in native-API mode because I want to use WSL, so I just want it to work with MS Hypervisor still enabled and without direct access to VT-x. My CPU is Intel 12th gen (Alder Lake) and VT-X is enabled in the BIOS. This happens on any VM, even if I try create a new one. It happens very early on in the boot process.
I had an AI agent analyze the log file and my Windows configuration and it's findings are detailed in the attachment. Using recompiler mode is far too slow to be useful other than for debug/troubleshoot, so that is not an option. Using virtualbox v7.1.10 gets me to green turtle (native-API) mode which is much faster. So that is all I want to try get working with v7.2.x
I also tried changing the number of processors to 1 and 3 just to confirm it was not related to that problem.
How can we reproduce this?
On latest fully updated Windows 11 Home with HyperV enabled, or disabled according to these instructions but still showing when viewing output of
msinfo32command, install Virtualbox and try create a VM or start an existing one.ai_findings.md
VBox.log
Did you upload all of your necessary log files, screenshots, etc.?
After downgrading from virtualbox v7.2.8 to v7.1.10 the above VM works normally in native-API mode. I also tried several versions in between those two, such as 7.1.12, 7.1.14, 7.2.6 etc. but none worked.