VirtualBox can't run after update.

[socratis]

I told you time and again to try the test builds. You haven't.

Now you wanna try the source code and not the test builds! Be my guest...

[hack3rcon]

I told you time and again to try the test builds. You haven't.

Now you wanna try the source code and not the test builds! Be my guest...

I downloaded "https://download.virtualbox.org/virtual ... _amd64.deb" and have a same problem.

[towo2099]

Wrinting every time "doesn't wortk" doies not help at all.
The logfile from the command "/sbin/vboxconfig" wold help instead.

[socratis]

@'hack3rcon'
Seriously now, I'm going to start ignoring you if you keep on ignoring me! This is not the test build!!!

[hack3rcon]

I installed the test build, but got the same error:

Code: Select all

$ sudo ./VirtualBox-6.0.15-134701-Linux_amd64.run 
Verifying archive integrity... All good.
Uncompressing VirtualBox for Linux installation.............
VirtualBox Version 6.0.15 r134701 (2019-11-17T14:57:03Z) installer
Installing VirtualBox to /opt/VirtualBox
Python found: python, installing bindings...
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.

VirtualBox has been installed successfully.

You will find useful information about using VirtualBox in the user manual
  /opt/VirtualBox/UserManual.pdf
and in the user FAQ
  http://www.virtualbox.org/wiki/User_FAQ

We hope that you enjoy using VirtualBox.

The installation log file is at /var/log/vbox-install.log.

And:

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.

[scottgus1]

OK, good error message posting!

However, as posting error messages will not get your Virtualbox running, you will need to troubleshoot what the error messages say. This is something you'll have to do, since we are not doing the install on your PC.

Both error messages contain this:

vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why.

Did you run dmesg to find out why?

If your system is using EFI Secure Boot you may need to sign the kernel modules

Did you find out if your host PC is using EFI so you may need to do this signing?

And even though you got these errors, what actually happens when you try to start Virtualbox?

[hack3rcon]

I cleared "dmesg" and run VirtualBox again and it just show me:

Code: Select all

$ sudo dmesg 
[24211.457403] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 00000000deb18171, val ffffffffc1ca756f

Yes, My system using UEFI and I did some research about signing the kernel, but it cause some boot errors!

[scottgus1]

Not being a Linux guy, I would not know the proper way to 'use dmesg' or any other such stuff. But I'll bet there's internet sites that tell how to do so generally. Being a raw noob on Linux, I do wonder, though, if there is a difference between 'use dmesg' and 'clear dmesg'. I may be wrong.

On Windows, Virtualbox is an MSI installer program using Microsoft MSI programs. To troubleshoot a failed install on a Windows machine we have to go to Microsoft for troubleshooting steps, not Virtualbox. I suspect you will have ot do the same. Go to your host OS's websites to figure out how to troubleshoot a failed install.

Another troubleshooting step I would suggest, to confirm that you have not got anything unusual about your present OS is to put a different disk in your host, freshly installing your host OS, do the updates, and install the official Virtualbox from http://www.virtualbox.org. Try a guest on that new fresh OS. If you get the same trouble, could be that Virtualbox isn't ready for your host OS version yet.

If you do get the same issue, try one version back on your host OS, again, a fresh install, not an in-the-OS rollback.

[mpack]

I'm seeing lots of mentions of x86, along with a confusing indication of "Debian x86_64" as the distro version. Is that just because Debian can be compiled for non PC processors, or does it indicate a 32bit host?

[fth0]

Being a raw noob on Linux, I do wonder, though, if there is a difference between 'use dmesg' and 'clear dmesg'.

FYI: dmesg is a standard Linux console command that displays all (text) messages from the kernel ring buffer to the console. dmesg --clear clears this buffer, so you don't have to search where the new messages begin.

[socratis]

dmesg --clear clears this buffer, so you don't have to search where the new messages begin.

True, very true...

But if you "clear" dmesg (on Linux) / Console (on OSX) / Event Viewer (on Win) after you've been asked to check there for error messages, guess what you'll find there...

[fth0]

Of course you have to execute the command(s) that create the kernel messages again, after clearing the kernel ring buffer. But you may be right, since hack3rcon wrote ...

I cleared "dmesg" and run VirtualBox again

... they maybe indeed have not run sudo vboxconfig again.

[hack3rcon]

Any idea to solve the problem?
I installed "sbsign" tool.

[scottgus1]

Hackercon, I'm going to ask you to read something. This is not an insult. It is a wholehearted attempt to help you interface with folks who wish to help you solve your problem. Take a good look at your responses (and the lack thereof) to the help attempts that have been made by the other posters on this thread, and consider what changes you need to make in your willingness to read what others have posted as response to your questions and comprehension of what they have posted.

Please read this:

http://slash7.com/2006/12/22/vampires/

Then look back through this thread and see what you need to modify.

[hack3rcon]

If I could find the solution then why I should ask here?
I searched but can't find any good way. some of them cause system not booted or...