Opened 8 years ago
Closed 8 years ago
#16513 closed defect (fixed)
VERR_VM_DRIVER_NOT_INSTALLED (Fedora 25 SELinux problem)
| Reported by: | Michael J. Fuhrman | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 5.1.14 |
| Keywords: | Cc: | ||
| Guest type: | Linux | Host type: | Linux |
Description
Fedora 25 recently updated, the new version is .. kernel-4.9.11-200.fc25.x86_64.
While attempting to run '/sbin/vboxconfig', it fails:
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.
There were problems setting up VirtualBox. To re-start ...
Attached will be 4 logs .. the upgrade logs for Linux, and 2 logs for VirtualBox rebuild and the /var/log/vbox-install.log
Attachments (4)
Change History (22)
by , 8 years ago
| Attachment: | 2017-02-25 Yum Update.log added |
|---|
comment:1 by , 8 years ago
The vbox-install.log is 4.9 meg. This system complained that it was too large =(
Let me know how you would like it attached.
follow-up: 4 comment:2 by , 8 years ago
Here are the first few lines of the vbox-install.log
Makefile:185: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again. Stop. Makefile:185: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again. Stop. Makefile:185: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again. Stop. Makefile:185: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again. Stop. Makefile:185: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again. Stop. Makefile:185: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again. Stop. make KBUILD_VERBOSE=1 SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 CONFIG_MODULE_SIG= -C /lib/modules/4.6.7-300.fc24.x86_64/build -j8 modules make[1]: warning: -jN forced in submake: disabling jobserver mode. test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \ echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it."; \ echo >&2 ; \ /bin/false) mkdir -p /tmp/vbox.0/.tmp_versions ; rm -f /tmp/vbox.0/.tmp_versions/*
comment:3 by , 8 years ago
Here is the other relevant piece of the log
/tmp/vbox.0/r0drv/linux/memobj-r0drv-linux.c: In function ‘rtR0MemObjNativeLockUser’:
/tmp/vbox.0/r0drv/linux/memobj-r0drv-linux.c:1053:33: warning: passing argument 4 of ‘get_user_pages’ makes pointer from integer without a cast [-Wint-conversion]
fWrite, /* force write access. */
^~~~~~
In file included from /tmp/vbox.0/r0drv/linux/the-linux-kernel.h:98:0,
from /tmp/vbox.0/r0drv/linux/memobj-r0drv-linux.c:31:
./include/linux/mm.h:1280:6: note: expected ‘struct page **’ but argument is of type ‘int’
long get_user_pages(unsigned long start, unsigned long nr_pages,
^~~~~~~~~~~~~~
/tmp/vbox.0/r0drv/linux/memobj-r0drv-linux.c:1054:33: error: passing argument 5 of ‘get_user_pages’ from incompatible pointer type [-Werror=incompatible-pointer-types]
&pMemLnx->apPages[0], /* Page array. */
^
In file included from /tmp/vbox.0/r0drv/linux/the-linux-kernel.h:98:0,
from /tmp/vbox.0/r0drv/linux/memobj-r0drv-linux.c:31:
./include/linux/mm.h:1280:6: note: expected ‘struct vm_area_struct **’ but argument is of type ‘struct page **’
long get_user_pages(unsigned long start, unsigned long nr_pages,
^~~~~~~~~~~~~~
/tmp/vbox.0/r0drv/linux/memobj-r0drv-linux.c:1050:18: error: too many arguments to function ‘get_user_pages’
rc = get_user_pages(R3Ptr, /* Where from. */
^~~~~~~~~~~~~~
In file included from /tmp/vbox.0/r0drv/linux/the-linux-kernel.h:98:0,
from /tmp/vbox.0/r0drv/linux/memobj-r0drv-linux.c:31:
./include/linux/mm.h:1280:6: note: declared here
long get_user_pages(unsigned long start, unsigned long nr_pages,
^~~~~~~~~~~~~~
/tmp/vbox.0/r0drv/linux/memobj-r0drv-linux.c:1067:33: warning: passing argument 6 of ‘get_user_pages_remote’ makes pointer from integer without a cast [-Wint-conversion]
fWrite, /* force write access. */
^~~~~~
In file included from /tmp/vbox.0/r0drv/linux/the-linux-kernel.h:98:0,
from /tmp/vbox.0/r0drv/linux/memobj-r0drv-linux.c:31:
./include/linux/mm.h:1276:6: note: expected ‘struct page **’ but argument is of type ‘int’
long get_user_pages_remote(struct task_struct *tsk, struct mm_struct *mm,
^~~~~~~~~~~~~~~~~~~~~
/tmp/vbox.0/r0drv/linux/memobj-r0drv-linux.c:1068:33: error: passing argument 7 of ‘get_user_pages_remote’ from incompatible pointer type [-Werror=incompatible-pointer-types]
&pMemLnx->apPages[0], /* Page array. */
^
In file included from /tmp/vbox.0/r0drv/linux/the-linux-kernel.h:98:0,
from /tmp/vbox.0/r0drv/linux/memobj-r0drv-linux.c:31:
./include/linux/mm.h:1276:6: note: expected ‘struct vm_area_struct **’ but argument is of type ‘struct page **’
long get_user_pages_remote(struct task_struct *tsk, struct mm_struct *mm,
^~~~~~~~~~~~~~~~~~~~~
/tmp/vbox.0/r0drv/linux/memobj-r0drv-linux.c:1061:18: error: too many arguments to function ‘get_user_pages_remote’
rc = get_user_pages_remote(
^~~~~~~~~~~~~~~~~~~~~
In file included from /tmp/vbox.0/r0drv/linux/the-linux-kernel.h:98:0,
from /tmp/vbox.0/r0drv/linux/memobj-r0drv-linux.c:31:
./include/linux/mm.h:1276:6: note: declared here
long get_user_pages_remote(struct task_struct *tsk, struct mm_struct *mm,
^~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
scripts/Makefile.build:293: recipe for target '/tmp/vbox.0/r0drv/linux/memobj-r0drv-linux.o' failed
make[2]: *** [/tmp/vbox.0/r0drv/linux/memobj-r0drv-linux.o] Error 1
make[2]: *** Waiting for unfinished jobs....
comment:4 by , 8 years ago
Replying to E Net ARch:
Makefile:185: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again. Stop.
I believe that the error is clear. When you install the VBox kernel modules they need to be compiled before they're used. That requires the kernel headers for the currently running kernel. You don't have them installed. Install them and the VBox modules will compile.
May I suggest something? It's usually better and faster, if problems like this one (configuration, question) get first addressed in the forums (https://forums.virtualbox.org/). More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is most probably not a bug and someone from the developers has to deal with it and close it as "Invalid".
So, if you can, please open a new thread in the VirtualBox on Linux Hosts section of the forums.
Also, consider changing your favorite internet search engine. There should be plenty of results about this, but, the search engine you're using now, does not seem to return any results for some reason.
comment:5 by , 8 years ago
Providing information on how this got posted here ... I used Google as my search engine. I searched there using your system. I looked at the various categories to see if I could drill down to the solution.
Maybe there needs to be a forum created for just this ERROR, with a list of TRY THIS FIRST!!!
Hope this helps.
comment:6 by , 8 years ago
Downloaded the latest RPM and attempted to install it ...
g-io-error-quark: GDBus.Error:org.freedesktop.DBus.Python.OSError: Traceback (most recent call last):
File "/usr/lib64/python3.5/site-packages/dbus/service.py", line 707, in _message_cb
retval = candidate_method(self, *args, **keywords)
File "/usr/lib/python3.5/site-packages/dnfdaemon/server/__init__.py", line 83, in newFunc
rc = func(*args, **kwargs)
File "/usr/share/dnfdaemon/dnfdaemon-system", line 404, in Install
value = self.install(cmds)
File "/usr/lib/python3.5/site-packages/dnfdaemon/server/__init__.py", line 412, in install
po = self.base.add_remote_rpm(cmd)
File "/usr/lib/python3.5/site-packages/dnf/base.py", line 925, in add_remote_rpm
return self.sack.add_cmdline_package(path)
OSError: Can not load RPM file: (1).rpm.
(36)
comment:7 by , 8 years ago
[root@localhost mfuhrman]# yum install kernel-headers Redirecting to '/usr/bin/dnf install kernel-headers' (see 'man yum2dnf') Last metadata expiration check: 0:52:34 ago on Sun Feb 26 08:08:00 2017. Package kernel-headers-4.9.11-200.fc25.x86_64 is already installed, skipping. Dependencies resolved. Nothing to do. Complete! [root@localhost mfuhrman]#
comment:8 by , 8 years ago
Attempted to uninstall and reinstall virtualbox ...
[root@localhost mfuhrman]# yum install VirtualBox.x86_64 Redirecting to '/usr/bin/dnf install VirtualBox.x86_64' (see 'man yum2dnf') Last metadata expiration check: 0:59:48 ago on Sun Feb 26 08:08:00 2017. Dependencies resolved. ========================================================================================================================================= Package Arch Version Repository Size ========================================================================================================================================= Installing: VirtualBox x86_64 5.1.14-1.fc25 rpmfusion-free-updates 7.2 M VirtualBox-kmodsrc x86_64 5.1.14-1.fc25 rpmfusion-free-updates 787 k VirtualBox-server x86_64 5.1.14-1.fc25 rpmfusion-free-updates 14 M akmod-VirtualBox x86_64 5.1.14-1.fc25 rpmfusion-free-updates 27 k Transaction Summary ========================================================================================================================================= Install 4 Packages Total download size: 22 M Installed size: 62 M Is this ok [y/N]: y Downloading Packages: (1/4): akmod-VirtualBox-5.1.14-1.fc25.x86_64.rpm 72 kB/s | 27 kB 00:00 (2/4): VirtualBox-kmodsrc-5.1.14-1.fc25.x86_64.rpm 376 kB/s | 787 kB 00:02 (3/4): VirtualBox-5.1.14-1.fc25.x86_64.rpm 1.0 MB/s | 7.2 MB 00:06 (4/4): VirtualBox-server-5.1.14-1.fc25.x86_64.rpm 679 kB/s | 14 MB 00:21 ----------------------------------------------------------------------------------------------------------------------------------------- Total 1.0 MB/s | 22 MB 00:22 Running transaction check Transaction check succeeded. Running transaction test The downloaded packages were saved in cache until the next successful transaction. You can remove cached packages by executing 'dnf clean packages'. Error: Transaction check error: file /usr/bin/VBox from install of VirtualBox-server-5.1.14-1.fc25.x86_64 conflicts with file from package VirtualBox-5.1-5.1.14_112924_fedora25-1.x86_64 file /usr/bin/VBoxTunctl from install of VirtualBox-server-5.1.14-1.fc25.x86_64 conflicts with file from package VirtualBox-5.1-5.1.14_112924_fedora25-1.x86_64 file /usr/bin/vbox-img from install of VirtualBox-server-5.1.14-1.fc25.x86_64 conflicts with file from package VirtualBox-5.1-5.1.14_112924_fedora25-1.x86_64 file /usr/share/icons/hicolor/128x128/apps/virtualbox.png from install of VirtualBox-server-5.1.14-1.fc25.x86_64 conflicts with file from package VirtualBox-5.1-5.1.14_112924_fedora25-1.x86_64 file /usr/share/icons/hicolor/16x16/apps/virtualbox.png from install of VirtualBox-server-5.1.14-1.fc25.x86_64 conflicts with file from package VirtualBox-5.1-5.1.14_112924_fedora25-1.x86_64 file /usr/share/icons/hicolor/20x20/apps/virtualbox.png from install of VirtualBox-server-5.1.14-1.fc25.x86_64 conflicts with file from package VirtualBox-5.1-5.1.14_112924_fedora25-1.x86_64 file /usr/share/icons/hicolor/32x32/apps/virtualbox.png from install of VirtualBox-server-5.1.14-1.fc25.x86_64 conflicts with file from package VirtualBox-5.1-5.1.14_112924_fedora25-1.x86_64 file /usr/share/icons/hicolor/40x40/apps/virtualbox.png from install of VirtualBox-server-5.1.14-1.fc25.x86_64 conflicts with file from package VirtualBox-5.1-5.1.14_112924_fedora25-1.x86_64 file /usr/share/icons/hicolor/48x48/apps/virtualbox.png from install of VirtualBox-server-5.1.14-1.fc25.x86_64 conflicts with file from package VirtualBox-5.1-5.1.14_112924_fedora25-1.x86_64 file /usr/share/icons/hicolor/64x64/apps/virtualbox.png from install of VirtualBox-server-5.1.14-1.fc25.x86_64 conflicts with file from package VirtualBox-5.1-5.1.14_112924_fedora25-1.x86_64 file /usr/share/applications/virtualbox.desktop from install of VirtualBox-5.1.14-1.fc25.x86_64 conflicts with file from package VirtualBox-5.1-5.1.14_112924_fedora25-1.x86_64 file /usr/share/pixmaps/VBox.png from install of VirtualBox-5.1.14-1.fc25.x86_64 conflicts with file from package VirtualBox-5.1-5.1.14_112924_fedora25-1.x86_64 Error Summary ------------- [root@localhost mfuhrman]#
comment:9 by , 8 years ago
For some reason, Yum Extender is showing VirtualBox-5.1 as installed. When I attempt to uninstall it, it fails.
When I ran .. >yum list installed .. also attached .. I don't see this package installed.
/me groans. =(
comment:10 by , 8 years ago
correction .. FOUND IT ...
[root@localhost mfuhrman]# yum list installed | grep Virtual Redirecting to '/usr/bin/dnf list installed' (see 'man yum2dnf') VirtualBox-5.1.x86_64 5.1.14_112924_fedora25-1 @@commandline
comment:11 by , 8 years ago
[root@localhost mfuhrman]# yum remove VirtualBox-5.1.x86_64 Redirecting to '/usr/bin/dnf remove VirtualBox-5.1.x86_64' (see 'man yum2dnf') Dependencies resolved. ========================================================================================================================================= Package Arch Version Repository Size ========================================================================================================================================= Removing: VirtualBox-5.1 x86_64 5.1.14_112924_fedora25-1 @@commandline 146 M Transaction Summary ========================================================================================================================================= Remove 1 Package Installed size: 146 M Is this ok [y/N]: y Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Erasing : VirtualBox-5.1-5.1.14_112924_fedora25-1.x86_64 1/1 Verifying : VirtualBox-5.1-5.1.14_112924_fedora25-1.x86_64 1/1 Removed: VirtualBox-5.1.x86_64 5.1.14_112924_fedora25-1 Complete! [root@localhost mfuhrman]#
comment:12 by , 8 years ago
Some Progress ... =)
[root@localhost mfuhrman]# yum install VirtualBox.x86_64 Redirecting to '/usr/bin/dnf install VirtualBox.x86_64' (see 'man yum2dnf') Last metadata expiration check: 1:15:28 ago on Sun Feb 26 08:08:00 2017. Dependencies resolved. ========================================================================================================================================= Package Arch Version Repository Size ========================================================================================================================================= Installing: VirtualBox x86_64 5.1.14-1.fc25 rpmfusion-free-updates 7.2 M VirtualBox-kmodsrc x86_64 5.1.14-1.fc25 rpmfusion-free-updates 787 k VirtualBox-server x86_64 5.1.14-1.fc25 rpmfusion-free-updates 14 M akmod-VirtualBox x86_64 5.1.14-1.fc25 rpmfusion-free-updates 27 k Transaction Summary ========================================================================================================================================= Install 4 Packages Total size: 22 M Installed size: 62 M Is this ok [y/N]: y Downloading Packages: [SKIPPED] VirtualBox-5.1.14-1.fc25.x86_64.rpm: Already downloaded [SKIPPED] VirtualBox-server-5.1.14-1.fc25.x86_64.rpm: Already downloaded [SKIPPED] akmod-VirtualBox-5.1.14-1.fc25.x86_64.rpm: Already downloaded [SKIPPED] VirtualBox-kmodsrc-5.1.14-1.fc25.x86_64.rpm: Already downloaded Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Installing : VirtualBox-kmodsrc-5.1.14-1.fc25.x86_64 1/4 Installing : akmod-VirtualBox-5.1.14-1.fc25.x86_64 2/4 Installing : VirtualBox-server-5.1.14-1.fc25.x86_64 3/4 Installing : VirtualBox-5.1.14-1.fc25.x86_64 4/4 Verifying : VirtualBox-5.1.14-1.fc25.x86_64 1/4 Verifying : VirtualBox-server-5.1.14-1.fc25.x86_64 2/4 Verifying : akmod-VirtualBox-5.1.14-1.fc25.x86_64 3/4 Verifying : VirtualBox-kmodsrc-5.1.14-1.fc25.x86_64 4/4 Installed: VirtualBox.x86_64 5.1.14-1.fc25 VirtualBox-kmodsrc.x86_64 5.1.14-1.fc25 VirtualBox-server.x86_64 5.1.14-1.fc25 akmod-VirtualBox.x86_64 5.1.14-1.fc25 Complete! [root@localhost mfuhrman]#
comment:13 by , 8 years ago
/me sighs ...
The VirtualBox Linux kernel driver (vboxdrv) is probably not loaded. You may not have kernel driver installed for kernel that is runnig, if so you may do as root: dnf install akmod-VirtualBox kernel-devel-$(uname -r)If you installed VirtualBox packages and don't want reboot the system, you may need load the kernel driver, doing as root: akmods; systemctl restart systemd-modules-load.service
where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT.
[root@localhost mfuhrman]# dnf install akmod-VirtualBox kernel-devel-$(uname -r) Last metadata expiration check: 1:19:38 ago on Sun Feb 26 08:08:00 2017. Package akmod-VirtualBox-5.1.14-1.fc25.x86_64 is already installed, skipping. Package kernel-devel-4.9.11-200.fc25.x86_64 is already installed, skipping. Dependencies resolved. Nothing to do. Complete! [root@localhost mfuhrman]#
[root@localhost mfuhrman]# systemctl restart systemd-modules-load.service Job for systemd-modules-load.service failed because the control process exited with error code. See "systemctl status systemd-modules-load.service" and "journalctl -xe" for details. [root@localhost mfuhrman]#
rebooting ???
comment:14 by , 8 years ago
No JOY!!! =(
[root@localhost mfuhrman]# akmods; systemctl restart systemd-modules-load.service
Checking kmods exist for 4.9.11-200.fc25.x86_64 [ OK ]
Job for systemd-modules-load.service failed because the control process exited with error code.
See "systemctl status systemd-modules-load.service" and "journalctl -xe" for details.
[root@localhost mfuhrman]# journalctl -xe
-- Subject: Unit systemd-modules-load.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-modules-load.service has failed.
--
-- The result is failed.
Feb 26 09:34:55 localhost.localdomain systemd[1]: systemd-modules-load.service: Unit entered failed state.
Feb 26 09:34:55 localhost.localdomain audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-module
Feb 26 09:34:55 localhost.localdomain systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.
Feb 26 09:34:58 localhost.localdomain dbus-daemon[999]: [system] Activating service name='org.fedoraproject.Setroubleshootd' requested by ':1.66' (uid=0 pid=986 c
Feb 26 09:34:59 localhost.localdomain dbus-daemon[999]: [system] Successfully activated service 'org.fedoraproject.Setroubleshootd'
Feb 26 09:35:00 localhost.localdomain setroubleshoot[2466]: SELinux is preventing systemd-modules from module_load access on the system /usr/lib/modules/4.9.11-20
Feb 26 09:35:00 localhost.localdomain python3[2466]: SELinux is preventing systemd-modules from module_load access on the system /usr/lib/modules/4.9.11-200.fc25.
***** Plugin catchall (100. confidence) suggests **************************
If you believe that systemd-modules should be allowed module_load access on the vboxdrv.ko system by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# ausearch -c 'systemd-modules' --raw | audit2allow -M my-systemdmodules
# semodule -X 300 -i my-systemdmodules.pp
Feb 26 09:35:00 localhost.localdomain dbus-daemon[1492]: [session uid=1000 pid=1492] Activating service name='org.freedesktop.Notifications' requested by ':1.79'
Feb 26 09:35:00 localhost.localdomain dbus-daemon[1492]: [session uid=1000 pid=1492] Successfully activated service 'org.freedesktop.Notifications'
Feb 26 09:35:00 localhost.localdomain setroubleshoot[2466]: SELinux is preventing systemd-modules from module_load access on the system /usr/lib/modules/4.9.11-20
Feb 26 09:35:00 localhost.localdomain python3[2466]: SELinux is preventing systemd-modules from module_load access on the system /usr/lib/modules/4.9.11-200.fc25.
***** Plugin catchall (100. confidence) suggests **************************
If you believe that systemd-modules should be allowed module_load access on the vboxdrv.ko system by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# ausearch -c 'systemd-modules' --raw | audit2allow -M my-systemdmodules
# semodule -X 300 -i my-systemdmodules.pp
Feb 26 09:35:00 localhost.localdomain setroubleshoot[2466]: SELinux is preventing systemd-modules from module_load access on the system /usr/lib/modules/4.9.11-20
Feb 26 09:35:00 localhost.localdomain python3[2466]: SELinux is preventing systemd-modules from module_load access on the system /usr/lib/modules/4.9.11-200.fc25.
***** Plugin catchall (100. confidence) suggests **************************
If you believe that systemd-modules should be allowed module_load access on the vboxdrv.ko system by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# ausearch -c 'systemd-modules' --raw | audit2allow -M my-systemdmodules
# semodule -X 300 -i my-systemdmodules.pp
Feb 26 09:35:00 localhost.localdomain setroubleshoot[2466]: SELinux is preventing systemd-modules from module_load access on the system /usr/lib/modules/4.9.11-20
Feb 26 09:35:00 localhost.localdomain python3[2466]: SELinux is preventing systemd-modules from module_load access on the system /usr/lib/modules/4.9.11-200.fc25.
***** Plugin catchall (100. confidence) suggests **************************
If you believe that systemd-modules should be allowed module_load access on the vboxdrv.ko system by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# ausearch -c 'systemd-modules' --raw | audit2allow -M my-systemdmodules
# semodule -X 300 -i my-systemdmodules.pp
lines 2525-2590/2590 (END)
comment:15 by , 8 years ago
changes applied ...
[root@localhost mfuhrman]# ausearch -c 'systemd-modules' --raw | audit2allow -M my-systemdmodules ******************** IMPORTANT *********************** To make this policy package active, execute: semodule -i my-systemdmodules.pp [root@localhost mfuhrman]# semodule -X 300 -i my-systemdmodules.pp [root@localhost mfuhrman]#
Attempted to restart the service ...
[root@localhost mfuhrman]# akmods; systemctl restart systemd-modules-load.service Checking kmods exist for 4.9.11-200.fc25.x86_64 [ OK ] [root@localhost mfuhrman]#
comment:17 by , 8 years ago
| Summary: | VERR_VM_DRIVER_NOT_INSTALLED → VERR_VM_DRIVER_NOT_INSTALLED (Fedora 25 SELinux problem) |
|---|
comment:18 by , 8 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
After I was able to reproduce the problem with a clean Fedora 25 installation we tried again after a few days and then it worked without any problem.
So please download the Fedora 25 iso image, update the guest to the latest packages, then install the Guest Additions (use the 5.1.16 ones) and reboot the guest. It should work without any SELinux problems.
Note:
See TracTickets
for help on using tickets.
First Update Log for Linux