Your message dated Sun, 23 Jul 2017 15:10:22 +0000 (UTC)
with message-id <2122486031.4369262.1500822622...@mail.yahoo.com>
and subject line Re: Bug#869258: virtualbox-dkms: fails to build on kernel
version 4.11.0-1
has caused the Debian Bug report #869258,
regarding virtualbox-dkms: fails to build on kernel version 4.11.0-1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
869258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869258
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: virtualbox-dkms
Version: 5.1.10-dfsg-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
After a recent dist-upgrade, VirtualBox fails to strart VMs with the
following error message:
> 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 virtualbox-dkms
> package and load the kernel module by executing
>
> 'modprobe vboxdrv'
>
> as root.
>
> where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The
> support driver is not installed. On linux, open returned ENOENT.
I tried to run "dpkg-reconfigure virtualbox-dkms" which resulted in the
following error:
> Error! Bad return status for module build on kernel: 4.11.0-1-amd64
> (x86_64)
> Consult /var/lib/dkms/virtualbox/5.1.10/build/make.log for more
> information.
The relevant section of the log file is as follows:
> CC [M]
> /var/lib/dkms/virtualbox/5.1.10/build/vboxdrv/r0drv/linux/mp-r0drv-linux.o
> /var/lib/dkms/virtualbox/5.1.10/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:
> In function ‘rtR0MemObjNativeLockUser’:
> /var/lib/dkms/virtualbox/5.1.10/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:1067:18:
> error: too few arguments to function ‘get_user_pages_remote’
> rc = get_user_pages_remote(
> ^~~~~~~~~~~~~~~~~~~~~
> In file included from
> /var/lib/dkms/virtualbox/5.1.10/build/vboxdrv/r0drv/linux/the-linux-kernel.h:98:0,
> from
> /var/lib/dkms/virtualbox/5.1.10/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:31:
> /usr/src/linux-headers-4.11.0-1-common/include/linux/mm.h:1326:6: note:
> declared here
> long get_user_pages_remote(struct task_struct *tsk, struct mm_struct *mm,
> ^~~~~~~~~~~~~~~~~~~~~
> /usr/src/linux-headers-4.11.0-1-common/scripts/Makefile.build:299: recipe for
> target
> '/var/lib/dkms/virtualbox/5.1.10/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.o'
> failed
As a workaround, I found that switching back to the older kernel version
(4.9.0-3) works.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.11.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=hu_HU.utf8, LC_CTYPE=hu_HU.utf8 (charmap=UTF-8),
LANGUAGE=hu_HU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages virtualbox-dkms depends on:
ii dkms 2.3-3
Versions of packages virtualbox-dkms recommends:
ii virtualbox 5.1.10-dfsg-1
virtualbox-dkms suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
>Version: 5.1.10-dfsg-1
old version, grab the one in unstable if you want it
G.
--- End Message ---
