VirtualBox can't run after update.

[hack3rcon]

Hello,
I'm using Debian 10.1 x86_64 and after update VirtualBox can't run my VMs and tell me to run "/sbin/vboxconfig". When I run that command then show me below error :

Code: Select all

$ sudo /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.

And :

Code: Select all

$ sudo modprobe vboxdrv
modprobe: ERROR: could not insert 'vboxdrv': Exec format error

And :

Code: Select all

$ dmesg
[ 4228.182912] VBoxPciLinuxLinuxUnload
[ 4356.225318] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000ac109651, val ffffffffc1a734cf
[ 7293.461533] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000ac109651, val ffffffffc1a734cf
[11310.256085] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000ac109651, val ffffffffc1a734cf

How can I solve it?

Thank you.

[socratis]

I'm using Debian 10.1 x86_64

Maybe that's too new...

and after update VirtualBox

To what?

I haven't seen any patches regarding Debian 10.1, but can you try with the latest test builds?

[hack3rcon]

I'm using ".run" file.https://download.virtualbox.org/virtual ... _amd64.run

[socratis]

Yes, and I specifically pointed you to the test builds, not the releases, because there's no Debian 10.1 release.

If you want to use the latest version for your host/guests, you should also consider doing the same for VirtualBox. If the existing releases don't work, you should try the latest test builds.

[hack3rcon]

Why an old version worked? Can I downgrade?

[towo2099]

That has nothing to do with too new debian.
Debian 10.1 is Buster!
Your problem is:

Code: Select all

modprobe: ERROR: could not insert 'vboxdrv': Exec format error

That you probleably allways get, if you build the modules against the wrong headers, which do not fit your running kernel.

And. btw, you don't need the test builds and you really should not use the generic installer, use debian packages!

[socratis]

if you build the modules against the wrong headers, which do not fit your running kernel.

You would get a warning during the compilation, if I'm not mistaken, not this error that the OP got.

And. btw, you don't need the test builds and you really should not use the generic installer, use debian packages!

Can you explain that to me 'towo2099'? What's exactly wrong with trying the test builds?

[towo2099]

Installing "things" by bypassing the package management is rare a good idea.
And the TE does not need a testbuild, since the release is running fine on debian buster.

[hack3rcon]

That has nothing to do with too new debian.
Debian 10.1 is Buster!
Your problem is:

Code: Select all

modprobe: ERROR: could not insert 'vboxdrv': Exec format error

That you probleably allways get, if you build the modules against the wrong headers, which do not fit your running kernel.

And. btw, you don't need the test builds and you really should not use the generic installer, use debian packages!

?
Can I install VirtualBox for Debian 9 on Debian 10? As I said, it worked on Debian 10 but after update then it can't launch.

[towo2099]

Why? What's wrong with the buster version?

Better you provide the output of:

Code: Select all

uname -a
dpkg -l | egrep -i "x-image|x-header"

[socratis]

Installing "things" by bypassing the package management is rare a good idea.

Yeah, sure, but

1. this is reserved for rare cases, and programs used to work way before the package manager, no animals were hurt
2. there's no Debian-specific test build, you got to drop-down to the generic Linux version, works on everything.

And the TE does not need a testbuild

What's a "TE"? "OP" in another language?

Can I install VirtualBox for Debian 9 on Debian 10?

No, you should be installing VirtualBox for Debian 10, if you're using Debian 10. See https://download.virtualbox.org/virtualbox/6.0.14/ and more specifically https://download.virtualbox.org/virtual ... _amd64.deb

[towo2099]

What's a "TE"?

Oha, falling back in my native language (german): TE = Tread Eröffner.
It should be better ts = tread starter.

[hack3rcon]

Why? What's wrong with the buster version?

Better you provide the output of:

Code: Select all

uname -a
dpkg -l | egrep -i "x-image|x-header"

Code: Select all

$ uname -a
Linux User 4.19.0-5-amd64 #1 SMP Debian 4.19.37-5+deb10u2 (2019-08-08) x86_64 GNU/Linux

And:

Code: Select all

$ dpkg -l | egrep -i "x-image|x-header"
ii  linux-headers-3.16.0-4-amd64               3.16.51-3                                   amd64        Header files for Linux 3.16.0-4-amd64
ii  linux-headers-3.16.0-4-common              3.16.51-3                                   amd64        Common header files for Linux 3.16.0-4
ii  linux-headers-4.19.0-5-amd64               4.19.37-5+deb10u2                           amd64        Header files for Linux 4.19.0-5-amd64
ii  linux-headers-4.19.0-5-common              4.19.37-5+deb10u2                           all          Common header files for Linux 4.19.0-5
ii  linux-headers-4.9.0-9-amd64                4.9.168-1+deb9u3                            amd64        Header files for Linux 4.9.0-9-amd64
ii  linux-headers-4.9.0-9-common               4.9.168-1+deb9u3                            all          Common header files for Linux 4.9.0-9
ii  linux-headers-amd64                        4.19+105                                    amd64        Header files for Linux amd64 configuration (meta-package)
rc  linux-image-3.16.0-4-amd64                 3.16.51-3                                   amd64        Linux 3.16 for 64-bit PCs
ii  linux-image-4.19.0-5-amd64                 4.19.37-5+deb10u2                           amd64        Linux 4.19 for 64-bit PCs (signed)
ii  linux-image-4.9.0-9-amd64                  4.9.168-1+deb9u3                            amd64        Linux 4.9 for 64-bit PCs
ii  linux-image-amd64                          4.19+105                                    amd64        Linux for 64-bit PCs (meta-package)

[hack3rcon]

Problem not solved

[hack3rcon]

Any idea?
Can install from source solve this problem?