Comment réparer et empêcher le pilote VirtualBox Kernel non installé

Question

Aujourd'hui, j'ai remarqué que mes machines virtuelles VirtualBox ne démarrent plus. Avec des messages

The virtual machine 'CGI' has terminated unexpectedly during startup with exit code 1 (0x1). Result Code: NS_ERROR_FAILURE (0x80004005) Component: MachineWrap Interface: IMachine Unknown macro: {b2547866-a0a1-4391-8b86-6952d82efaa0}

Et

Kernel driver not installed (rc=-1908) The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing '/sbin/vboxconfig' as root. where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT.

Il semble que cela soit causé par une mise à jour du noyau. En fait, je ne savais pas qu'Ubuntu effectuait des mises à jour automatiques du noyau. Le journal /var/log/dpkg.log indique que la mise à jour du noyau était en cours juste avant le début des problèmes.

Sudo dpkg --list | grep linux-image affiche les lignes d'images avec de nombreuses versions 4.8, 4.10 et 4.13.

[user:~] $ uname -a Linux io 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

La solution proposée pour ce problème ne fonctionne malheureusement pas.

[root:~] # /sbin/vboxconfig vboxdrv.sh: Stopping VirtualBox services. depmod: ERROR: could not open directory /lib/modules/4.10.0-27-generic: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: ERROR: could not open directory /lib/modules/4.10.0-28-generic: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: ERROR: could not open directory /lib/modules/4.10.0-30-generic: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: ERROR: could not open directory /lib/modules/4.10.0-32-generic: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: ERROR: could not open directory /lib/modules/4.10.0-33-generic: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: ERROR: could not open directory /lib/modules/4.10.0-35-generic: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: ERROR: could not open directory /lib/modules/4.10.0-37-generic: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: ERROR: could not open directory /lib/modules/4.10.0-38-generic: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: ERROR: could not open directory /lib/modules/4.10.0-40-generic: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: ERROR: could not open directory /lib/modules/4.8.0-41-generic: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: ERROR: could not open directory /lib/modules/4.8.0-45-generic: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: ERROR: could not open directory /lib/modules/4.8.0-46-generic: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: ERROR: could not open directory /lib/modules/4.8.0-49-generic: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: ERROR: could not open directory /lib/modules/4.8.0-52-generic: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: ERROR: could not open directory /lib/modules/4.8.0-54-generic: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: ERROR: could not open directory /lib/modules/4.8.0-56-generic: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: ERROR: could not open directory /lib/modules/4.8.0-58-generic: No such file or directory depmod: FATAL: could not search modules: No such file or directory vboxdrv.sh: Building VirtualBox kernel modules. vboxdrv.sh: failed: Look at /var/log/vbox-install.log to find out what went wrong. There were problems setting up VirtualBox. To re-start the set-up process, run /sbin/vboxconfig as root. [root:~] #

Le journal d'installation /var/log/vbox-install.log est trop volumineux pour être posté ici, mais il commence par le message suivant

make[1]: warning: -jN forced in submake: disabling jobserver mode. test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \ echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it."; \ echo >&2 ;

Il y a en fait trois questions maintenant, je pense * Comment puis-je résoudre la configuration du noyau? * Comment puis-je réparer VirtualBox? Dois-je supprimer et réinstaller? * Comment puis-je prévenir ces types de problèmes? Devrais-je désactiver les mises à jour automatiques du noyau?

Kirill Feoktistov · Answer

J'ai rencontré le même problème après la mise à niveau de VirtualBox vers 5.2.6 r120293

Noyau Linux version 4.14.13-041413-generic

La séquence de commandes suivante m'a aidé:

$ Sudo apt install --reinstall virtualbox-dkms && Sudo apt install libelf-dev $ Sudo /sbin/vboxconfig

Asklep · Answer

$ Sudo apt install --reinstall virtualbox-dkms && Sudo apt install libelf-dev

juste cela a résolu le même problème sur mon Kubuntu 18.4.2

Beytullah Gul · Answer

