Guru Meditation critical error occurs whenever I boot my Redhat enterprise VM on Windows 11 Pro PC

Discussions related to using VirtualBox on Windows hosts.
Post Reply
Zectzozda
Posts: 1
Joined: 7. Jun 2022, 04:05

Guru Meditation critical error occurs whenever I boot my Redhat enterprise VM on Windows 11 Pro PC

Post by Zectzozda »

Hello!

My Redhat enterprise VM encounters this Guru Meditation error whenever I launch it on my Windows 11 Pro PC. I've attached some relevant screenshots. Note: the VBox.log file exceeds the 128KiB max limit on this site. Unfortunately, as I had to create this account to post here, my account doesn't meet the 1 day and 1 post minimum requirements to post URLs, so here's my attempt at pointing you in the direction of the paste containing the VBox.log contents: www dot controlc dot com slash 9d238f6d

Note: I found this forum with a similar issue (post id 518910), which recommended disabling hardware acceleration within the 3rd party antivirus. I've checked this setting in Malwarebytes, but it is already disabled.

I perused through the file, but my untrained eye could not identify any mentions of a possible cause, nor could I really decipher most of the file.

Your help is much appreciated!

Edit: I rebooted the VM in a vain attempt to get it working again. It didn't show a guru error. Instead, it posted a few lines of "*ERROR* failed to send host log message."
Attachments
VBox.png
VBox.png (958 Bytes) Viewed 765 times
Hardware acceleration already disabled malwarebytes.png
Hardware acceleration already disabled malwarebytes.png (46.38 KiB) Viewed 765 times
Virtualbox Guru Meditation.png
Virtualbox Guru Meditation.png (22.74 KiB) Viewed 765 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 critical error occurs whenever I boot my Redhat enterprise VM on Windows 11 Pro

Post by scottgus1 »

Start the VM from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the VM from within the VM's OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.

Right-click the VM in the main Virtualbox window's VM list, choose Show Log. Save the far left tab's log, zip it, and post the zip file, using the forum's Upload Attachment tab.
Post Reply