Digging a bit deeper, I found the following errors during startup: [FAILED] Failed to start LSB: VirtualBox Linux Kernel Module.
root@debian:/home/xxx# /etc/init.d/virtualbox start Starting virtualbox (via systemctl): virtualbox.serviceJob for virtualbox.service failed. See 'systemctl status virtualbox.service' and 'journalctl -xn' for details. failed! root@debian:/home/xxx# systemctl status virtualbox.service * virtualbox.service - LSB: VirtualBox Linux kernel module Loaded: loaded (/etc/init.d/virtualbox) Active: failed (Result: exit-code) since Wed 2015-04-29 02:24:55 CEST; 6s ago Process: 1284 ExecStart=/etc/init.d/virtualbox start (code=exited, status=1/FAILURE) Apr 29 02:24:55 debian virtualbox[1284]: Starting VirtualBox kernel modulesNo suitable module for running kernel found ... failed! Apr 29 02:24:55 debian virtualbox[1284]: failed! Apr 29 02:24:55 debian systemd[1]: virtualbox.service: control process exited, code=exited status=1 Apr 29 02:24:55 debian systemd[1]: Failed to start LSB: VirtualBox Linux kernel module. Apr 29 02:24:55 debian systemd[1]: Unit virtualbox.service entered failed state. root@debian:/home/xxx# journalctl -xn -- Logs begin at Wed 2015-04-29 02:18:33 CEST, end at Wed 2015-04-29 02:24:55 CEST. -- Apr 29 02:24:47 debian systemd[1261]: Reached target Default. -- Subject: Unit UNIT has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit UNIT has finished starting up. -- -- The start-up result is done. Apr 29 02:24:47 debian systemd[1261]: Startup finished in 123ms. -- Subject: System start-up is now complete -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- All system services necessary queued for starting at boot have been -- successfully started. Note that this does not mean that the machine is -- now idle as services might still be busy with completing start-up. -- -- Kernel start-up required KERNEL_USEC microseconds. -- -- Initial RAM disk start-up required INITRD_USEC microseconds. -- -- Userspace start-up required 123746 microseconds. Apr 29 02:24:51 debian su[1274]: Successful su for root by xxx Apr 29 02:24:51 debian su[1274]: + /dev/pts/0 xxx:root Apr 29 02:24:51 debian su[1274]: pam_unix(su:session): session opened for user root by xxx(uid=1000) Apr 29 02:24:55 debian virtualbox[1284]: Starting VirtualBox kernel modulesNo suitable module for running kernel found ... failed! Apr 29 02:24:55 debian virtualbox[1284]: failed! Apr 29 02:24:55 debian systemd[1]: virtualbox.service: control process exited, code=exited status=1 Apr 29 02:24:55 debian systemd[1]: Failed to start LSB: VirtualBox Linux kernel module. -- Subject: Unit virtualbox.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit virtualbox.service has failed. -- -- The result is failed. Apr 29 02:24:55 debian systemd[1]: Unit virtualbox.service entered failed state. (btw, the "INITRD_USEC microseconds" or "KERNEL_USEC microseconds" seem to be buggy output...) Does anyone have an idea about this? Dietmar -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/trinity-5c59d31c-242e-4f33-a5ef-6cb64ec6243c-1430267636813@3capp-webde-bs01
