Virtualbox dkms build fails with kernel 6.17

Support and Help
, ,
1

Ubuntu Version

Ubuntu 24.04 LTS

Desktop Environment (if applicable)

GNOME

Problem Description

Hello my friends,
This follows Kernel panic in 7.0, works in 6.14 ( Kernel panic in 7.0, works in 6.14 - #23 by jjmeric solved) - this is similar but different:

I need a bit more help for my other computer “Maxwell” which I use for heavy work like building the Corpus of Mande languages. I expected the problem would be the same, with the Tuxedo Motorcomm driver, but no, it’s similar but different (see below). Fixes or ideas welcome!

JJ

I was not aware that I had Oracle’s Virtual Box installed.
I routinely use python virtual environments (venv) - does that requires Virtual Box ???
How can I check what is using Virtual Box ?
How can I get rid of that Kernel Panic error and start again nicely with an updated system ?

Relevant System Information

Rapport d’informations du système

Détails du compte rendu

  • Date de génération : 2026-09-14 14:50:13

Informations liées au matériel :

  • Modèle du matériel : ASUS ROG STRIX B760-I GAMING WIFI
  • Mémoire : 32,0 Gio
  • Processeur : Intel® Core™ i9-14900T × 32
  • Carte graphique : Intel® Graphics (RPL-S)
  • Capacité du disque : 512,1 Go

Informations liées au logiciel :

  • Version du micrologiciel : 1820
  • Nom du système d’exploitation : Ubuntu 24.04.3 LTS
  • Construction du système d’exploitation : (null)
  • Type de système d’exploitation : 64 bits
  • Version de GNOME : 46
  • Système de fenêtrage : X11
  • Version du noyau : Linux 6.14.0-37-generic

Error Messages / Logs

`cat /var/lib/dkms/virtualbox/7.0.16/build/make.log`
`DKMS make.log for virtualbox-7.0.16 for kernel 6.17.0-35-generic (x86_64)`
`lun. 14 sept. 2026 11:09:20 CEST`
`make : on entre dans le répertoire « /usr/src/linux-headers-6.17.0-35-generic »`
`make[1] : on entre dans le répertoire « /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.1) 13.3.0`
`You are using: gcc-13 (Ubuntu 13.3.0-6ubuntu2~24.04.1) 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`
`CC [M] vboxdrv/SUPDrvTracer.o`
`CC [M] vboxdrv/SUPLibAll.o`
`CC [M] vboxdrv/common/string/strformatrt.o`
`CC [M] vboxdrv/combined-agnostic1.o`
`In file included from vboxdrv/linux/SUPDrv-linux.c:42:`
`vboxdrv/linux/../SUPDrvInternal.h:47:10: fatal error: VBox/cdefs.h: Aucun fichier ou dossier de ce nom`
`47 | #include <VBox/cdefs.h>`
`| ^~~~~~~~~~~~~~`
`compilation terminated.`
`CC [M] vboxdrv/combined-agnostic2.o`
`In file included from vboxdrv/SUPDrv.c:43:`
`vboxdrv/SUPDrvInternal.h:47:10: fatal error: VBox/cdefs.h: Aucun fichier ou dossier de ce nom`
`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: Aucun fichier ou dossier de ce nom`
`47 | #include <VBox/cdefs.h>`
`| ^~~~~~~~~~~~~~`
`compilation terminated.`
`CC [M] vboxdrv/combined-os-specific.o`
`make[4]: *** [/usr/src/linux-headers-6.17.0-35-generic/scripts/Makefile.build:287 : vboxdrv/linux/SUPDrv-linux.o] Erreur 1`
`make[4]: *** Attente des tâches non terminées…`
`In file included from vboxdrv/SUPDrvSem.c:43:`
`vboxdrv/SUPDrvInternal.h:47:10: fatal error: VBox/cdefs.h: Aucun fichier ou dossier de ce nom`
`47 | #include <VBox/cdefs.h>`
`| ^~~~~~~~~~~~~~`
`compilation terminated.`
`make[4]: *** [/usr/src/linux-headers-6.17.0-35-generic/scripts/Makefile.build:287 : vboxdrv/SUPDrv.o] Erreur 1`
`make[4]: *** [/usr/src/linux-headers-6.17.0-35-generic/scripts/Makefile.build:287 : vboxdrv/SUPDrvGip.o] Erreur 1`
`make[4]: *** [/usr/src/linux-headers-6.17.0-35-generic/scripts/Makefile.build:287 : vboxdrv/SUPDrvSem.o] Erreur 1`
`In file included from vboxdrv/SUPDrvTracer.c:43:`
`vboxdrv/SUPDrvInternal.h:47:10: fatal error: VBox/cdefs.h: Aucun fichier ou dossier de ce nom`
`47 | #include <VBox/cdefs.h>`
`| ^~~~~~~~~~~~~~`
`compilation terminated.`
`make[4]: *** [/usr/src/linux-headers-6.17.0-35-generic/scripts/Makefile.build:287 : vboxdrv/SUPDrvTracer.o] Erreur 1`
`vboxdrv/SUPLibAll.c:41:10: fatal error: VBox/sup.h: Aucun fichier ou dossier de ce nom`
`41 | #include <VBox/sup.h>`
`| ^~~~~~~~~~~~`
`compilation terminated.`
`make[4]: *** [/usr/src/linux-headers-6.17.0-35-generic/scripts/Makefile.build:287 : vboxdrv/SUPLibAll.o] Erreur 1`
`vboxdrv/common/string/strformatrt.c:42:10: fatal error: iprt/string.h: Aucun fichier ou dossier de ce nom`
`42 | #include <iprt/string.h>`
`| ^~~~~~~~~~~~~~~`
`compilation terminated.`
`make[4]: *** [/usr/src/linux-headers-6.17.0-35-generic/scripts/Makefile.build:287 : vboxdrv/common/string/strformatrt.o] Erreur 1`
`vboxdrv/combined-agnostic2.c:38:10: fatal error: internal/iprt.h: Aucun fichier ou dossier de ce nom`
`38 | #include “internal/iprt.h”`
`| ^~~~~~~~~~~~~~~~~`
`compilation terminated.`
`make[4]: *** [/usr/src/linux-headers-6.17.0-35-generic/scripts/Makefile.build:287 : vboxdrv/combined-agnostic2.o] Erreur 1`
`vboxdrv/combined-os-specific.c:38:10: fatal error: the-linux-kernel.h: Aucun fichier ou dossier de ce nom`
`38 | #include “the-linux-kernel.h”`
`| ^~~~~~~~~~~~~~~~~~~~`
`compilation terminated.`
`make[4]: *** [/usr/src/linux-headers-6.17.0-35-generic/scripts/Makefile.build:287 : vboxdrv/combined-os-specific.o] Erreur 1`
`vboxdrv/combined-agnostic1.c:38:10: fatal error: internal/iprt.h: Aucun fichier ou dossier de ce nom`
`38 | #include “internal/iprt.h”`
`| ^~~~~~~~~~~~~~~~~`
`compilation terminated.`
`make[4]: *** [/usr/src/linux-headers-6.17.0-35-generic/scripts/Makefile.build:287 : vboxdrv/combined-agnostic1.o] Erreur 1`
`make[3]: *** [/usr/src/linux-headers-6.17.0-35-generic/scripts/Makefile.build:544 : vboxdrv] Erreur 2`
`make[2]: *** [/usr/src/linux-headers-6.17.0-35-generic/Makefile:2016 : .] Erreur 2`
`make[1]: *** [/usr/src/linux-headers-6.17.0-35-generic/Makefile:248 : __sub-make] Erreur 2`
`make[1] : on quitte le répertoire « /var/lib/dkms/virtualbox/7.0.16/build »`
`make: *** [Makefile:248 : __sub-make] Erreur 2`
`make : on quitte le répertoire « /usr/src/linux-headers-6.17.0-35-generic »`
`useradmin@Maxwell:~$`

What I’ve Tried

this happened after an update of Ubuntu
Default GNU GRUB automatic login stops at Kernel Panic VFS : Unable to mount root fs on unknown block (0,0)
I can still boot with GRUB Advanced options → kernel 6.14

sudo dkms status
virtualbox/7.0.16, 6.14.0-37-generic, x86_64: installed

Kernel panic in 7.0, works in 6.14
Ubuntu Weekly Newsletter Issue 962
2

Could you use a slightly more descriptive title ?
We’ll soon have a “Kernel panic” collection of topics otherwise …

Something like: “Virtualbox dkms build fails with kernel 6.17” would describe the problem better and not have us end up with a list of slightly identical topic titles all over the place.

2 Likes
4

I edited the title and added tags.

@ogra is right about a descriptive title; it will also help you find better help from the volunteer users.

Thanks

1 Like
5

ogra, rubi1200

thanks, fine with me, thank you for the title update and tags

1 Like
6

Python venv does not use VirtualBox at all
vboxmanage list vms - to check if you have any VMs

The unknown-block(0,0) panic happened because virtualbox-dkms failed to build on kernel 6.17, which broke the apt hook before update-initramfs could run.

Boot into 6.14 from GRUB, purge virtualbox-dkms, and rebuild the initrd:

sudo apt purge virtualbox-dkms
sudo dpkg --configure -a
sudo update-initramfs -u -k all
sudo update-grub

Then reboot into 6.17…

7

steelf, you are my hero for the last two days! bravo! I owe you a cup of champagne!

All worked well : No vms was listed, so I followed your instructions, see below.

There’s one hiccup : I see no GRUB menu when starting the system, is this the normal situation when the base kernel works OK ?

JJ

useradmin@Maxwell:~$ sudo apt purge virtualbox-dkms
[sudo] Mot de passe de useradmin :
Lecture des listes de paquets… Fait
Construction de l’arbre des dépendances… Fait
Lecture des informations d’état… Fait
Le paquet suivant a été installé automatiquement et n’est plus nécessaire :
dkms
Veuillez utiliser « sudo apt autoremove » pour le supprimer.
Les paquets supplémentaires suivants seront installés :
kbuild module-assistant virtualbox virtualbox-qt virtualbox-source
Paquets suggérés :
vde2 virtualbox-guest-additions-iso
Les paquets suivants seront ENLEVÉS :
virtualbox-dkms*
Les NOUVEAUX paquets suivants seront installés :
kbuild module-assistant virtualbox-source
Les paquets suivants seront mis à jour :
virtualbox virtualbox-qt
2 mis à jour, 3 nouvellement installés, 1 à enlever et 473 non mis à jour.
4 partiellement installés ou enlevés.
Il est nécessaire de prendre 1 726 ko/58,5 Mo dans les archives.
Après cette opération, 869 ko d’espace disque seront libérés.
Souhaitez-vous continuer ? [O/n] O
Réception de :1 http://fr.archive.ubuntu.com/ubuntu noble/universe amd64 kbuild amd64 1:0.1.9998svn3604+dfsg-1 [755 kB]
Réception de :2 http://fr.archive.ubuntu.com/ubuntu noble/universe amd64 module-assistant all 0.11.11ubuntu1 [92,1 kB]
Réception de :3 http://fr.archive.ubuntu.com/ubuntu noble-updates/multiverse amd64 virtualbox-source amd64 7.0.16-dfsg-2ubuntu1.3 [878 kB]
1 726 ko réceptionnés en 0s (30,3 Mo/s)
Sélection du paquet kbuild précédemment désélectionné.
(Lecture de la base de données… 233057 fichiers et répertoires déjà installés.)
Préparation du dépaquetage de …/kbuild_1%3a0.1.9998svn3604+dfsg-1_amd64.deb …
Dépaquetage de kbuild (1:0.1.9998svn3604+dfsg-1) …
Sélection du paquet module-assistant précédemment désélectionné.
Préparation du dépaquetage de …/module-assistant_0.11.11ubuntu1_all.deb …
Dépaquetage de module-assistant (0.11.11ubuntu1) …
Sélection du paquet virtualbox-source précédemment désélectionné.
Préparation du dépaquetage de …/virtualbox-source_7.0.16-dfsg-2ubuntu1.3_amd64.deb …
Dépaquetage de virtualbox-source (7.0.16-dfsg-2ubuntu1.3) …
dpkg: virtualbox-dkms : problèmes de dépendance, mais suppression comme demandé :
virtualbox dépend de virtualbox-dkms (>= 7.0.16-dfsg-2ubuntu1.1) | virtualbox-source (>= 7.0.16-dfsg-2ubuntu1.1) | virtualbox-modules; cependant :
Le paquet virtualbox-dkms doit être supprimé.
Le paquet virtualbox-source n’est pas encore configuré.
Le paquet virtualbox-modules n’est pas installé.
Le paquet virtualbox-dkms qui fournit virtualbox-modules doit être supprimé.
virtualbox dépend de virtualbox-dkms (>= 7.0.16-dfsg-2ubuntu1.1) | virtualbox-source (>= 7.0.16-dfsg-2ubuntu1.1) | virtualbox-modules; cependant :
Le paquet virtualbox-dkms doit être supprimé.
Le paquet virtualbox-source n’est pas encore configuré.
Le paquet virtualbox-modules n’est pas installé.
Le paquet virtualbox-dkms qui fournit virtualbox-modules doit être supprimé.

(Lecture de la base de données… 233349 fichiers et répertoires déjà installés.)
Suppression de virtualbox-dkms (7.0.16-dfsg-2ubuntu1.1) …
Module virtualbox-7.0.16 for kernel 6.14.0-37-generic (x86_64).
Before uninstall, this module version was ACTIVE on this kernel.

vboxdrv.ko.zst:

  • Uninstallation
    • Deleting from: /lib/modules/6.14.0-37-generic/updates/dkms/
  • Original module
    • No original module was found for this module on this kernel.
    • Use the dkms install command to reinstall any previous module version.

vboxnetadp.ko.zst:

  • Uninstallation
    • Deleting from: /lib/modules/6.14.0-37-generic/updates/dkms/
  • Original module
    • No original module was found for this module on this kernel.
    • Use the dkms install command to reinstall any previous module version.

vboxnetflt.ko.zst:

  • Uninstallation

    • Deleting from: /lib/modules/6.14.0-37-generic/updates/dkms/

  • Original module

    • No original module was found for this module on this kernel.
    • Use the dkms install command to reinstall any previous module version.
      depmod…
      Deleting module virtualbox-7.0.16 completely from the DKMS tree.
      (Lecture de la base de données… 233061 fichiers et répertoires déjà installés.)
      Préparation du dépaquetage de …/virtualbox-qt_7.0.16-dfsg-2ubuntu1.3_amd64.deb …
      Dépaquetage de virtualbox-qt (7.0.16-dfsg-2ubuntu1.3) sur (7.0.16-dfsg-2ubuntu1.1) …
      Préparation du dépaquetage de …/virtualbox_7.0.16-dfsg-2ubuntu1.3_amd64.deb …
      Dépaquetage de virtualbox (7.0.16-dfsg-2ubuntu1.3) sur (7.0.16-dfsg-2ubuntu1.1) …
      Paramétrage de linux-headers-6.17.0-35-generic (6.17.0-35.35~24.04.1) …
      /etc/kernel/header_postinst.d/dkms:

  • dkms: running auto installation service for kernel 6.17.0-35-generic

  • dkms: autoinstall for kernel 6.17.0-35-generic
    …done.
    Paramétrage de kbuild (1:0.1.9998svn3604+dfsg-1) …
    Paramétrage de linux-image-6.17.0-35-generic (6.17.0-35.35~24.04.1) …
    Paramétrage de module-assistant (0.11.11ubuntu1) …
    Paramétrage de linux-headers-generic-hwe-24.04 (6.17.0-35.35~24.04.1) …
    Paramétrage de linux-generic-hwe-24.04 (6.17.0-35.35~24.04.1) …
    Paramétrage de virtualbox-source (7.0.16-dfsg-2ubuntu1.3) …
    Paramétrage de virtualbox (7.0.16-dfsg-2ubuntu1.3) …
    Job for virtualbox.service failed because the control process exited with error code.
    See “systemctl status virtualbox.service” and “journalctl -xeu virtualbox.service” for details.
    invoke-rc.d: initscript virtualbox, action “restart” failed.
    × virtualbox.service - LSB: VirtualBox Linux kernel module
    Loaded: loaded (/etc/init.d/virtualbox; generated)
    Active: failed (Result: exit-code) since Mon 2026-09-14 22:13:35 CEST; 13ms ago
    Duration: 1min 174ms
    Docs: man:systemd-sysv-generator(8)
    Process: 6623 ExecStart=/etc/init.d/virtualbox start (code=exited, status=1/FAILURE)
    CPU: 59ms

sept. 14 22:13:35 Maxwell systemd[1]: Starting virtualbox.service - LSB: VirtualBox Linux kernel module…
sept. 14 22:13:35 Maxwell virtualbox[6623]: * Loading VirtualBox kernel modules…
sept. 14 22:13:35 Maxwell virtualbox[6623]: * No suitable module for running kernel found
sept. 14 22:13:35 Maxwell virtualbox[6623]: …fail!
sept. 14 22:13:35 Maxwell systemd[1]: virtualbox.service: Control process exited, code=exited, status=1/FAILURE
sept. 14 22:13:35 Maxwell systemd[1]: virtualbox.service: Failed with result ‘exit-code’.
sept. 14 22:13:35 Maxwell systemd[1]: Failed to start virtualbox.service - LSB: VirtualBox Linux kernel module.
Paramétrage de virtualbox-qt (7.0.16-dfsg-2ubuntu1.3) …
Traitement des actions différées (« triggers ») pour desktop-file-utils (0.27-2build1) …
Traitement des actions différées (« triggers ») pour hicolor-icon-theme (0.17-2) …
Traitement des actions différées (« triggers ») pour gnome-menus (3.36.0-1.1ubuntu3) …
Traitement des actions différées (« triggers ») pour man-db (2.12.0-4build2) …
Traitement des actions différées (« triggers ») pour shared-mime-info (2.4-4) …
Traitement des actions différées (« triggers ») pour linux-image-6.17.0-35-generic (6.17.0-35.35~24.04.1) …
/etc/kernel/postinst.d/dkms:

  • dkms: running auto installation service for kernel 6.17.0-35-generic
  • dkms: autoinstall for kernel 6.17.0-35-generic
    …done.
    /etc/kernel/postinst.d/initramfs-tools:
    update-initramfs: Generating /boot/initrd.img-6.17.0-35-generic
    /etc/kernel/postinst.d/zz-update-grub:
    Sourcing file /etc/default/grub' Generating grub configuration file ... Found linux image: /boot/vmlinuz-6.17.0-35-generic Found initrd image: /boot/initrd.img-6.17.0-35-generic Found linux image: /boot/vmlinuz-6.14.0-37-generic Found initrd image: /boot/initrd.img-6.14.0-37-generic Found memtest86+ 64bit EFI image: /boot/memtest86+x64.efi Warning: os-prober will not be executed to detect other bootable partitions. Systems on them will not be added to the GRUB boot configuration. Check GRUB_DISABLE_OS_PROBER documentation entry. Adding boot menu entry for UEFI Firmware Settings ... done useradmin@Maxwell:~$ sudo dpkg --configure -a useradmin@Maxwell:~$ sudo update-initramfs -u -k all update-initramfs: Generating /boot/initrd.img-6.17.0-35-generic update-initramfs: Generating /boot/initrd.img-6.14.0-37-generic useradmin@Maxwell:~$ sudo update-grub Sourcing file /etc/default/grub’
    Generating grub configuration file …
    Found linux image: /boot/vmlinuz-6.17.0-35-generic
    Found initrd image: /boot/initrd.img-6.17.0-35-generic
    Found linux image: /boot/vmlinuz-6.14.0-37-generic
    Found initrd image: /boot/initrd.img-6.14.0-37-generic
    Found memtest86+ 64bit EFI image: /boot/memtest86+x64.efi
    Warning: os-prober will not be executed to detect other bootable partitions.
    Systems on them will not be added to the GRUB boot configuration.
    Check GRUB_DISABLE_OS_PROBER documentation entry.
    Adding boot menu entry for UEFI Firmware Settings …
    done
8

note: I found out why I had Virtual box, this has to do with BOINC
See: Boinc keeps getting an error/notice saying “virtual box is not installed” on Ubuntu

So nothing essential for me, a painful install - finally never used - not recommended !

9

Great! :slightly_smiling_face:

initrd.img-6.17.0-35-generic was generated and picked up by GRUB, so the kernel panic is completely resolved. You can safely reboot into 6.17 now.

To clean up the leftover virtualbox.service failure from your log- since you don’t use BOINC VMs

sudo apt purge virtualbox virtualbox-qt
sudo apt autoremove --purge
10

Kernel 6.17 is no longer supported. User should be running 6.8.x or 7.0.x kernels, as they are supported for the life of Ubuntu 24.04

2 Likes
11

Never say “never” …

Ubuntu installed OEM kernel on my Lenovo and I am still on the 6.17 because there is no 7.0 and the dependencies were not updated to point to the generic kernel either. I did expect it to happen with 24.04.5 release.

1 Like
12

Edit: Disregard the entire previous edit.

Where is your virtualbox source from? If it’s from Oracle, that explains it. If it’s from the Ubuntu repositories, then you might have to do an early upgrade to 26.04 to get Virtualbox working.

13

I will say “never” for the 6.17 generic kernel, which is what the OP is using here. But for the sake of you and anyone else reading the statement: Other kernel variants may have different support timelines.