Host goes into Guru Mediation after multiple installs/uninstalls of VirtualBox 6.1

[wgjames]

I am running a Ubuntu 20.04 guest on an Ubuntu 22.04 host. I tried upgrading from VirtualBox 6.1 to 7.0, but the cut/paste did not work even though I installed the VirtualBox 7.0 extension back and enabled the guest additions. So I then uninstalled VirtualBox 7.0 and reinstalled VirtualBox 6.1.

This required a couple of installs/uninstalls but I finally got the installation on the host side correct. lsmod shows the following:

james@ThinkPad-W530:~/Downloads$ lsmod | grep vbox
vboxnetadp 28672 0
vboxnetflt 28672 0
vboxdrv 573440 2 vboxnetadp,vboxnetflt

systemctl status shows the following:

james@ThinkPad-W530:~/Downloads$ systemctl status of vboxdrv
● <vbox service> - VirtualBox Linux kernel module
Loaded: loaded (/usr/lib/virtualbox/vboxdrv ; enabled; vendor preset: enabled)
Active: active (exited) since Tue 2024-07-16 14:03:05 PDT; 8min ago
Process: 98819 ExecStart=/usr/lib/virtualbox/vboxdrv start (code=exited, status=0/SUCCESS)
CPU: 358ms

Jul 16 14:03:05 ThinkPad-W530 systemd[1]: Starting VirtualBox Linux kernel module...
Jul 16 14:03:05 ThinkPad-W530 vboxdrv[98819]: vboxdrv : Starting VirtualBox services.
Jul 16 14:03:05 ThinkPad-W530 systemd[1]: Started VirtualBox Linux kernel module.

The VirtualBox GUI Help window shows 6.1.50 r161033 (Qt 5.15.3) installed.

But none of my VMs will boot.

I've attached the part of the log in which the VM goes into Guru Mediation mode (the full log is too large). Can someone help?

jak

[multiOS]

A complete 'zipped' copy of the VBox.Log might be more informative, as it should be possible to identify if there are any configuration issues that could be linked to the Guru Meditation error. A copy of the VBoxHardening.log (if one exists) might also help with the identification of any possible software conflicts.

An initial Forum search for

VCPU0: Guru Meditation -2708 (VERR_VMM_SET_JMP_ABORTED_RESUME)

turned up a couple of previous reports of the same error, but they both were from users of Windows Hosts and involved an identified conflict with the Avast! security software, which is unlikely in your case (Linux Host), but it might point to a similar software conflict with some (so far) unidentified Linux software.

Please note that if this does turn out to be an issue which is specific to VirtualBox 6.1.50, it's unlikely to get a "fix" as Oracle support for the 6.1.xx series finally ended with the release of 6.1.50. Did the 7.0.xx version you tried exhibit any problems other than the Copy/Paste issue you've mentioned?

[wgjames]

As a followup, I sorted through the log and found this:

00:00:01.364483 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

However, when I do VBoxManage showvminfo on the VM, I see this:
Recording enabled: no
Recording screens: 1
Screen 0:
Enabled: yes
ID: 0
Record video: yes
Record audio: no
Destination: File
File: /home/james/VirtualBox/VirtualBox_VMs/base-vm-1/base-vm-1-screen0.webm
Options: vc_enabled=true,ac_enabled=false,ac_profile=med
Video dimensions: 1024x768
Video rate: 512kbps
Video FPS: 25fps
The video dimensions look fine.
jak

[wgjames]

Thanx for the reply!

Please note that if this does turn out to be an issue which is specific to VirtualBox 6.1.50, it's unlikely to get a "fix" as Oracle support for the 6.1.xx series finally ended with the release of 6.1.50. Did the 7.0.xx version you tried exhibit any problems other than the Copy/Paste issue you've mentioned?

The guest window failed to resize and move in addition to the Copy/Paste issue. I am not opposed to switching to 7.0, but I cannot work without having full functionality for the guest window and Copy/Paste between the guest and host.

As, I posted a followup, there seems to be a problem with the guest window width being improperly set. The log has the following in it:


00:00:01.178832 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
00:00:01.179511 !!
<rest of log including Guru Mode>
00:00:06.174355 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={4680b2de-8690-11e9-b83d-5719e53cf1de} aComponent={DisplayWrap} aText={The console is not powered up (setVideoModeHint)}, preserve=false aResultDetail=0
00:00:06.174940 GUI: Aborting startup due to invalid machine state detected: 1

Which is the last line in the log. When I check the VM configuration using VBoxManage, it shows the following:
Recording enabled: no
Recording screens: 1
Screen 0:
Enabled: yes
ID: 0
Record video: yes
Record audio: no
Destination: File
File: /home/james/VirtualBox/VirtualBox_VMs/base-vm-1/base-vm-1-screen0.webm
Options: vc_enabled=true,ac_enabled=false,ac_profile=med
Video dimensions: 1024x768
Video rate: 512kbps
Video FPS: 25fps

It indicates that video recording is on even when I set it to off by using VBoxManage and if I check the base-vm-1.vbox file, it is set to off.

A couple other notes. Because apt install recommended it, I installed qemu

I have attached the zipped log file.

jak

[LalaK]

I have this exact same issue. Running Virtual Box 6.1.50 on Ubuntu 22.04. The VMs say started, and the process never dies, but it doesn't show up under the runningvms list.

Did you find a fix?

[wgjames]

So I removed VirtualBox 6.1 and installed 7.0 and the VMs now boot.

However, even though I've installed the guest additions and the extension for 7.0, copy/paste between the host and guest does not seem to work.

Any ideas?

jak

[wgjames]

So I think I have my problems solved. If I click on File -> Preferences->Display in the VirtualBox GUI and check the box labelled Raise Window Under Mouse Pointer the virtual machine window takes the focus when the mouse is over it and cut/paste seem to work.

Thanx to multios for his reply. VirtuBox 7.0.20 seems to be working for me now!

jak

[holgermw]

I have the same issue. Problems were starting after rebooting my Ubuntu and changing it to the new kernel version 5.15.0-122. So i reverted to the last kernel version before and volá ... VirtualBox 6.1.50 is running again!
Hope this helps anyone...

[deanpm]

I have the same issue. Problems were starting after rebooting my Ubuntu and changing it to the new kernel version 5.15.0-122. So i reverted to the last kernel version before and volá ... VirtualBox 6.1.50 is running again!
Hope this helps anyone...

Eight long hours I've been battling with this. Was convinced my vdi was corrupted so lost hours down a rabbit hole figuring out how to mount, check, repair my image. Eventually decided to install vbox and a fresh vm on another linux box (same up-to-date kernel image) and had exactly the same issue which was my first clue that this wasn't a corrupted vdi. As you suggested, I reverted from 5.15.0-116 to 5.15.0-113 and everything is magically working again.

Thank you so much for your post. Hugely appreciated.