[Solved] Running 6.0.14 on Fedora 30 fails with KVM installed

[solarflow]

I had this running fine a little while ago, and now I can't get any virtualbox VMs to run, each time a power one up, or create a new VM I get the dreaded message: "A critical error has occurred while running the virtual machine ..."

Looking at the logs I don't see any indication what is wrong. I have the latest virtualbox 6.0.14 with the extention pack installed. The last line in the log just says: "Aborting startup due to invalid machine state detected: 1"

I tried running this to see if it would help, doesn't work.:

# /usr/lib/virtualbox/vboxdrv.sh setup
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: failed: Cannot unload module vboxnetflt.


# systemctl status vboxdrv.service
● vboxdrv.service - VirtualBox Linux kernel module
   Loaded: loaded (/usr/lib/virtualbox/vboxdrv.sh; enabled; vendor preset: disabled)
   Active: active (exited) since Mon 2019-12-02 00:06:40 PST; 25min ago
  Process: 3575 ExecStart=/usr/lib/virtualbox/vboxdrv.sh start (code=exited, status=0/SUCCESS)

 systemd[1]: Starting VirtualBox Linux kernel module...
 vboxdrv.sh[3575]: vboxdrv.sh: Starting VirtualBox services.
 vboxdrv.sh[3586]: Starting VirtualBox services.
 systemd[1]: Started VirtualBox Linux kernel module.

[socratis]

Looking at the logs I don't see any indication what is wrong.

You can either continue doing that, or you can ZIP a VBox.log and let us have a look as well...

We need to see a complete VBox.log, from a complete VM run, where the problem occurs:

• Start the VM from cold-boot (not from a paused or saved state) / Observe or recreate the problem / Shutdown the VM (force close it if you have to).
• With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
• Save only the first "VBox.log", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.

[solarflow]

Thanks, I have attached the log. What I think i'm seeing is that hardware virtualization might be the problem, if that right, I don't know why the only thing that comes to mind could be something for spectre/meltdown mitigation, etc.

Code: Select all

# grep -E 'vme' /proc/cpuinfo
flags		: fpu [b]vme[/b] de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid dtherm ida flush_l1d

Code: Select all

# uname -a
Linux localhost 5.3.13-200.fc30.x86_64 #1 SMP Mon Nov 25 23:02:12 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Code: Select all

# lsmod | grep box
vboxpci                28672  0
vboxnetadp             28672  0
vboxnetflt             32768  0
vboxdrv               499712  3 vboxpci,vboxnetadp,vboxnetflt

[socratis]

I couldn't find anything wrong with your VBox.log. I even checked the CPU capabilities between your and my setup, nothing...

[fth0]

What I think i'm seeing is that hardware virtualization might be the problem

That may indeed be the problem. At least two Google search results for the Guru Meditation -79 (VERR_INVALID_STATE) error point to cases where qemu-kvm was installed in the host OS and the VM crashed very early (after RUNNING for about 20 ms). Please uninstall qemu-kvm and check if the problem persists.

[solarflow]

your hunch was right, kvm was interfering. Its working again now.

Thanks for the help!

[socratis]

Marking as [Solved].

Changing the title slightly from "Running 6.0.14 on Fedora 30 fails" to "Running 6.0.14 on Fedora 30 fails with KVM installed" to better reflect the situation.