Maybe, someone can help an old long time virtualbox user, who does not know what else to try.
I experience some strange "guru meditation" on a Linux host (OpenSUSE Leap 15) and VirtualBox 6.1.2.
The machine is a Xeon 2650v2 with 32GB of RAM.VCPU1: Guru Meditation -4005 (VERR_VMX_UNABLE_TO_START_VM)
There are already five virtual machines running (without any problems) with different Windows and Linux versions.
I installed a Windows10-1909 update on a Windows7 virtual machine and need to install a "MSSQL Server Express".
Each time (reproducable!) the setup is running, the machine switches to guru meditation and is dead.
The CPU is running at 200% (Linux command "top -c") from this point in time (two cores).
Now the misterious thing: On the host, there are already two Windows10 machines with identical configuration (except hard disk and the uuids).
Only this updated machine reproducably crashes on the MSSQL setup.
I already tried (hopefully all of) the many advices here in the forum and linked by google:
- try different hypervisor settings
- try only one CPU
- try more or less RAM
- change virtualization settings
- change GPU and VRAM settings
- change PAE and pages settings
The problem persists. Before I switch back to an older virtualbox release, I would like to try and maybe get some usable advice from the many professionals here in the forums.
Even then it is possible that also the older release 6.0.x crashes; I did not try that, yet.
The VBoxLog is attached to this message. I hope it includes all the necessary information.
Please let me know, if anything else is needed for finding some hints in the right direction.