i think there are two problems, neither of them is with virtualbox
itself so you can upvote that again actually.
the kernel looks for the dkms_autoinstaller file on installation and
does nothing if not found (it's not in dkms), so the modules dont get
rebuilt at kernel install time.
but i dont think they really need to, they should (and do) get built
when the kernel is booted the first time. what's not working is the
fedora-loadmodules service (which loads the modules in preload) is being
loaded before dkms.service (which builds the modules) and not after.
Possibly because we have a Wants=fedora-loadmodules in dkms.service,
shouldn't it be a Before=fedora-loadmodules?
Looks like new kernel installation does not trigger dkms to rebuild
external kernel modules.
2015-07-28 23:40 GMT+02:00 luca pedrielli <luca.pedrielli at gmail.com>:
Il 28/07/2015 20:55, Ben Bullard ha scritto:
VBox is installed and working. Then install new kernel, kernel-devel,
kernel-headers. After rebooting in to new installed kernel dkms is
enabled:
$ systemctl status dkms.service
dkms.service - Builds and install new kernel modules through DKMS
Loaded: loaded (/lib/systemd/system/dkms.service; enabled)
Active: active (exited) since Tue 2015-07-28 13:36:24 CDT; 1min 22s
ago
Docs: man:dkms(8)
Process: 3820 ExecStart=/bin/sh -c dkms autoinstall --verbose
--kernelver $(uname -r) (code=exited, status=0/SUCCESS)
Main PID: 3820 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/dkms.service
But VBox will not open vm giving error in attached screenshot. Though
the
files are in /etc/modprobe.preload.d:
$ ls /etc/modprobe.preload.d
modprobe-preload.conf@ vbox-guest-additions virtualbox
Then if i manually run:
_______________________________________________
OM-Cooker mailing list
[email protected]
http://ml.openmandriva.org/listinfo.cgi/om-cooker-openmandriva.org
