On Tue, 28 Feb 2017 12:54:22 -0600 William Moreno <williamjmorenor@xxxxxxxxx> wrote: > Hello > > 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 :( Not sure this is really something for devel list (In fact there's a long thread on the users list this morning about this very issue). It's a selinux-policy bug, fixed in the latest selinux policy that went out early this morning: https://bodhi.fedoraproject.org/updates/FEDORA-2017-e06f91350b Update to that one. kevin
Attachment:
pgpW3ER6ShAY9.pgp
Description: OpenPGP digital signature
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
