VirtualBox won't start
 

Out of the blue, I can't get VirtualBox to start. I updated Slackware 14.2 to the current version via slackpkg, which didn't install much, and now I get this when trying to start VirtualBox:

/opt/VirtualBox/VirtualBox
VirtualBox: Error -610 in supR3HardenedMainInitRuntime!
VirtualBox: dlopen("/opt/VirtualBox/VBoxRT.so",) failed: <NULL>

I have, of course, removed and reinstalled it. I also removed and reinstalled the video drivers (nVidia proprietary 375.39), but other than that I have no clue. A romp through Google has not revealed anything of use.

Anyone see this before, and have any ideas?

EDIT: I installed an older version of VirtualBox and it works. It appears this is something Oracle did to the current version of VirtualBox....

The current version is 5.1.22, and gives the above error. I backed off to 5.1.14, and that older version works as expected.

I just upgraded VirtualBox, Version 5.1.22 r115126 (Qt5.6.1) on slackware 64 14.2 all up to date.

I brought up and installed guest additions on 3 slackware vms and 3 windows vms without any issues.

You said this is with current?

I do see similar message here your <NULL> says "libGL.so.1: cannot open shared object" there.

What does say?

Can't do it until tonight, but I'll reload the current version then and report here....

This is with SlackWare 14.2

Edit:

So I tried the previous four versions, and they all work fine. The current version of VirutalBox, 5.1.22 now works. All I did was remove it, run an older version, and then try the current version again....is there a full moon? Increase in cosmic ray activity?

If you got a new kernel with the upgrade, this may halp. As root

This will recompile the VBox kernel against the new Linux kernel.

Unless he installed it via SBo, which in that case, just rebuild the virtualbox-kernel package to build against the newer kernel that Slackware added.

I tried that to rebuild the kernel module, did not help. I installed VB from the installer from their website - didn't know there was a slackbuilds package for it...

I vote cosmic rays. It worked before, my kernel has not been touched for a while, and it's working fine now...

same issue and fixed it
 

Howdy all,

I have exactly the problem : updated my slackbox to the last current and the same error happens!

run VB 5.1.22 and 5.1.20 fails even if i ru /etc/rc.d/rc.vboxdrv setup

but looking up at /opt i found that the owner wasn't root !

doing chown root:root /opt fixed the issue.

after all Vb 5.1.22 works fine.

Weird. The /opt/VirtualBox directory and all files underneath should be owned by root. If not, it should complain and tell you something like "Effective UID is not root...."...

I never saw this problem before, have not had this problem since. <shrug>

BUT if root owns everything you can still get this error. I fixed it by removing all files under /opt/VirtualBox and, as root, run the installer downloaded from their website. Problem solved.

Try it:

chown root:root -Rc /opt/VirtualBox

You get nothing in the output because there is nothing to change. YET now you can't get VB to run! (can someone explain that for me?). Run the installer, which removes the files and reinstalls them, and now it works.

This might be the first time in all the years of using Linux where I've seen a reinstall actually fix a problem....

This is apparently not an uncommon error message.

If you do a web search for VirtualBox: Error -610 in supR3HardenedMainInitRuntime!, you will find many discussions and posts about this error, far too many for me to recommend just one, as I have no experience with this error.

One of them may give you the information you need. (I suspect that the first error led to the second one.)

It's a two part message. The first part tells you what spawned the supR3HardenedMainInitRuntime error, and apparently there are a lot of different causes...

I didn't understand, WTF: yesterday Virtualbox worked fine but today

VirtualBox: Error -610 in supR3HardenedMainInitRuntime!
VirtualBox: dlopen("/opt/VirtualBox/VBoxRT.so",) failed: <NULL>

P.S. Slackware 14.2 stable

Hello,

I reproduced this error by changing ownerships of /opt directory, so ensure that directory is owned by root.

PoC :
--
SeB

Hi,

got the same error and adding my observations. The access writes for /opt and /opt/VirtualBox are relevant too. If /opt/VirtualBox is writable for everyone, the init will fail:

But if /opt is writable for everyone, the start will fail with:
So just
will fix that.