I have VB 7.0.4 running on an Ubuntu 22.04 host. VB 7.0.4 has been running for several months perfectly.
I recently upgraded to VB 7.0.6, however that stopped me from being able to ssh into my VMs.
So I removed VB and reinstalled 7.0.4.
Following that I cannot start any VM, or even create a new Centos 7 VM. I see a "critical error" message with advice to contact this forum:
An excerpt from the VBox.log file shows this:
Code: Select all
00:00:01.020905 Console: Machine state changed to 'Running'
00:00:01.021210 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'
00:00:01.021232 Console: Machine state changed to 'Stuck'
00:00:01.022323 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:00:01.022325 !!
00:00:01.022325 !! VCPU0: Guru Meditation -37 (VERR_NOT_SUPPORTED)
00:00:01.022340 !!
00:00:01.022355 !!
00:00:01.022356 !! {mappings, <NULL>}
00:00:01.022357 !!
00:00:01.022366 !!
00:00:01.022366 !! {hma, <NULL>}
00:00:01.022367 !!
00:00:01.022368 !!
00:00:01.022369 !! {cpumguest, verbose}
00:00:01.022370 !!
The complete log file is attached.
Does any one have a clue what may cause this?
Thanks - AdamL