As per https://bugs.mageia.org/show_bug.cgi?id=6914#c10 the dkms install command is failing.
Blocks: (none) => 6914
seems more the dkms than the kmod one aka dkms-virtualbox vs virtualbox-kernel-3.3.8-desktop
Assignee: bugsquad => tmbSource RPM: kmod-virtualbox-4.1.18-1.mga2.src.rpm => virtualbox
Hm, seems weird... $ rpm -qpl virtualbox-kernel-3.3.8-desktop-2.mga2-4.1.18-1.mga2.x86_64.rpm /var/lib/dkms-binary/virtualbox/4.1.18-1.mga2/3.3.8-desktop-2.mga2 /var/lib/dkms-binary/virtualbox/4.1.18-1.mga2/3.3.8-desktop-2.mga2/dkms.conf /var/lib/dkms-binary/virtualbox/4.1.18-1.mga2/3.3.8-desktop-2.mga2/x86_64 /var/lib/dkms-binary/virtualbox/4.1.18-1.mga2/3.3.8-desktop-2.mga2/x86_64/log /var/lib/dkms-binary/virtualbox/4.1.18-1.mga2/3.3.8-desktop-2.mga2/x86_64/log/make.log /var/lib/dkms-binary/virtualbox/4.1.18-1.mga2/3.3.8-desktop-2.mga2/x86_64/module /var/lib/dkms-binary/virtualbox/4.1.18-1.mga2/3.3.8-desktop-2.mga2/x86_64/module/symvers.gz /var/lib/dkms-binary/virtualbox/4.1.18-1.mga2/3.3.8-desktop-2.mga2/x86_64/module/vboxdrv.ko.xz /var/lib/dkms-binary/virtualbox/4.1.18-1.mga2/3.3.8-desktop-2.mga2/x86_64/module/vboxnetadp.ko.xz /var/lib/dkms-binary/virtualbox/4.1.18-1.mga2/3.3.8-desktop-2.mga2/x86_64/module/vboxnetflt.ko.xz so dkms.conf is there, and is correct: $ cat dkms.conf MAKE[0]="./vboxbuild $kernel_source_dir" PACKAGE_NAME=virtualbox PACKAGE_VERSION=4.1.18-1.mga2 DEST_MODULE_LOCATION[0]=/kernel/3rdparty/vbox BUILT_MODULE_LOCATION[0]=vboxdrv/ BUILT_MODULE_NAME[0]=vboxdrv DEST_MODULE_LOCATION[1]=/kernel/3rdparty/vbox BUILT_MODULE_LOCATION[1]=vboxnetflt/ BUILT_MODULE_NAME[1]=vboxnetflt DEST_MODULE_LOCATION[2]=/kernel/3rdparty/vbox BUILT_MODULE_LOCATION[2]=vboxnetadp/ BUILT_MODULE_NAME[2]=vboxnetadp AUTOINSTALL=yes And the same rpms & scriots works in cauldron... Can you check the rpm is installed and in good shape? Do you have to manually install virtualbox-kernel-3.3.8-desktop-2.mga2-4.1.18-1.mga2 ?
Do you have several dkms installed? What does "dkms status" say?
[root@x2 ~]# dkms status iscsitarget, 1.4.20.3-1.mga2: added fglrx, 8.98, 3.3.8-desktop-2.mga2, x86_64: installed fglrx, 8.98, 3.3.6-desktop-2.mga2, x86_64: installed fglrx, 8.961-1.mga2.nonfree, 3.3.8-desktop-2.mga2, x86_64: installed-binary from 3.3.8-desktop-2.mga2 virtualbox, 4.1.12-1.mga2, 3.3.6-desktop-2.mga2, x86_64: installed-binary from 3.3.6-desktop-2.mga2 fglrx, 8.961-1.mga2.nonfree, 3.3.6-desktop-2.mga2, x86_64: installed-binary from 3.3.6-desktop-2.mga2 virtualbox, 4.1.18-1.mga2, 3.3.8-server-2.mga2, x86_64: installed-binary from 3.3.8-server-2.mga2 virtualbox, 4.1.18-1.mga2, 3.3.8-netbook-2.mga2, x86_64: installed-binary from 3.3.8-netbook-2.mga2 [root@x2 ~]# uname -a Linux x2.hodgins.homeip.net 3.3.6-desktop-2.mga2 #1 SMP Thu May 17 16:25:59 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
# rpm -qa|grep virtualbox-kernel virtualbox-kernel-3.3.8-desktop-2.mga2-4.1.18-1.mga2 virtualbox-kernel-3.3.8-server-2.mga2-4.1.18-1.mga2 virtualbox-kernel-desktop-latest-4.1.18-1.mga2 virtualbox-kernel-server-latest-4.1.18-1.mga2 virtualbox-kernel-3.3.6-desktop-2.mga2-4.1.12-7.mga2 virtualbox-kernel-3.3.8-netbook-2.mga2-4.1.18-1.mga2 virtualbox-kernel-netbook-latest-4.1.18-1.mga2
Ok. Now this is weird ... rpm -Vv virtualbox-kernel-3.3.8-desktop-2.mga2 missing /var/lib/dkms-binary/virtualbox/4.1.18-1.mga2/3.3.8-desktop-2.mga2 missing /var/lib/dkms-binary/virtualbox/4.1.18-1.mga2/3.3.8-desktop-2.mga2/dkms.conf missing /var/lib/dkms-binary/virtualbox/4.1.18-1.mga2/3.3.8-desktop-2.mga2/x86_64 missing /var/lib/dkms-binary/virtualbox/4.1.18-1.mga2/3.3.8-desktop-2.mga2/x86_64/log missing /var/lib/dkms-binary/virtualbox/4.1.18-1.mga2/3.3.8-desktop-2.mga2/x86_64/log/make.log missing /var/lib/dkms-binary/virtualbox/4.1.18-1.mga2/3.3.8-desktop-2.mga2/x86_64/module missing /var/lib/dkms-binary/virtualbox/4.1.18-1.mga2/3.3.8-desktop-2.mga2/x86_64/module/symvers.gz missing /var/lib/dkms-binary/virtualbox/4.1.18-1.mga2/3.3.8-desktop-2.mga2/x86_64/module/vboxdrv.ko.xz missing /var/lib/dkms-binary/virtualbox/4.1.18-1.mga2/3.3.8-desktop-2.mga2/x86_64/module/vboxnetadp.ko.xz missing /var/lib/dkms-binary/virtualbox/4.1.18-1.mga2/3.3.8-desktop-2.mga2/x86_64/module/vboxnetflt.ko.xz From syslog ... Aug 8 04:11:42 x2 MageiaUpdate[25655]: [RPM] virtualbox-kernel-3.3.8-desktop-2.mga2-4.1.18-1.mga2.x86_64 installed Aug 8 04:12:02 x2 MageiaUpdate[25655]: [RPM] kernel-desktop-devel-3.3.8-2.mga2-1-1.mga2.x86_64 installed Aug 8 04:12:02 x2 MageiaUpdate[25655]: [RPM] kernel-desktop-devel-latest-3.3.8-2.mga2.x86_64 installed Aug 8 04:12:04 x2 MageiaUpdate[25655]: [RPM] virtualbox-4.1.18-1.mga2.x86_64 installed I have no idea why the files are missing. I uninstalled the package (with nodeps), then reinstalled # urpmi virtualbox-kernel-3.3.8-desktop-2.mga2 installing virtualbox-kernel-3.3.8-desktop-2.mga2-4.1.18-1.mga2.x86_64.rpm from /var/cache/urpmi/rpms Preparing... ############################################################################### 1/1: virtualbox-kernel-3.3.8-desktop-2.mga2 ############################################################################### vboxdrv.ko.xz: - Installation - Installing to /lib/modules/3.3.8-desktop-2.mga2/dkms-binary/3rdparty/vbox/ vboxnetflt.ko.xz: - Installation - Installing to /lib/modules/3.3.8-desktop-2.mga2/dkms-binary/3rdparty/vbox/ vboxnetadp.ko.xz: - Installation - Installing to /lib/modules/3.3.8-desktop-2.mga2/dkms-binary/3rdparty/vbox/ depmod......... DKMS: install Completed. virtualbox, 4.1.18-1.mga2, 3.3.8-desktop-2.mga2, x86_64: installed-binary from 3.3.8-desktop-2.mga2 virtualbox, 4.1.18-1.mga2, 3.3.8-server-2.mga2, x86_64: installed-binary from 3.3.8-server-2.mga2 virtualbox, 4.1.18-1.mga2, 3.3.8-netbook-2.mga2, x86_64: installed-binary from 3.3.8-netbook-2.mga2 [root@x2 ~]# service virtualbox start Starting virtualbox (via systemctl): [ OK ] [root@x2 ~]# service virtualbox status virtualbox kernel module is not loaded # uname -a Linux x2.hodgins.homeip.net 3.3.8-desktop-2.mga2 The modules do now exist in /lib/modules/3.3.8-desktop-2.mga2/dkms-binary/3rdparty/vbox/ So I manually modprobed all three modules, and now I can run VirtualBox. I do not understand what has caused the problems. There is a problem with the init script reporting ok on the start, when it's failing. No idea why it was failing though. And I don't have any idea how the files in /var/lib/dkms-binary/virtualbox/4.1.18-1.mga2/3.3.8-desktop-2.mga2 either failed to get installed, or got deleted. Until the power supply died last night, I haven't had any problems with this system.
Just fyi, I've tried to recreate the problem, starting with a clean install, followed by installing the packages in the same order as shown in my syslog, without any success. As I can't recreate the problem, I'm taking bug 6914 off of the dependency list.
Blocks: 6914 => (none)
This message is a reminder that Mageia 2 is nearing its end of life. Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- The Mageia Bugsquad
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD