Opened 6 years ago
Last modified 5 years ago
#18904 new defect
Unable to install VirtualBox on Debian 10 Buster
Reported by: | baltzatu | Owned by: | |
---|---|---|---|
Component: | installer | Version: | VirtualBox 6.0.10 |
Keywords: | vboxdrv.sh, failed, modprobe, vboxdrv, dmesg | Cc: | |
Guest type: | all | Host type: | Linux |
Description
Hello.
Today I tried to upgrade my VirtualBox to the latest version. I powered off my vms and started the update. Now, all the versions I try to install (testbuilds included) fail on compiling. The host is older. No Secure Boot, no EFI, just plain old BIOS and MBR. OS: Debian 10 Buster almost headless (LXDE installed, but it doesn't start on boot and I almost never use it).
Errors on install: vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why
dmesg: [ 360.630491] vboxdrv: loading out-of-tree module taints kernel. [ 360.630672] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel [ 360.630887] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000e65fb879, val ffffffffc0ab74cf [ 474.533886] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000e65fb879, val ffffffffc0ab74cf [ 2230.385340] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000e65fb879, val ffffffffc0ab74cf [ 4321.446054] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 0000000058cb242c, val ffffffffc0b734cf [ 4468.860093] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000e65fb879, val ffffffffc0ab74cf [ 4912.527732] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000e65fb879, val ffffffffc0ab74cf [ 4946.446931] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000e65fb879, val ffffffffc0ab74cf [ 5099.180792] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 0000000058cb242c, val ffffffffc0b734cf [ 5657.446078] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000e65fb879, val ffffffffc0ab75af [ 6310.679083] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000751064cb, val ffffffffc0ab792f [ 7275.790717] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000e65fb879, val ffffffffc0ab74cf
I tried the Fedora 29/30 fix, with no luck.
Please help... I'd hate to reinstall and fall back to Stretch.
If you need more details, please let me know.
Thank you.
Attachments (2)
Change History (14)
comment:2 by , 6 years ago
Ty for the info, but:
- when I upgraded from Stretch to Buster, VirtualBox was installed and it worked properly until today, when I made the upgrade attempt;
- take a look at the VirtualBox repository (http://download.virtualbox.org/virtualbox/debian/dists/). Buster is there, so that's pretty much why I tried to upgrade...
comment:3 by , 6 years ago
From what version of Virtualbox on Debian 10 did you upgraded to what version exactly. Such information usually helps tremendously.
by , 6 years ago
Attachment: | 2019-09-04 - VirtualBox 6.0.10 on Debian Buster.jpg added |
---|
VB 6.0.10 on Debian Buster
comment:4 by , 6 years ago
I'll get back to you on that. I hope I'll find it in an apticron message.
Anyway, here's another Buster host, also updated from Stretch, that runs VirtualBox 6.0.10-132072~Ubuntu~bionic just fine.
comment:6 by , 6 years ago
No joy, same errors:
vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why. dmesg: [ 360.630491] vboxdrv: loading out-of-tree module taints kernel. [ 360.630672] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel [ 360.630887] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000e65fb879, val ffffffffc0ab74cf [ 474.533886] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000e65fb879, val ffffffffc0ab74cf [ 2230.385340] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000e65fb879, val ffffffffc0ab74cf [ 4321.446054] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 0000000058cb242c, val ffffffffc0b734cf [ 4468.860093] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000e65fb879, val ffffffffc0ab74cf [ 4912.527732] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000e65fb879, val ffffffffc0ab74cf [ 4946.446931] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000e65fb879, val ffffffffc0ab74cf [ 5099.180792] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 0000000058cb242c, val ffffffffc0b734cf [ 5657.446078] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000e65fb879, val ffffffffc0ab75af [ 6310.679083] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000751064cb, val ffffffffc0ab792f [ 7275.790717] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000e65fb879, val ffffffffc0ab74cf [11293.857385] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000e65fb879, val ffffffffc0ab74cf [13283.872538] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000e65fb879, val ffffffffc0ab74cf
comment:7 by , 6 years ago
I tried installing virtualbox-6.0_6.0.10-132072~Ubuntu~bionic_amd64.deb. No joy also.
So:
- after upgrading from Stretch to Buster, VirtualBox worked fine;
- if VirtualBox is uninstalled and then reinstalled or upgraded in Buster, it breaks.
comment:8 by , 6 years ago
The latest version installed in Stretch, before upgrading to Buster, was virtualbox-6.0:amd64 6.0.10-132072~Ubuntu~bionic.
comment:9 by , 6 years ago
Same here. Worked after dist-upgrade failed after installing 6.0.12
Fixed with kernel upgrade from
linux-image-4.19.0-5-amd64
to
linux-image-4.19.0-6-amd64-unsigned
I guess what makes the difference is the -unsigned part, but can't really test it as it's a production system and every reboot counts.
P.S it's a legacy non-efi install, so no secure boot anyway.
comment:10 by , 6 years ago
I was running linux-image-4.19.0-5-amd64 before I found this ticket. I had the same errors in dmesg. Now my modules are loading.
supaplex@claw:~$ dpkg -l virtualbox-6.0 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==============-===========================-============-================================= ii virtualbox-6.0 6.0.12-133076~Ubuntu~bionic amd64 Oracle VM VirtualBox supaplex@claw:~$ dpkg -l linux-image-4.19.0-6-amd64{,-unsigned} Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-===================================-=================-============-================================== ii linux-image-4.19.0-6-amd64 4.19.67-2+deb10u1 amd64 Linux 4.19 for 64-bit PCs (signed) un linux-image-4.19.0-6-amd64-unsigned <none> <none> (no description available) supaplex@claw:~$ lsmod | grep vbox vboxpci 28672 0 vboxnetadp 28672 0 vboxnetflt 32768 1 vboxdrv 487424 4 vboxpci,vboxnetadp,vboxnetflt
comment:11 by , 6 years ago
according to a comment in:
"Installing linux-image-4.19.0-6-amd64 should have the same effect, the problem lies in the linux-image-4.19.0-5-amd64 / linux-headers-4.19.0-5-amd64 combo"
Has this been verified? Doesn't seem like a problem we can solve.
comment:12 by , 5 years ago
Sorry, guys, but I was't able to login until today.
I couldn't wait that much, so I downgraded to Stretch, but I got another server to test on.
With the signed kernel:
/sbin/vboxconfig vboxdrv.sh: Stopping VirtualBox services. 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. If your system is using EFI Secure Boot you may need to sign the kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load them. Please see your Linux system's documentation for more information.
dmesg:
[3457494.117302] vboxnetflt: 0 out of 40359804711 packets were not sent (directed to host) [3457664.536437] VBoxPciLinuxLinuxUnload [3457731.967315] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 000000009064bbeb, val ffffffffc0b924cf [3457766.496868] traps: VBoxSVC[9391] trap int3 ip:7fc1af6330b4 sp:7ffc3013b9d0 error:0 in VBoxXPCOMIPCC.so[7fc1af624000+1f000] [3457836.957360] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 000000009064bbeb, val ffffffffc0b924cf [3457935.447100] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 000000009064bbeb, val ffffffffc0b924cf
uname -r 4.19.0-5-amd64
After installing the unsigned kernel and rebooting:
uname -r 4.19.0-6-amd64
/sbin/vboxconfig still fails, but the error is different: "[ 124.816132] vboxpci: IOMMU not found (not registered)". I ran it again, it ran OK, VirtualBox services are running.
by , 5 years ago
Attachment: | 2019-10-08 - VirtualBox 6.0.12 on Debian Buster.jpg added |
---|
Here's the proof
fwiw, Debian 10 is just a month old, doubt anyone has tested that yet:
https://www.debian.org/News/2019/20190706
it is the next 5 years LTS release of Debian