VirtualBox: Failed to open a session for the virtual machine

[SLA]

Hi All,
I tried to use VirtualBox on Linux hosts, which version is Red Hat Enterprise 6.5, the VirtualBox can be installed successfully but got an error when try to run guest OS. The error is as follow:
Result Code: NS_ERROR_FAILURE(0x80004005)
Component: SessionMachine
Interface: ISession{7844aa05-b02e-4cdd-a04f-ade4a762e6b7}

2019-08-20_144424.jpg (79.18 KiB) Viewed 1045 times

2019-08-20_144339.jpg (102.52 KiB) Viewed 1045 times

[socratis]

It's usually easier, more convenient, smaller size, searchable and quotable, if you use that "Copy" button in the error dialog, and simply paste the error text, instead of posting the image...

I can't even start to understand why you would also post part of the log as a picture... Please ZIP and attach the full log.

So, please edit your message and replace the pictures with 1) the Copied Error Code, 2) the ZIPPED VBox.log.

[SLA]

Hi Socratis,

I cannot get log file because of our company security policy, so just snapshots.

I also check ~/.config/VirtualBox/VBoxSVC.log:

2019-08-20_171017.jpg (109.39 KiB) Viewed 1034 times

and ~/.config/VirtualBox/selectorwindows.log:

2019-08-20_171017.jpg (109.39 KiB) Viewed 1034 times

There are many error in that log and I cannot find which error lead to VirtualBox crash

[socratis]

I'm sorry, but without a complete log this is an exercise in futility, seriously...

[MontyMan]

Dear SLA,

If these are company computers that have stopped working, maybe as an IT person you could get an exception to the "no USB devices" rule, in order to get your VMs working again? Or maybe log into this site from the machine experiencing the issue, so you can post it from there?

If not, you could snap pictures of each (overlapping) screen shot, then on a personal machine assemble them using Paint or similar, then use freeware OCR to re-create the log file. I've had some luck with SimpleOCR. You'll have to go back and correct o's and 0's, i's and L's, and similar errors in disambiguation, perhaps using the original. It may even help to (on the original machine) paste into a word processor and try a couple different fonts, to find one that's more accurately scannable with OCR. It's time consuming but it's the only way I can think of to get your log file text.

All best,
.Monty.

[socratis]

Even with the screenshots, I can tell that something is really wrong here:

Synopsys VirtualBox VM 5.2.20 r125587 [BUILD_INFO] linux.amd64 release log

That's not the official VirtualBox. This is a custom build, and not even the 5.2.20 build which was rev. 125813, not 125587. I would completely remove/uninstall/delete/purge that version and install the official version from the Linux Downloads section of VirtualBox.