Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT) after messy repair attempts

Discussions related to using VirtualBox on Linux hosts.
Post Reply
dee_ess_1154
Posts: 2
Joined: 24. May 2021, 20:28

Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT) after messy repair attempts

Post by dee_ess_1154 »

Hi there,

I've been using my VM for a few months now productively, until I messed up today. I would appreciate any help fixing it.

Here's some basic info:

Using Virtualbox Version 6.1.22 r144080 (Qt5.9.5)
Host OS: Linux Mint 19.3 Tricia x86_64
CPU: Intel i7-8700K (12) @ 4.700GHz
GPU: NVIDIA GeForce GTX 1080 Ti using nvidia-driver-465

Guest OS is some Windows 10 64-bit

Installed Extension Packs:
00:00:00.803625 Oracle VM VirtualBox Extension Pack (Version: 6.1.22 r144080; VRDE Module: VBoxVRDP)
Mounted iso for the Guest Additions was VBoxGuestAdditions_5.2.42.iso, so I'm assuming that's the version that was installed.

Current behaviour:
On starting the VM, I get the Virtualbox splash screen until I get "Guru Meditation - A cricital error has occured..." a few seconds later.
Latest Log is attached.

What happened:
Earlier, the VM was working as expected - I shut it down after use and was looking to restart when I got the "Windows is now checking your disks" on the next boot. This got stuck at 78% or something; and there was no further progress after ~15 minutes of waiting. I had no choice but to hard shutdown.

At this point, things got a bit messy: after fiddling around I noticed that the file-system that holds the VM was switched to read-only, which might indicate a hardware problem?
I checked all the cables, rebooted and ran disk checks - everything seemed to be in order after that.

I then tried different versions of virtualbox, installing and un-installing different packages and messing with the settings. However I'm pretty sure the latest settings are the same I used before.

Now, I'm out of ideas and I fear the worst - data loss!
If there's anything to be checked, to be attempted - I'd much appreciate some input.

Thanks!
Attachments
VBox.log.zip
(80.61 KiB) Downloaded 6 times
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT) after messy repair attempts

Post by scottgus1 »

The VM environment seems to run fine, but it guru-meditates right after touching the disk:
00:00:08.744863 VMMDev: Guest Log: BIOS: Booting from Hard Disk...
00:00:08.961550 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=00007f8c98000000 w=1024 h=768 bpp=24 cbLine=0xC00 flags=0x0 origin=0,0
00:00:08.980060 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'
00:00:08.980074 Console: Machine state changed to 'GuruMeditation'
00:00:08.980315 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:00:08.980316 !!
00:00:08.980316 !! VCPU0: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)
This may have something to do with it:
dee_ess_1154 wrote:the file-system that holds the VM was switched to read-only
A permissions glitch might cause this, probably not a hardware problem, I'd guess. More of a Linux problem, though.

See if you can fix that, then try again.
dee_ess_1154
Posts: 2
Joined: 24. May 2021, 20:28

Re: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT) after messy repair attempts

Post by dee_ess_1154 »

Thanks so much for the input!
A few hours later and it seems the problem is found. Looks like it was not strictly a Virtualbox problem, but rather the Windows 10 bootloader had issues.
Booting with an install iso and liberal use of diskpart and bootrec seems to have fixed the issue.
Thanks again, you pointed me in the right direction; I wasn't sure how to read the error log and had no idea what triple fault might mean.
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT) after messy repair attempts

Post by scottgus1 »

Triple Fault means that something is so wrong it blew past Virtualbox's error fixers and Virtualbox throws up its hands and says "Beats me what to do with this!"

Glad you're up and running!

One future thought, since the data is so important, take backups! And practice the restore process.
Post Reply