system failing to load virtualbox modules

[William Moreno]

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 :(

Regards

William Moreno Reyes
http://about.me/williamjmorenor

[Kevin Fenzi]

On Tue, 28 Feb 2017 12:54:22 -0600
William Moreno  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

[Andrew Lofthouse]

> > 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 -- [e-mail]
> To unsubscribe send an email to [e-mail]

[Jos de Kloe]

You did not menthon what copy of VirtualBox you used, and that makes a
difference.
I have been running the copy from rpmfusion for some time, and
experienced the same trouble you had. It often breaks after
updates/upgrades, forcing me to use old kernel copies.

In the end I decided to fall back to the upstream version provided by
Oracle. Also that one needs to be reinstalled now and then, but at least
it allows me to stay up-to-date to the latest kernel versions, with
selinux in enforcing mode.

Jos

On 02/28/2017 09:20 PM, Andrew Lofthouse wrote:
> >
> > 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
> <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
> <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 -- [e-mail]
> <mailto:[e-mail]>
> To unsubscribe send an email to [e-mail]
> <mailto:[e-mail]>
>
>
>
>
> devel mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]

[Porfirio Andrés Páiz Carrasco]

2017-02-28 14:20 GMT-06:00 Andrew Lofthouse :
> > > 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.

Last but not least, here is a selinux coloring book, it has cats and
dogs, did I mention it is fun?:
https://people.redhat.com/duffy/selinux/selinux-coloring-book_A4-Stapled.pdf
> > devel mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
>
> devel mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]