> With the last system update I have seem a message in system start up
> about a error loading kernel modules, after that VirtualBox do not
> start because the apropiate module can not been loaded.
> https://bugzilla.redhat.com/show_bug.cgi?id=1426836
> There is another report about VirtualBox not running:
> https://bugzilla.redhat.com/show_bug.cgi?id=1427525
> I do not like VirtualBox but I need it because I am working with a
> web app than only provides a .ova file to work locally and looks like
> I am not the only one that can not start VirtualBox after updating
> Fedora 25, trying old kernels do not work for me :(

A work-around is to set selinux to permissive mode, restart the vbox service, then re-enable selinux enforcing mode.
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-leave@lists.fedoraproject.org