Guru meditation for 32-bit Lubuntu 17.10 guest with 4.13.0-32 and 4.13.0-36 kernels

[Oloryn]

I've had a 32-bit Lubuntu 17.10 guest (running VB 5.2.6 on a 64-bit Windows 10 machine, with no VT-x (which is why the guest is runing 32-bit), and ever since a couple of recent kernel updates (to 4.13.0-32 and 4.13.0-36), booting the guest provokes a Guru Meditation. Logs for each of the two kernels are attached. Relevant messages I'm seeing are "emR3Debug: rc=VERR_TRPM_DONT_PANIC" and "VCPU0: Guru Meditation -2403 (VERR_TRPM_DONT_PANIC)".

I've tried switching to the most recent test build (5.2.7 r120865 (Qt5.6.2)), but the problem persists. So far I've been able to work around this by launching the guest by booting with a 4.3.0-21 kernel.

Any ideas on how to deal with this?

[QuaxEros]

Same thing here. VBox 5.2.6_201293. Linux & Windows 10 (x64) as hosts without hw-virtualization.
I can take up my kernels to 4.9.0.6-686 (non-pae). upgrading to 4.13.x or 4.14.x leads to Guru meditation.
I tried VBox 5.0 and 5.1, same issue. Would the VBox BIOS maybe be the problem?

[Oloryn]

I've been getting the same thing for about 2 1/2 months here. I've worked around it by booting with an the last kernel to be able to boot. At this point, it's been going on long enough that another problem has raised its head: I can't create a 32-bit Ubuntu 18.04 VM at all, as the same "VCPU0: Guru Meditation -2403 (VERR_TRPM_DONT_PANIC)" problem comes up with the kernel on the install disk.

The VBox.log and VBox.png files are attached, zipped.

[socratis]

First of all, why did you attach a completely black PNG? I don't think it "adds" anything to the description, right?

Now, from the log:

00:00:28.464424 !! VCPU0: Guru Meditation -2403 (VERR_TRPM_DONT_PANIC)

This is the Guru Meditation you're getting.

00:00:02.048774 HM: HMR3Init: Falling back to raw-mode: VT-x is not available
00:00:04.213702 Full Name: "Intel(R) Pentium(R) CPU P6200 @ 2.13GHz"

And this is why you're getting it. If you want to run this VM, you will need to address/fix this.

Unfortunately, your Pentium P6200 does not support VT-x. So, you can't run this VM as is. Your best bet would be to try something from the 4.3.x series, the 5.0.x series or the 5.1.x series. The higher the VirtualBox version, the more dependent it is on the existence of VT-x, as the "raw mode" will be getting phased out over time.

But, given the fact that another user with the exact same CPU failed, even when running a 4.3.0 version of VirtualBox, I'd say that your only option is to get a new computer, if you want to run this VM/kernel (don't forget that your CPU is 8 years old). It's a fact of life that both hardware and software evolves, and the requirements change. So, the kernel *must* have VT-x or it will fail. That's where you are right now.

@QuaxEros
You didn't attach any logs, but I believe that you're in the same situation. Just open up a VBox.log, search for "Full Name". That line is going to give you the name of your CPU. Search for that name, and if it's an Intel one, you'll end up in an information/characteristics page from "ark.intel.com", like the one that I've linked to above for the P6200. Search for VT-x. If it says "No", you need to update your hardware as well...