Guru meditation on VM start

[Dave Odell]

It worked yesterday, but today I get a Guru Meditation trying to start some of my virtual machines. This shows up in VBox.log as "VCPU0: Guru Meditation -2708 (VERR_VMM_SET_JMP_ABORTED_RESUME)". I suspect this may have started due to a Linux kernel upgrade I installed this morning.

A fresh VM with no disk shows the issue. Sometimes turning off the I/O APIC makes the issue go away, sometimes not. Turning off nested paging sometimes lets VirtualBox make a little bit of progress w.r.t. booting VMs, but that usually still crashes before the VM finishes starting.

This may be related to this bug reported on the VirtualBox forums: https://forums.virtualbox.org/viewtopic.php?t=111889&sid=5cd33c0872a03b689e7e9f84d850f538

Ubuntu is 22.04.4 LTS, kernel is 5.15.0-116-generic, VirtualBox is 6.1.50-dfsg-1~ubuntu1.22.04.1.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Ange des Ténèbres (angedestenebresk)]

Hey,

I have exactly the same issue on Linux Mint 21.3 (based on Ubuntu 22.04) with the kernel 5.15.0-116 and Virtualbox installed from Ubuntu repo (version 6.1.50-dfsg-1~ubuntu1.22.04.1).

After trying to go back to previous kernel version 5.15.0-113, all my VM worked again. So, it seems the last kernel version for 5.15 causes that.

[Arrigo Marchiori (ardovm)]

Same problem here, on several machines, all Ubuntu 22.04 after updating the kernel to version 5.15.0-116.

All hosts and guests are x86_64.

[berni123 (bernd-bernd--zimmermann)]

I can confirm this bug an add the following information:

Kernel 5.15.0-116-generic: VBox 6.1.50 is not working at all

Kernel 5.15.0-112-generic and 5.15.0-113-generic: VBox 6.1.50 is working with boot workaround amg_iommu=off due to the bug in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2068738

Kernel 5.15.0-107-generic: VBox 6.1.50 is working without problems

It looks like, that another kernel patch between -112/-113 and -116 causes the issue with VBox 6.1.50

Regards,
Bernd

[Andy (montagu)]

Here is a ticket for the same issue on virtualbox.org, for what it's worth:
https://www.virtualbox.org/ticket/22115
But support for VirtualBox 6.1 ended in January this year so we can't expect any fix to be forthcoming from Oracle.

[Xavier Tannier (xtannier)]

I have the same problem, solved by uninstalling the version from Ubuntu repo, and installing instead the version 7 from virtualbox web site:
https://www.virtualbox.org/wiki/Linux_Downloads

[Pudding (little-pudding)]

Same story for me with Linux Mint 21.3 Cinnamon and VirtualBox 6.1 on Thinkpad T495 (AMD Ryzen):

5.15.0-116 fails

5.15.0-113 fails (doesn't even manage to boot Linux Mint, why did they push this to updates?!)

5.15.0-112 fails (manages to get a line of text out on the console before the VM crashes)

5.15.0-107 works perfectly fine

[Alan Knepper (al-knepper)]

I've had all sorts of issues with Kernels after -107. First my keyboard was unresponsive after a sleep/suspend. Then it was not being able to suspend (it would just immediately wake).

Adding entries in grub fixed the first issue for while and got fixed about 112 or 113. Now they toss this issue in.

I've been trying quite a few other operating systems, installing them to a spare 40G chunk of HD. I'm surprised at how many have my original suspend/keyboard issues. I've never made records as to which Kernels are involved, sure might have been useful huh?!!

I have also discovered that Kernel 113 or 6.5x fix Virtualbox. I found the partial fix by booting Zorin OS (my current testing OS on that 40G hd) and found that all of my VM images worked in that OS. I was glad to find out that all the vdi files were still valid.

I think I'm going to wait for the dust to settle, as I can always backup to Kernel 113 as long as I don't do a autoremove command.

[William Veliz (wilardo)]

I have the same error with Linux Mint 21.2 Cinnamon with kernel 5.15.0-116-generic and VirtualBox installed from Ubuntu repo (version 6.1.50-dfsg-1~ubuntu1.22.04.1).

[Alan Knepper (al-knepper)]

Upgrading to virtualbox 7.0.20 fixed my system. I'm back on 5.15.0-116 kernel.

[Andre Juanel (ajuanel)]

Same issue here with Ubuntu Mate 22.04. It worked with kernel 5.15.0-112.

The log file says:
ERROR [COM]: aRC=NS_ERROR_INVALID_ARG (0x80070057) aIID={4680b2de-8690-11e9-b83d-5719e53cf1de} aComponent={DisplayWrap} aText={Argument aWidth is invalid (must be aWidth != 0 && aWidth <= 32767)}, preserve=false aResultDetail=0

Waiting for a kernel fix.

[Michael Plotkin (plotkin)]

Just tested the "focal-proposed" kernel version 5.15.0-118 (with "Pre-released updates" enabled) on Ubuntu 20.04 with VBox 6.1.50. Unfortunately the VM didn't work at all with exactly the same symptoms as with "stable" kernel version 5.15.0-116. Was unable to find any workaround so I had to downgrade the kernel version to 5.15.0-113 and to disable further kernel upgrades until a working fix is available.