réjean Posted December 26, 2013 Share Posted December 26, 2013 Hi all! I am having a problem with Vbox in Mageia. I can create a arch.vdi (or any other distro) but when comes the time to start a new machine I get 2 messages; Failed to open a session for the virtual machine arch. The virtual machine 'arch' has terminated unexpectedly during startup with exit code 1. and Kernel driver not installed (rc=-1908) The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing '/etc/init.d/vboxdrv setup' as root. If it is available in your distribution, you should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary. Here is the content of my /etc/init.d: [rejean@localhost ~]$ cd /etc/init.d [rejean@localhost init.d]$ ls -l total 144 -rwxr-xr-x 1 root root 1814 Jan 11 2013 apmd* -rwxr-xr-x 1 root root 1212 Jan 11 2013 bpalogin* -rwxr-xr-x 1 root root 1517 May 8 2013 dm* -rw-r--r-- 1 root root 16466 May 8 2013 functions -rwxr-xr-x 1 root root 1795 Jan 11 2013 hddtemp* -rwxr-xr-x 1 root root 1945 Jan 12 2013 irqbalance* -rwxr-xr-x 1 root root 2985 Feb 3 2013 lm_sensors* -rwxr-xr-x 1 root root 1185 Aug 22 17:05 mandi* -rwxr-xr-x 1 root root 4136 May 8 2013 mandrake_everytime* -rwxr-xr-x 1 root root 345 May 8 2013 mandrake_firstime* -rwxr-xr-x 1 root root 2412 Jan 12 2013 microcode_ctl* -rwxr-xr-x 1 root root 1791 Mar 17 2013 msec* -rwxr-xr-x 1 root root 3317 May 8 2013 netconsole* -rwxr-xr-x 1 root root 8703 May 8 2013 network* -rwxr-xr-x 1 root root 535 May 8 2013 network-auth* -rwxr-xr-x 1 root root 6595 May 8 2013 network-up* -rwxr-xr-x 1 root root 1163 May 8 2013 partmon* -rwxr-xr-x 1 root root 1323 Jan 13 2013 pptp* -rw-r--r-- 1 root root 1160 Sep 22 13:26 README -rwxr-xr-x 1 root root 2155 Mar 24 2013 resolvconf* -rwxr-xr-x 1 root root 5524 Jul 11 06:12 vboxadd-timesync* -rwxr-xr-x 1 root root 9974 Jul 11 06:12 vboxweb-service* -rwxr-xr-x 1 root root 2137 Jul 11 06:12 virtualbox* -rwxr-xr-x 1 root root 1473 Jan 14 2013 vnstat* -rwxr-xr-x 1 root root 1769 Apr 2 2013 wine* [rejean@localhost init.d]$ Quote Link to comment Share on other sites More sharing options...
réjean Posted December 26, 2013 Author Share Posted December 26, 2013 Oh! Here is the detail from the 1st message; Result Code: NS_ERROR_FAILURE (0x80004005) Component: Machine Interface: IMachine {22781af3-1c96-4126-9edf-67a020e0e858} Quote Link to comment Share on other sites More sharing options...
réjean Posted December 26, 2013 Author Share Posted December 26, 2013 I do have the dkms installed; Quote Link to comment Share on other sites More sharing options...
réjean Posted December 26, 2013 Author Share Posted December 26, 2013 I do have a "dev/vboxusb" but that's it, no other "/dev/vbox...". Quote Link to comment Share on other sites More sharing options...
sunrat Posted December 27, 2013 Share Posted December 27, 2013 Hmmm, I do have /etc/init.d/vboxdrv on my system (siduction). How did you install VBox? You also need kernel headers to build the module. Maybe try: -Uninstall VBox -Install kernel-headers -Reinstall VBox and dkms-vbox Quote Link to comment Share on other sites More sharing options...
réjean Posted December 27, 2013 Author Share Posted December 27, 2013 (edited) I am quite sure that I had installed Vbox from Synaptic. I uninstalled it and dkms-vbox and reinstalled them from Synaptic but there are no kernel-headers to install but: [root@localhost rejean]# apt-get install kernel-headers Reading Package Lists... Done Building Dependency Tree... Done Selecting kernel-userspace-headers for 'kernel-headers' kernel-userspace-headers is already the newest version. 0 upgraded, 0 newly installed, 0 removed and 0 not upgraded. [root@localhost rejean]# Edited December 27, 2013 by réjean Quote Link to comment Share on other sites More sharing options...
sunrat Posted December 27, 2013 Share Posted December 27, 2013 I didn't know Mageia used apt-get. Anyway, looks like they are called kernel devel something. See http://paperiniktips.sviluppo-siti-web.com/linux-mageia-how-to-properly-installing-the-kernel-headers/ Quote Link to comment Share on other sites More sharing options...
BarryB Posted December 27, 2013 Share Posted December 27, 2013 Rejean Did you insall the matching "virtualbox-kernel" from from Mageia Control Center? Quote Link to comment Share on other sites More sharing options...
réjean Posted December 27, 2013 Author Share Posted December 27, 2013 (edited) Yes and Yes. I have the kernel-desktop, the kernel-desktop-devel and the kernel-desktop-latest install and also the virtualbox-kernel and the virtualbox-guest-addition and the dkms-virtual box and I just installed the virtualbox-kernel-server-latest just in case it might help. I forgot that Mageia uses RPM ( was just back from spending a few hours in Ubuntu (and I did install APT just to see if it could help installing the "headers" from a terminal)). I notice that I have a lot of 3.8.13.4 and 3.10.24 versions of each packages ( must have been doing an upgrade awhile back) does it hurt? Anyway I am still getting the same messages when I try to start a machine in Vbox. Thanks for your help both of you. Edited December 27, 2013 by réjean Quote Link to comment Share on other sites More sharing options...
BarryB Posted December 27, 2013 Share Posted December 27, 2013 Rejean I am assuming your running Mageia 3 based on the kernel. it could be some miss match stuff... try '/etc/init.d/vboxdrv setup' as root You can start removing old kernels and supporting files...however I would only do it one at a time and through MMC. Quote Link to comment Share on other sites More sharing options...
réjean Posted December 27, 2013 Author Share Posted December 27, 2013 @Barry; 98% of the time when I install something I use MMC. I have tried your suggestion over and over; [rejean@localhost ~]$ su Password: [root@localhost rejean]# /etc/init.d/vboxdrv setup bash: /etc/init.d/vboxdrv: No such file or directory [root@localhost rejean]# I found a thread on Mageia forum and all I had to do is; [rejean@localhost ~]$ su Password: [root@localhost rejean]# urpme virtualbox-kernel-desktop-latest removing virtualbox-kernel-desktop-latest-4.2.16-4.mga3.x86_64 removing package virtualbox-kernel-desktop-latest-4.2.16-4.mga3.x86_64 1/1: removing virtualbox-kernel-desktop-latest-4.2.16-4.mga3.x86_64 ##################################################################### [root@localhost rejean]# urpmi virtualbox-kernel-desktop-latest $MIRRORLIST: media/core/updates/virtualbox-kernel-desktop-latest-4.2.16-4.mga3.x86_64.rpm installing virtualbox-kernel-desktop-latest-4.2.16-4.mga3.x86_64.rpm from /var/cache/urpmi/rpms Preparing... ##################################################################### 1/1: virtualbox-kernel-desktop-latest ##################################################################### [root@localhost rejean]# and that seems to have fixed it. Thanks! Quote Link to comment Share on other sites More sharing options...
BarryB Posted December 28, 2013 Share Posted December 28, 2013 Glad you got it fixed. Yeah the Mageia fourms are pretty good, most fourms it seems to me have come a long, long way from the old RTM days!!! 2 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.