Guru Meditation - Windows 11 Guest Dies on Restart

Discussions related to using VirtualBox on Windows hosts.
Post Reply
dbareis
Posts: 3
Joined: 20. Sep 2020, 03:49

Guru Meditation - Windows 11 Guest Dies on Restart

Post by dbareis »

RE: VirtualBox Version 6.1.34 r150636 (Qt5.6.2) on Windows 11 Host

I have installed Windows 11 following these instructions (https://blogs.oracle.com/virtualization ... virtualbox). I have managed to get it installed and running but all through install and any time I start a reboot it displays a critical error:
Picture of dialog
Picture of dialog
Guru Meditation (on restart).png (19.56 KiB) Viewed 1008 times
I can put up with it if I have to but hopefully someone has a solution (logs attached).
Attachments
Guru Meditation - Logs.zip
Logs
(238.75 KiB) Downloaded 11 times
scottgus1
Site Moderator
Posts: 20945
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Windows, Linux

Re: Guru Meditation - Windows 11 Guest Dies on Restart

Post by scottgus1 »

Thanks for the logs! In both VM logs, the guru meditates on a Triple Fault, which is Virtualbox's "Beats me what's going on, I give up" error message. The meditation happens right after the EFI BIOS finishes loading. I don't know why, though.

You're using a registry Rick method to get 11 installed. This is needed because 6.1 is not compatible with Windows 11. Apparently, the goal is for 7.0 to support 11, and the 6.1.97 development snapshot releases on the test builds are supposed to be what 7.0 will be one day.

We'll have to see if forum gurus can weigh in on what may be wrong in the logs or whether their Windows 11 on 6.1.34 VMs reboot OK.

You could also try un-hacked 11 on 6.1.97. Save the test build installer until you update again later.
fth0
Volunteer
Posts: 5690
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: Guru Meditation - Windows 11 Guest Dies on Restart

Post by fth0 »

The VBoxHardening.log file shows two candidates which could lead to problems: Bitdefender and ObjectDock. For a test, uninstall both softwares, reboot, and check if the issue persists. If the issue is solved, re-install the softwares one by one and see which one is responsible.
Post Reply