virtualbox.org

Hi. After resetting my VM I get the Guru Meditation error with code:
1607 (VERR_PGM_HANDLER_NOT_FOUND)
Would someone please be able to tell me what to do to get it to work again? Thanks!

nzn wrote:Would someone please be able to tell me what to do to get it to work again?

Place a suitable fee into account number...

Seriously though, we will need to see the VBox.log file from the guest in question. Boot the guest, make sure the problem occurs then shut the guest down (by force if necessary). zip the log file and post it.

-Andy.

nzn wrote:After resetting my VM

Can you explain that part?

Thanks for offering to help!
After resetting my VM = choosing the reset option when right clicking the VM icon.
Can no longer boot the guest. All options are grayed.
The guru message is right next to the VM icon in vbox manager.
Log is attached.

Was this a one-off Guru, or is this reproducible? I can't easily see how this could be reproducible if it takes that long:

315:36:29.805695 Changing the VM state from 'RUNNING' to 'RESETTING'
...
315:36:37.258288 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'

You seem that you started the VM from a saved-state:

00:00:02.969450 Changing the VM state from 'CREATING' to 'CREATED'
00:00:02.970729 Changing the VM state from 'CREATED' to 'LOADING'
00:00:02.972425 SSM: File header: Format 2.0, VirtualBox Version 5.2.22 r126460, 64-bit host, cbGCPhys=8, cbGCPtr=8

Do you get that Guru if you don't?

00:00:00.833881 Guest OS type: 'Ubuntu_64'
00:00:02.013267 Name <string> = "vm-term1" (cb=9)

I couldn't get the Ubuntu distro/version from this, can you be a little more detailed? If you have a link to the ISO that you used to create the VM, that would be even better...

00:00:02.013271 RamSize <integer> = 0x0000000040000000 (1 073 741 824, 1 024 MB)

In any case/distro/version, this seems way too low for anything 64-bit!

VirtualBox VM 5.2.22 r126460 win.amd64 (Nov  8 2018 19:34:58) release log
00:00:02.013586 VMSVGAEnabled <integer> = 0x0000000000000001 (1)

Now... that's an interesting combination, to say the least!

You see, before 6.0.0, you had to manually enable the VMSVGA option from the command-line, with a really not-existent (documentation-wise) command. How exactly did you do it, and most importantly, why?

Someone more technical than me set it up for me so I can't say I know for sure the answers to all your questions, but the VMSVGA probably came because originally he tried to do it in VBox 6.0.0 and the ethernet over USB didn't work on it so we did it on 5.2.2 instead. Never had any RAM problems.
I could not try any of your suggestions as all options to set or start the machine were grayed out (see attachment).
As it happens, I managed to solve the issue by closing VBox, and then from Task manager closing some other VBox related processes that were somehow still running.
After that I just restarted VBox, the machine had an "aborted" sign next to it and it started up normally.
Thanks for all your good will and efforts!

nzn wrote:but the VMSVGA probably came because originally he tried to do it in VBox 6.0.0 and the ethernet over USB didn't work on it so we did it on 5.2.2 instead.

That would definitely explain it. I didn't realize that you set up this VM with 6.0.x originally.

nzn wrote:I could not try any of your suggestions as all options to set or start the machine were grayed out (see attachment).

Yes, because the VM is PAUSED! You need to get into the habit of shutting down the VM from within the VM. A lot of problems go away if you follow that simple rule.

nzn wrote:As it happens, I managed to solve the issue by closing VBox, and then from Task manager closing some other VBox related processes that were somehow still running.

Do not do that! Unless you are pretty sure that the VirtualBox processes are indeed stuck, which is a rare thing. You might cause corruption in the configuration files, and then you'll have a whole new set of problems.

nzn wrote:and it started up normally.

Glad to see you get it going. Marking as [Solved].