Thank you for the communication Matias ! On Sun, 22 Mar 2026 at 20:35, Matias Larsson <[email protected]> wrote:
> @Holger: Note that this bug specifically concerns 6.17 kernel version. > Therefore, in order to test the fix, one needs to boot into 6.17 kernel. > > So, you might want to find out why your system boots into 6.14 instead > of 6.17. Some things to check maybe: > > - Which kernel versions are installed on your system. > - Which kernel is GRUB (or whatever bootloader/UEFI you use) configured to > boot. Have there been configuration changes earlier? > > Also, please note that my earlier message is a test report (of sorts), > not an instruction for solving the problem. I made an edit to clarify > this for future. Testing had been requested in this thread, hence I > tested and reported back. > > If you're on Ubuntu 22.04 or lower, then repeating my steps can have > nasty side effects. See https://wiki.ubuntu.com/Testing/EnableProposed > for how to enable '-proposed' updates. For Ubuntu 22.04 and lower there > are additional steps one needs to take. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (2143743). > https://bugs.launchpad.net/bugs/2136499 > > Title: > virtualbox-dkms FTBFS in Noble with the linux-6.17 kernel > > Status in virtualbox package in Ubuntu: > Invalid > Status in virtualbox source package in Noble: > Fix Committed > Status in virtualbox source package in Questing: > Fix Committed > Status in virtualbox source package in Resolute: > Invalid > > Bug description: > [ Impact ] > > DKMS make.log for virtualbox-7.0.16 for kernel 6.17.0-7-generic (x86_64) > Tue Dec 16 20:56:46 UTC 2025 > make: Entering directory '/usr/src/linux-headers-6.17.0-7-generic' > make[1]: Entering directory '/var/lib/dkms/virtualbox/7.0.16/build' > warning: the compiler differs from the one used to build the kernel > The kernel was built by: x86_64-linux-gnu-gcc-13 (Ubuntu > 13.3.0-6ubuntu2~24.04) 13.3.0 > You are using: gcc-13 (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0 > CC [M] vboxdrv/linux/SUPDrv-linux.o > CC [M] vboxdrv/SUPDrv.o > CC [M] vboxdrv/SUPDrvGip.o > CC [M] vboxdrv/SUPDrvSem.o > In file included from vboxdrv/SUPDrv.c:43: > vboxdrv/SUPDrvInternal.h:47:10: fatal error: VBox/cdefs.h: No such file > or directory > 47 | #include <VBox/cdefs.h> > | ^~~~~~~~~~~~~~ > compilation terminated. > In file included from vboxdrv/SUPDrvSem.c:43: > vboxdrv/SUPDrvInternal.h:47:10: fatal error: VBox/cdefs.h: No such file > or directory > 47 | #include <VBox/cdefs.h> > | ^~~~~~~~~~~~~~ > compilation terminated. > make[4]: *** > [/usr/src/linux-headers-6.17.0-7-generic/scripts/Makefile.build:287: > vboxdrv/SUPDrv.o] Error 1 > make[4]: *** Waiting for unfinished jobs.... > make[4]: *** > [/usr/src/linux-headers-6.17.0-7-generic/scripts/Makefile.build:287: > vboxdrv/SUPDrvSem.o] Error 1 > In file included from vboxdrv/linux/SUPDrv-linux.c:42: > vboxdrv/linux/../SUPDrvInternal.h:47:10: fatal error: VBox/cdefs.h: No > such file or directory > 47 | #include <VBox/cdefs.h> > | ^~~~~~~~~~~~~~ > compilation terminated. > In file included from vboxdrv/SUPDrvGip.c:43: > vboxdrv/SUPDrvInternal.h:47:10: fatal error: VBox/cdefs.h: No such file > or directory > 47 | #include <VBox/cdefs.h> > | ^~~~~~~~~~~~~~ > compilation terminated. > make[4]: *** > [/usr/src/linux-headers-6.17.0-7-generic/scripts/Makefile.build:287: > vboxdrv/linux/SUPDrv-linux.o] Error 1 > make[4]: *** > [/usr/src/linux-headers-6.17.0-7-generic/scripts/Makefile.build:287: > vboxdrv/SUPDrvGip.o] Error 1 > make[3]: *** > [/usr/src/linux-headers-6.17.0-7-generic/scripts/Makefile.build:556: > vboxdrv] Error 2 > make[2]: *** [/usr/src/linux-headers-6.17.0-7-generic/Makefile:2016: .] > Error 2 > make[1]: *** [/usr/src/linux-headers-6.17.0-7-generic/Makefile:248: > __sub-make] Error 2 > make[1]: Leaving directory '/var/lib/dkms/virtualbox/7.0.16/build' > make: *** [Makefile:248: __sub-make] Error 2 > make: Leaving directory '/usr/src/linux-headers-6.17.0-7-generic' > > Morover, even if the driver builds, Virtualbox VMs crash on start, with > "Unable to allocate and lock memory", "Error ID: Host Memory Low" and > other errors. > > While the build issue affects only Noble, the VM crash affects both > Noble an Questing. > > [ Test case ] > > In Questing: > - Install virtualbox-dkms: > > $ sudo apt install virtualbox-dkms > > - Load the modules: > > $ sudo modprobe vboxdrv > $ sudo modprobe vboxnetadp > $ sudo modprobe vboxnetflt > > - Create a virtualbox VM and launch it. > > In Noble > - Install the latest linux-6.17 kernel: > > $ sudo apt install linux-generic-hwe-24.04 > > - Install virtualbox-dkms: > > $ sudo apt install virtualbox-dkms > > - Load the modules: > > $ sudo modprobe vboxdrv > $ sudo modprobe vboxnetadp > $ sudo modprobe vboxnetflt > > - Create a virtualbox VM and launch it. > > The same procedure must be repeated on linux-6.8 to test for possible > regressions. > > > [ Regression potential ] > > We may experience regressions in systems that are using the virtualbox > drivers and VMs, especially with kernels >= 6.8 kernel. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/2136499/+subscriptions > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2136499 Title: virtualbox-dkms FTBFS in Noble with the linux-6.17 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/2136499/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
