Page 1 of 1

Virtual Box stoped working, Fedora 27

Posted: 8. Feb 2018, 04:36
by DrMN
Virtual Box has stopped working as of Fedora 27.

On a freshly installed Fedora 27, installation of VirtualBox-5.2, and VirtualBox-5.1, fails with a modprob error. The error message refers the user to dmesg, but there is nothing in dmesg related to the error.

The failure is duplicated on three different machines, and has posted widely on other bulletin boards.

As far as F27 is concerned, vbox is broken.

Re: Virtual Box stoped working, Fedora 27

Posted: 8. Feb 2018, 09:20
by andyp73
OK, so if the modprob error refers you to dmesg and there is nothing in the dmesg output that helps then we need more detail of what the error message said in order to be able to help diagnose the issue.

I know of one user of Fedora that had a similar sounding issue that resolved it by turning off secure boot but at this point in time that is just a wild shot in the dark and could be way off target!

-Andy.

Re: Virtual Box stoped working, Fedora 27

Posted: 8. Feb 2018, 11:18
by socratis
DrMN wrote:fails with a modprob error
"A" modprobe error? Don't you think that you should have mentioned the exact error? Because if the installer fails to ping the kernel module, mainly because it's being uninstalled at the moment, that's a red-herring, it's not an earth shuttering error, it can be safely ignored.
DrMN wrote:As far as F27 is concerned, vbox is broken.
No, it's not broken. Not in the way you think it might be at least...