Quick backstory: I added a wifi 6E card to a Bullseye OS laptop. To recognize the card I had to upgrade the linux image and headers as show below and confirmed using "uname -a". 6.0.0-0.deb11.2-rt-amd64 #1 SMP PREEMPT_RT Debian 6.0.3-1~bpo11+1 (2022-10-29) x86_64 GNU/Linux The upgraded image and headers came from Debian backports and were installed using apt-get. I have several bare metal OS's using Bullseye and this image and they are perfect bringing my new network PCI card to 100% function. Problem: on the machine running VirtualBox the VM's won't start and are stuck at starting VM. Hmmmmm. I noticed that Oracle released 7.0.4 and decided to try that. Formerly I was running the latest 6.0+ version but it didn't start either, which is why I removed 6.0+ and installed 7.0.4, hoping the issue would go away. It didn't. For reference I double checked VirtualBox 7.0.4 by restarting my Bullseye host AND using the advanced menu mounted the OLD kernel. Running the old kernel/image VBox 7.0.4 runs perfectly and the VM's mount as usual. So VBox 7.0.4 is not the issue. As described above; the lower/older kernel/image doesn't recognize the new PCI card so no internet ---- of course that won't fly! Does anyone have an idea of how I might be able to "build or re-build" something in VBox that would resolve where I am stuck? Deleting VBox and then starting from scratch with installing the new 7.0.4 version didn't do the trick. I would really appreciate someone coming along side me with ideas.
I'm not running Debian but here is the relevant wiki site which includes a troubleshoot section. For Bullseye the Fasttrack Repository must be added, this applies to the Guest Additions as well.
Good find summerheat. I suspect that linux headers for that particular may not be installed. Any partcular reason you use rt version instead of default one? Does it work with regular kernel (without rt)?
Guys, thank you for the help and suggestions. For now; I lowered my kernel back to 5.10+ and located some Intel drivers that make my card work decently. VirtualBox immediately started working again when I ditched the kernel mentioned above. The FastTrack link above shows promise. I am hoping to jump back on this project again over the holiday break I have coming up.
