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:
# modprobe vboxdrv vboxnetflt vboxnetadp vboxguest vboxsf
then VBox works again and continues to work on subsequent reboots as
normal . But users aren't supposed to have to manually run modprobe
command every time they install a new kernel. So I'm wrong about one
thing, kernel modules are built or modprobe wouldn't work they just
aren't being loaded automatically after installing a new kernel.
Based on that I changed title of this e-mail. Thanks Luca for helping
me sort out the real problem.
Hi Ben,
i think this is a possible issue the first time you use new kernel version.
dkms service build new modules, but are they ready when the system
tries to preload them?
i think that, on second reboot with new kernel version, all should be fine.
Ben Bullard
ben79
--------------------
OpenMandriva-QA Team
On 07/28/2015 01:28 AM, luca pedrielli wrote:
Il 28/07/2015 01:14, Ben Bullard ha scritto:
On a system with VBox 5.0 working with kernel-nrjQL-desktop-3.18.16.
Then enabled nicco's repo for kernel 3.19.x. Attached is output of
'# urpmi --debug --auto-select'. VBox kernel modules don't get built.
and what happens if you reboot with the new kernel?
is dkms service enabled?
Ben Bullard
ben79
--------------------
OpenMandriva-QA Team
On 07/27/2015 05:07 PM, Ben Bullard wrote:
The vbox 5.0 in main testing does not seem to build kernel modules
when a new kernel module is installed. Isn't that what dkms is
supposed to do. See screenshot. I've repeated this a number of
times. Also what the error message is telling to do won't work:
# /etc/init.d/vboxdrv setup
-bash: /etc/init.d/vboxdrv: No such file or directory
Problem is I already voted this up in kahinah. Just changed my
vote. Don't know if that's OK or best way to do this so please advise.
Also I don't know if this is a virtualbox problem or a dkms problem.
--
Ben Bullard
ben79
--------------------
OpenMandriva-QA Team
_______________________________________________
OM-QA mailing list
[email protected]
http://ml.openmandriva.org/listinfo.cgi/om-qa-openmandriva.org
_______________________________________________
OM-Cooker mailing list
[email protected]
http://ml.openmandriva.org/listinfo.cgi/om-cooker-openmandriva.org
--
Saluti, Luca Pedrielli
_______________________________________________
OM-Cooker mailing list
[email protected]
http://ml.openmandriva.org/listinfo.cgi/om-cooker-openmandriva.org
_______________________________________________
OM-QA mailing list
[email protected]
http://ml.openmandriva.org/listinfo.cgi/om-qa-openmandriva.org
--
Saluti, Luca Pedrielli
_______________________________________________
OM-Cooker mailing list
[email protected]
http://ml.openmandriva.org/listinfo.cgi/om-cooker-openmandriva.org
