Virtualbox - Error starting guest NS_ERROR_FAILURE (0x80004005)

Trentanel

It's not a problem with the machine's hardware or BIOS.
I just installed Solus on an external USB drive connected to the same computer, and Virtualbox works.

The only notable difference is the installation mode. In the latter case, I chose “overwrite an entire disk,” whereas for installations where Virtualbox crashes on launch, I used manual mode. I designated the esp and / partitions for formatting and installation.

I don't know what to conclude from this.

AAndresH

Trentanel Well, I tried both ways, normal installation deleting entire disk and manually creating partitions, and it worked normally. Which distro are you trying to test on Virtualbox?

Trentanel

I have that and it does not work

ls -ld /usr/lib64/virtualbox /usr/lib64/virtualbox/components
drwxrwxr-x 4 root root 4096 15 févr. 10:50 /usr/lib64/virtualbox
drwxrwxr-x 2 root root 4096 15 févr. 10:50 /usr/lib64/virtualbox/components

Then I run

sudo chmod 755 /usr/lib64/virtualbox
sudo chmod 755 /usr/lib64/virtualbox/components

to obtain

ls -ld /usr/lib64/virtualbox /usr/lib64/virtualbox/components
drwxr-xr-x 4 root root 4096 15 févr. 10:50 /usr/lib64/virtualbox
drwxr-xr-x 2 root root 4096 15 févr. 10:50 /usr/lib64/virtualbox/components

And virtualbox starts correctly.

Trentanel

AAndresH
Thanks, but the problem is not with distro I want to test. It's the right on /usr/lib64/virtualbox and components. Virtualbox fails from the launch, without log.
On this disc, Archlinux has been replaced by Solus and I kept my data partition. I don't know why the rights are w for group after installation.

Me gusta Solus, ese ha sido mi único problema.

« Previous Page