Debian 9 (stretch), Guru Meditation, emR3Debug: rc=VERR_INVALID_STATE

[Virtuaris]

Dear Support,

trying to setup Virtualbox 6.0.2 (6.0.2-128162~Debian~stretch, installed from official Oracle/Virtualbox Debian repo alongside with Extension Pack Oracle_VM_VirtualBox_Extension_Pack-6.0.2.vbox-extpack) on a HP ProLiant DL360 G6 Server (2 x Intel(R) Xeon(R) CPU L5520 @ 2.27GHz, 82GB ram) using headless installation i always encounter 'Guru Meditation' when i launch a VM.

To minimize possible error causes my last attempt was to boot a VM without storage using a Debian netinstall ISO image, no luck, same game...

I searched the web for parts of the log i considered being relevant (e.g. emR3Debug: rc=VERR_INVALID_STATE) but could not find anything useful yet.

Maybe you have any idea what's going wrong here.

Attached to this post the logfile of an exemplary VM boot process.

In /var/log/kern.log these messages are logged when booting the VM:

Code: Select all

Jan 17 23:04:20 synapse kernel: [628380.846672] vboxdrv: ffffffffc101d020 VMMR0.r0
Jan 17 23:04:21 synapse kernel: [628381.047596] vboxdrv: ffffffffc0000020 VBoxDDR0.r0
Jan 17 23:04:21 synapse kernel: [628381.119791] vboxdrv: ffffffffc0029020 VBoxEhciR0.r0

Thank you so much

bests

Harald

[socratis]

00:00:01.243777   LocalInitScript  <string>  = "/vm/vagrant/haris/VirtualBox/Test/dbgc-init" (cb=44)

What is Vagrant doing there?

00:00:01.388714 Changing the VM state from 'CREATING' to 'CREATED'
00:00:01.395126 Changing the VM state from 'CREATED' to 'POWERING_ON'
00:00:01.395622 Changing the VM state from 'POWERING_ON' to 'RUNNING'
00:00:01.395648 Console: Machine state changed to 'Running'
00:00:01.402548 VMMDev: Guest Log: BIOS: VirtualBox 6.0.2
00:00:01.403029 PCI: Setting up resources and interrupts
00:00:01.404283 SUP: Loaded VBoxEhciR0.r0 (/usr/lib/virtualbox/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/linux.amd64/VBoxEhciR0.r0) at 0xXXXXXXXXXXXXXXXX - ModuleInit at XXXXXXXXXXXXXXXX and ModuleTerm at XXXXXXXXXXXXXXXX
00:00:01.405844 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'
00:00:01.405871 Console: Machine state changed to 'GuruMeditation'
00:00:01.406731 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:00:01.406732 !!
00:00:01.406733 !!         VCPU0: Guru Meditation -79 (VERR_INVALID_STATE)

I usually don't quote that big of a text chunk, but I just wanted to show how really early on the boot process you get the Guru. It seems like when you're trying to load the Ext.Pack, the whole thing comes crumbling down.

Did you see that with 6.0.0 as well? Or 5.2.22/24? Can you try?

[Virtuaris]

What is Vagrant doing there?

I planned to use Vagrant for VM deployment but all actions described in my post were taken on vanilla Virtualbox (VBoxManage or gui).

Did you see that with 6.0.0 as well? Or 5.2.22/24? Can you try?

Downgrading to Virtualbox 5.2 showed me the light and my own stupidity:

Stderr: VBoxManage: error: VT-x is being used by another hypervisor (VERR_VMX_IN_VMX_ROOT_MODE).
VBoxManage: error: VirtualBox can't operate in VMX root mode. Please disable the KVM kernel extension, recompile your kernel and reboot (VERR_VMX_IN_VMX_ROOT_MODE)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole

Indeed KVM/qemu/libvirt is running on the same server. I just was not aware that only one hypervisor may utilize the CPU VT-x extension.
Strange enough that Virtualbox 6.x does not state such a fundamental error in plain words...

socratis, i'm truly sorry for waisting your time, Thx a lot your for your willingness to help me out anyway.

cheers

Harald

[socratis]

Indeed KVM/qemu/libvirt is running on the same server. I just was not aware that only one hypervisor may utilize the CPU VT-x extension.

Hmm... That's a really interesting situation! I wonder why the log doesn't show anything related, and/or why just the guru instead of the classical warning-then-guru situation. And there's no sign that VT-x was not available:

00:00:01.244662 HM: HMR3Init: VT-x w/ nested paging hw support
00:00:01.388209   HVP - Hypervisor Present (we're a guest)                = 1 (0)
00:00:01.388512 *********************** VT-x features ***********************
00:00:01.388514 Nested hardware virtualization - VMX features

I wonder why in the seven kingdoms this is showing in the logs. We might need some feedback from the developers.

i'm truly sorry for waisting your time

Not at all, on the contrary. In fact your analysis revealed a situation that we should investigate further!

[Virtuaris]

In fact your analysis revealed a situation that we should investigate further!

Ok, i'll happily provide more details if requested, np...

I wonder why in the seven kingdoms this is showing in the logs. We might need some feedback from the developers.

I admit i stopped reading the logs after i got the Vbox 5.2 log message since for me it was clear that this must be the cause for 6.x to crash as well.