Opened 4 years ago
Last modified 3 years ago
#19622 new defect
VINF_EM_TRIPLE_FAULT on Server 2019 initial boot and install
Reported by: | moumoku | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 6.1.8 |
Keywords: | Cc: | ||
Guest type: | Windows | Host type: | Windows |
Description
VT-v enabled in host bios, attempted with guest efi enabled as well as disabled. Host Hyper-V platform disabled. After parsing the logs with an untrained eye, it looks as if it might be an issue with the cpu. Attempted with 1, 4 and 8 threads allocated, and 4gb and 8gb memory allocated.
Attachments (3)
Change History (7)
by , 4 years ago
comment:1 by , 4 years ago
HMR3Init: Attempting fall back to NEM: AMD-V is not available WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...
I think this would suggest I haven't enabled virtualization in by bios, but I've double, and triple checked that at this point. Also, I've removed Hyper-V, both via "Turn Windows features on or off" and via BCDedit, so color me confused.
comment:2 by , 4 years ago
For whatever reason, switching from "Windows 2019" to "Windows 10" in OS selector allows me to boot into the installer. More later.
comment:3 by , 4 years ago
Hello,
I am seeing the same thing while trying to boot from the Windows Server 2019 setup ISO to begin the operating system installation. The same remedy (changing OS type from Server 2019 to Windows 10) resolves the problem. I am attaching my logs here in case it is helpful. I am using 6.1.16 on a Windows Server 2012 R2 host.
Thanks
by , 3 years ago
Logs, Windows 10 20H1 host, Windows Server 2022 client, Hyper-V fallback
comment:4 by , 3 years ago
Replicating this issue with a Windows 10 21H1 host (mistakenly wrote 20H1 in attachment description), Windows Server 2022 client, Hyper-V fallback. Uploaded logs. Crash happens when Windows 2019 is selected as Windows version; changing to Windows 10 stops crash.
Vbox.log, Vbox.png and VboxHardening.log