Bug ID | 1217342 |
---|---|
Summary | VirtualBox: Starting VM hangs if hosts system uses newer kernel |
Classification | openSUSE |
Product | openSUSE Distribution |
Version | Leap 15.5 |
Hardware | x86-64 |
OS | openSUSE Leap 15.5 |
Status | NEW |
Severity | Normal |
Priority | P5 - None |
Component | Virtualization:Other |
Assignee | virt-bugs@suse.de |
Reporter | ceggers@arri.de |
QA Contact | qa-bugs@suse.de |
Target Milestone | --- |
Found By | --- |
Blocker | --- |
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.