Welcome, Guest. Please login or register.
Did you miss your activation email?

Author Topic: [DE] VM's starten in VirtualBox nicht mehr  (Read 1841 times)

Offline Hanisch

  • User
  • Posts: 455
[DE] VM's starten in VirtualBox nicht mehr
« on: 2017/11/24, 15:41:24 »
Hallo,
in meiner neuen Siduction-Installation 'patiente-kde-amd64' mit dem Kernel 4.14.1-towo.2-siduction-amd64
und der VirtualBox 5.2.0 von der Oracle-Homepage https://www.virtualbox.org/wiki/Linux_Downloads
sowie 'virtualbox-dkms' starten keine VM's mehr.
Code: [Select]
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.

Code: [Select]
sudo /sbin/vboxconfig
Created symlink /etc/systemd/system/multi-user.target.wants/vboxdrv.service → /lib/systemd/system/vboxdrv.service.
Created symlink /etc/systemd/system/multi-user.target.wants/vboxballoonctrl-service.service → /lib/systemd/system/vboxballoonctrl-service.service.
Created symlink /etc/systemd/system/multi-user.target.wants/vboxautostart-service.service → /lib/systemd/system/vboxautostart-service.service.
Created symlink /etc/systemd/system/multi-user.target.wants/vboxweb-service.service → /lib/systemd/system/vboxweb-service.service.
vboxdrv.sh: Stopping VirtualBox services.
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.

Das LOG File  /var/log/vbox-install.log   siehe   https://paste.ubuntu.com/26034692/

Code: [Select]
sudo modprobe vboxdrv
modprobe: FATAL: Module vboxdrv not found in directory /lib/modules/4.14.1-towo.2-siduction-amd64

Jetzt weiß ich nicht mehr weiter. Verursacht kann das sein durch den Versuch, Bumblebee zu installieren:
Code: [Select]
sudo dpkg --add-architecture i386 && sudo apt-get update && sudo apt-get install bumblebee-nvidia primus primus-libs:i386Kann man das irgendwie rückgängig machen?
Bzw. die VirtualBox kernel module zwangsweise neu bilden?

Gruß
Ch. Hanisch


Offline melmarker

  • User
  • Posts: 2.799
    • g-com.eu
Solved: VM's starten in VirtualBox nicht mehr
« Reply #1 on: 2017/11/24, 15:48:03 »
Nutz die Forensuche
Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. (Benjamin Franklin, November 11, 1755)
Never attribute to malice that which can be adequately explained by stupidity. (Hanlons razor)