Ik wilde weer met VirtualBox werken, maar het bleek niet meer oké te zijn. Dus voerde ik vboxconfig (als root) uit, maar dit leverde op: 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: Starting VirtualBox services. vboxdrv.sh: Building VirtualBox kernel modules. vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why.
There were problems setting up VirtualBox. To re-start the set-up process, run /sbin/vboxconfig as root. Met dmesg zie ik: [276787.274664] vboxdrv: disagrees about version of symbol cpu_tlbstate [276787.274668] vboxdrv: Unknown symbol cpu_tlbstate (err -22) [276817.780511] vboxdrv: disagrees about version of symbol cpu_tlbstate [276817.780514] vboxdrv: Unknown symbol cpu_tlbstate (err -22) Ik heb zowel build-essential als linux-headers-amd64 geïnstalleerd. Moet ik nog iets anders installeren? -- Cecil Westerhof Senior Software Engineer LinkedIn: http://www.linkedin.com/in/cecilwesterhof