| Summary: | VirtualBox kernel modules fail to load automatically on x86_64 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | David Walser <luigiwalser> |
| Component: | RPM Packages | Assignee: | Thomas Backlund <tmb> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | ||
| Version: | 5 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | virtualbox-5.0.14-1.mga5.src.rpm, kmod-virtualbox-5.0.14-1.mga5.src.rpm | CVE: | |
| Status comment: | |||
|
Description
David Walser
2016-02-25 01:04:19 CET
I'm using the same 64 bit packages and have never had to manually load vboxdrv lsmod | grep vboxdrv vboxdrv 458752 2 vboxnetadp,vboxnetflt OK, I figured it out again. I had figured it out when I set up the 32-bit install and then forgot about it. In msec secure mode, services aren't enabled by default when you install packages that call _post_service, so virtualbox.service isn't enabled, and therefore the kernel modules aren't loaded. Maybe rather than using a SysV service to load the kernel modules, the virtualbox package should just install a file /etc/modprobe.preload.d/virtualbox with the three kernel modules listed. Status:
NEW =>
RESOLVED |