root@linux:/home/linux/Downloads# apt install --reinstall virtualbox-dkms && Sudo apt install libelf-dev Paket listeleri okunuyor... Bitti Bağımlılık ağacı oluşturuluyor Durum bilgisi okunuyor... Bitti 0 paket yükseltilecek, 0 yeni paket kurulacak, 1 paket yeniden kurulacak, 0 paket kaldırılacak ve 643 paket yükseltilmeyecek. 0 B/682 kB arşiv dosyası indirilecek. Bu işlem tamamlandıktan sonra 0 B ek disk alanı kullanılacak. (Veritabanı okunuyor ... 361148 dosya veya dizin kurulu durumda.) Paket açılacak: .../virtualbox-dkms_5.2.8-dfsg-5_all.deb ... -------- Uninstall Beginning -------- Module: virtualbox Version: 5.2.8 Kernel: 4.15.0-kali3-AMD64 (x86_64) ------------------------------------- Status: Before uninstall, this module version was ACTIVE on this kernel. vboxdrv.ko: - Uninstallation - Deleting from: /lib/modules/4.15.0-kali3-AMD64/updates/ - 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: - Uninstallation - Deleting from: /lib/modules/4.15.0-kali3-AMD64/updates/ - 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: - Uninstallation - Deleting from: /lib/modules/4.15.0-kali3-AMD64/updates/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. vboxpci.ko: - Uninstallation - Deleting from: /lib/modules/4.15.0-kali3-AMD64/updates/ - 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... DKMS: uninstall completed. ------------------------------ Deleting module version: 5.2.8 completely from the DKMS tree. ------------------------------ Done. Paket açılıyor: virtualbox-dkms (5.2.8-dfsg-5) üzerine (5.2.8-dfsg-5) ... Ayarlanıyor: virtualbox-dkms (5.2.8-dfsg-5) ... Loading new virtualbox-5.2.8 DKMS files... Building for 4.15.0-kali2-AMD64 4.15.0-kali3-AMD64 Module build for kernel 4.15.0-kali2-AMD64 was skipped since the kernel headers for this kernel does not seem to be installed. Building initial module for 4.15.0-kali3-AMD64 Done. vboxdrv: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/4.15.0-kali3-AMD64/updates/ vboxnetadp.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/4.15.0-kali3-AMD64/updates/ vboxnetflt.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/4.15.0-kali3-AMD64/updates/ vboxpci.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/4.15.0-kali3-AMD64/updates/ depmod... DKMS: install completed. Job for virtualbox.service failed because the control process exited with error code. See "systemctl status virtualbox.service" and "journalctl -xe" 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 Wed 2018-05-23 16:30:46 +03; 7ms ago Docs: man:systemd-sysv-generator(8) Process: 22851 ExecStart=/etc/init.d/virtualbox start (code=exited, status=1/FAILURE) May 23 16:30:46 linux systemd[1]: Starting LSB: VirtualBox Linux kernel module... May 23 16:30:46 linux virtualbox[22851]: Loading VirtualBox kernel modules...No suitable module for running kernel found ... failed! May 23 16:30:46 linux virtualbox[22851]: failed! May 23 16:30:46 linux systemd[1]: virtualbox.service: Control process exited, code=exited status=1 May 23 16:30:46 linux systemd[1]: virtualbox.service: Failed with result 'exit-code'. May 23 16:30:46 linux systemd[1]: Failed to start LSB: VirtualBox Linux kernel module. Paket listeleri okunuyor... Bitti Bağımlılık ağacı oluşturuluyor Durum bilgisi okunuyor... Bitti Aşağıdaki ek paketler kurulacak: libdw1 libelf1 zlib1g zlib1g-dev Aşağıdaki YENİ paketler kurulacak: libelf-dev zlib1g-dev Aşağıdaki paketler yükseltilecek: libdw1 libelf1 zlib1g 3 paket yükseltilecek, 2 yeni paket kurulacak, 0 paket kaldırılacak ve 640 paket yükseltilmeyecek. 286 kB/759 kB arşiv dosyası indirilecek. Bu işlem tamamlandıktan sonra 848 kB ek disk alanı kullanılacak. Devam etmek istiyor musunuz? [E/h] e İndir: 1 http://kali.mirror.garr.it/mirrors/kali kali-rolling/main AMD64 zlib1g-dev AMD64 1:1.2.11.dfsg-1 [214 kB] İndir: 2 http://kali.mirror.garr.it/mirrors/kali kali-rolling/main AMD64 libelf-dev AMD64 0.170-0.4 [71,6 kB] 2 sn.'de 286 kB alındı (153 kB/s) Reading changelogs... Done (Veritabanı okunuyor ... 361148 dosya veya dizin kurulu durumda.) Paket açılacak: .../zlib1g_1%3a1.2.11.dfsg-1_AMD64.deb ... Paket açılıyor: zlib1g:AMD64 (1:1.2.8.dfsg-5) üzerine (1:1.2.11.dfsg-1) ... Ayarlanıyor: zlib1g:AMD64 (1:1.2.11.dfsg-1) ... (Veritabanı okunuyor ... 361148 dosya veya dizin kurulu durumda.) Paket açılacak: .../libdw1_0.170-0.4_AMD64.deb ... Paket açılıyor: libdw1:AMD64 (0.170-0.3) üzerine (0.170-0.4) ... Paket açılacak: .../libelf1_0.170-0.4_AMD64.deb ... Paket açılıyor: libelf1:AMD64 (0.170-0.3) üzerine (0.170-0.4) ... Daha önce seçili olmayan zlib1g-dev:AMD64 paketi seçiliyor. Paket açılacak: .../zlib1g-dev_1%3a1.2.11.dfsg-1_AMD64.deb ... Paket açılıyor: zlib1g-dev:AMD64 (1:1.2.11.dfsg-1) ... Daha önce seçili olmayan libelf-dev:AMD64 paketi seçiliyor. Paket açılacak: .../libelf-dev_0.170-0.4_AMD64.deb ... Paket açılıyor: libelf-dev:AMD64 (0.170-0.4) ... Ayarlanıyor: libelf1:AMD64 (0.170-0.4) ... Tetikleyiciler işleniyor: libc-bin (2.27-3) ... Tetikleyiciler işleniyor: man-db (2.8.2-1) ... Ayarlanıyor: zlib1g-dev:AMD64 (1:1.2.11.dfsg-1) ... Ayarlanıyor: libdw1:AMD64 (0.170-0.4) ... Ayarlanıyor: libelf-dev:AMD64 (0.170-0.4) ... Tetikleyiciler işleniyor: libc-bin (2.27-3) ... root@linux:/home/linux/Downloads# /sbin/vboxconfig bash: /sbin/vboxconfig: Böyle bir dosya ya da dizin yok root@linux:/home/linux/Downloads#