On Sun, Feb 26, 2017 at 2:27 PM, Paul Smith <phhs80@xxxxxxxxx> wrote: >>> >>>> After doing the updates of today (selinux included), virtualbox stopped working: >>>> >>>> # /usr/lib/virtualbox/vboxdrv.sh setup >>>> vboxdrv.sh: Building VirtualBox kernel modules. >>>> vboxdrv.sh: Starting VirtualBox services. >>>> vboxdrv.sh: Building VirtualBox kernel modules. >>>> vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why. >>>> # >>>> >>>> Any ideas? >>> >>> >>> Vbox running fine here on a fully updated F25 system. >>> >>> The message you're getting says to use dmesg for more info... Did you >>> do that? >> >> Thanks, Ed. However, >> >> dmesg | grep vboxdrv >> >> returns nothing. > > But after doing > > dnf --allowerasing downgrade selinux-policy selinux-policy-targeted > > the reported problem disappears. Let me add that I am using Oracle VirtualBox (from http://www.virtualbox.org/): VirtualBox-5.1-5.1.14_112924_fedora25-1.x86_64 Paul _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
