質問: virtualbox kernelドライバがインストールされていない場合の修復方法 今日、私は自分のvirtualbox vmがもう起動しないことに気付きました。メッセージ付き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} そして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. これはカーネルのアップデートによるものと思われます。私は、ubuntuがカーネルの自動更新を行っていることを実際には知りませんでした。ログ/var/log/dpkg.logは、問題が始まる直前にカーネルの更新が行われていたことを示しています。sudo dpkg --list | grep linux-imageは、4.8、4.10、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 残念ながらこの問題に対する提案された解決策はうまくいきません。[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:~] # インストールログ/var/log/vbox-install.logはここに投稿するには大きすぎますが、それは次のメッセージで始まります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 ; 実際には3つの質問があります。カーネル構成をどのように修正すればよいですか? * virtualboxはどのように修正しますか?削除して再インストールする必要がありますか? *この種の問題を防ぐにはどうすればいいですか?カーネルの自動更新を無効にするべきですか?
回答: virtualboxを5.2.6 r120293にアップグレードした後も同じ問題が発生しましたlinuxカーネルバージョン4.14.13-041413-generic次のコマンドシーケンスは私にとって役に立ちました:$ sudo apt install --reinstall virtualbox-dkms && sudo apt install libelf-dev $ sudo /sbin/vboxconfig