Bug 1217342

Summary: VirtualBox: Starting VM hangs if hosts system uses newer kernel
Product: [openSUSE] openSUSE Distribution Reporter: Christian Eggers <ceggers>
Component: Virtualization:OtherAssignee: Larry Rainey <llrainey15>
Status: NEW --- QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None    
Version: Leap 15.6   
Target Milestone: ---   
Hardware: x86-64   
OS: openSUSE Leap 15.5   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: dmesg output after trying to start a VirtualBox VM

Description Christian Eggers 2023-11-20 15:34:16 UTC
Created attachment 870854 [details]
dmesg output after trying to start a VirtualBox VM

Machine: DELL Precision 5680

In order to get sound on this machine running, I was forced to install
a contemporary kernel (6.6.0-lp155.8) from the Kernel:stable:Backport:standard repository (sound works fine after installing this kernel, latest Alsa libs AND sof-firmware).

Unfortunately, VirtualBox runs not fine at all. I installed the KMP (in the same version) from Kernel:stable:Backport:KMP:standard and VirtualBox starts without complaining about missing modules (and I see vboxnetadp, vboxnetflt and vboxdrv in the output of lsmod).

But when I try to run a virtual machine, the sidebar shows only a progress bar "VM hochfahren ..." , stuck at 20%. Additionally I get much output in the kernel log (see attached file). I have the same problem with different virtual machines (Windows 11, openSUSE).

When booting the host system with the openSUSE Leap 15.5 stock kernel (currently 5.14.21), VirtualBox VMs run fine.
Comment 1 Larry Rainey 2023-11-21 13:28:22 UTC
On Tumbleweed, I have no issues on a Dell 7000 with a Gen 12 i7 with the 6.6.1 kernel as Host or Guest.
 
user@LLR3:~> uname -a
Linux LLR3 6.6.1-1-default #1 SMP PREEMPT_DYNAMIC Thu Nov  9 05:27:56 UTC 2023 (1fcc265) x86_64 x86_64 x86_64 GNU/Linux
user@LLR3:~> psg virtual
root      1386     1  0 Nov14 ?        00:00:10 /usr/lib/virtualbox/vboxwebsrv --background
root      1390     1  0 Nov14 ?        00:00:02 /usr/lib/virtualbox/VBoxXPCOMIPCD
root      1413     1  0 Nov14 ?        00:01:27 /usr/lib/virtualbox/VBoxSVC --auto-shutdown
user     14096     1  0 Nov14 ?        00:42:44 /usr/lib/virtualbox/VBoxXPCOMIPCD
user     14102     1  1 Nov14 ?        03:12:23 /usr/lib/virtualbox/VBoxSVC --auto-shutdown
user     14130 14074  0 Nov14 ?        00:16:25 /usr/lib/virtualbox/VirtualBox6
user     28091 14102  8 07:10 ?        00:00:57 /usr/lib/virtualbox/VirtualBoxVM --comment Mint --startvm da7f2283-4722-4d94-890a-93c03e4b8178 --no-startvm-errormsgbox
user     28324 14102  8 07:11 ?        00:01:01 /usr/lib/virtualbox/VirtualBoxVM --comment Manjaro --startvm 1222f84b-36a0-4b58-b84a-526d7a225af5 --no-startvm-errormsgbox
user     28564 14102  6 07:11 ?        00:00:44 /usr/lib/virtualbox/VirtualBoxVM --comment Ubuntu --startvm d5db27f0-e3b3-4e18-84a2-2d999edf7504 --no-startvm-errormsgbox
user     28790 14102  8 07:11 ?        00:00:58 /usr/lib/virtualbox/VirtualBoxVM --comment tumbleweed --startvm 4713d533-f86c-463c-8da8-ee67427a1fed --no-startvm-errormsgbox
user     29062 14102 45 07:11 ?        00:05:02 /usr/lib/virtualbox/VirtualBoxVM --comment win11 --startvm ce4f8eb9-4894-4373-89fb-dbc625899167 --no-startvm-errormsgbox
user     29383 14102  7 07:11 ?        00:00:50 /usr/lib/virtualbox/VirtualBoxVM --comment suse15 --startvm 7e154200-c32c-40ac-a01d-1b7632c55598 --no-startvm-errormsgbox
user     29680 14102 10 07:11 ?        00:01:09 /usr/lib/virtualbox/VirtualBoxVM --comment twkde --startvm 25ebb4a2-a3af-4a44-a3da-88fc2adf06dc --no-startvm-errormsgbox
user     29976 14102 14 07:11 ?        00:01:33 /usr/lib/virtualbox/VirtualBoxVM --comment fedora --startvm d6da2ee7-920b-413f-8f9c-f944c8a6fa76 --no-startvm-errormsgbox
user     30268 14102 13 07:12 ?        00:01:23 /usr/lib/virtualbox/VirtualBoxVM --comment gnome --startvm 04aa4c99-1973-469c-8c57-8d44d2628ca6 --no-startvm-errormsgbox
user@LLR3:~>

I suggest removing and reinstalling virtualbox in Tumbleweed. If you are using the 6.6.0 in Leap - that is not supported. Only in Tumbleweed.
Comment 2 Christian Eggers 2023-12-07 10:48:06 UTC
> I suggest removing and reinstalling virtualbox in Tumbleweed. If you are
> using the 6.6.0 in Leap - that is not supported. Only in Tumbleweed.

I just installed Tumbleweed on this machine and can confirm that VirtualBox works here.
Comment 3 Christian Eggers 2024-04-08 13:39:12 UTC
Same problem on current openSUSE-15.6 beta (with stock kernel)!

I just installed the latest beta of openSUSE-15.6. Here kernel 6.4 is shipped.
I also had to manually add the openSUSE signing key with mokutil.

After that I started VirtualBox and created a new machine (with default settings). Again the machines startup freezes at 20% and it is not possible to terminate the VM / close the VirtualBox window.

This should definitely be fixed until openSUSE-15.6 GA.