I've tried booting nested VirtualBox VM Windows 10 1903 x64 ISO and a Windows XP 32 bit, inside a VM with two CPUs, but all I got is triple fault guru meditation, when the nested VM started.
The log is the attempt to boot the Windows 10 1903 x64 setup ISO. The nested VirtualBox was also 6.1.0beta1
Nested VT-x triple fault
-
- Volunteer
- Posts: 321
- Joined: 7. Oct 2009, 12:40
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: various
Nested VT-x triple fault
- Attachments
-
- VBox.zip
- (74.59 KiB) Downloaded 575 times
-
- Volunteer
- Posts: 3342
- Joined: 10. May 2007, 16:59
- Location: Israel
Nested VT-x crash
Level 0 = host. (Win10, 64-bit + Intel Core i7 6600U, Skylake CPU) - VBox 6.1.0-BETA1
Level 1 = 1st level of virtualization.
Level 2 = 2nd level of virtualization, going deeper into the rabbit hole.
Level 1 = Windows XP + VBox 4.1.6 (older, with official WinXP host support and VT-x enabled)
Level 2 = empty VM (VT-x enabled) -- I expected to see VirtualBox BIOS booting and that's it.
Actual results:
Crash with Guru meditation. (which means that Nested VT-x is incomplete, at least in 32-bit mode --- theoretically this should work.)
Level 1 = 1st level of virtualization.
Level 2 = 2nd level of virtualization, going deeper into the rabbit hole.
Level 1 = Windows XP + VBox 4.1.6 (older, with official WinXP host support and VT-x enabled)
Level 2 = empty VM (VT-x enabled) -- I expected to see VirtualBox BIOS booting and that's it.
Actual results:
Crash with Guru meditation. (which means that Nested VT-x is incomplete, at least in 32-bit mode --- theoretically this should work.)
- Attachments
-
- Nested VT-x crash of Level1 hypervisor. Screenshot
- Nested-VT-x.png (72.13 KiB) Viewed 19189 times
-
- Nested-VT-x--Level1-ZeroVM-2019-09-24-18-40-59.zip
- Nested VT-x, Level0, vbox.log
- (22.37 KiB) Downloaded 591 times
-
- Nested-VT-x-level0-Windows XP-2019-09-24-20-41-12.zip
- Nested VT-x, Level0, vbox.log
- (27.43 KiB) Downloaded 610 times