| Summary: | module for VirtualBox is missing in 2.6.38.1-desktop-1.mga | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Kristoffer Grundström <lovaren> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | ftg |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | kernel-2.6.38.1-desktop-1.mga | CVE: | |
| Status comment: | |||
| Attachments: | Here's the proof of what's installed | ||
|
Kristoffer Grundström
2011-03-29 15:03:50 CEST
Source RPM:
kernel =>
kernel-2.6.38.1-desktop-1.mga
Kristoffer Grundström
2011-03-29 15:04:00 CEST
Hardware:
All =>
i586 Problem is solved when you boot to the next kernel. The boot-sequence will install virtualbox-module. Should I close as fixed? Created attachment 172 [details]
Here's the proof of what's installed
Still no VirtualBox-dir in /usr/bin/ Had to reload the file-list in rpmdrake to see the guest-additions-package for Virtualbox to, but it has conflicts when installing the 6th-version of 4.04 'cause of missing kmod (vboxdrv). You only need the virtualbox-guest-additions package if you're installing Mageia _inside_ a virtual machine, i.e. when Mageia is the guest OS. For the time being (and as with development releases) you need the -devel-latest package matching the kernel flavour you have, this will enable DKMS to build the necessary kernel modules when you boot a new kernel. Status:
NEW =>
RESOLVED If you happened to install a new kernel before dkms-virtualbox, it probably compiled against the new kernel devel files, producing a module in the /lib/modules for the new kernel, not the one you were running under. That would make it impossible to load the new module until you rebooted with the new kernel. However, it should have at least compiled the driver module during install. Did you notice if it rebuilt the module during the reboot ? CC:
(none) =>
ftg |
Description of problem: I installed Virtualbox & ran it to create a machine. When executing the machine I see the message that I should do '/etc/init.d/vboxdrv setup' as root. I went to Terminal & logged in as root. Wrote that command & got: -bash: /etc/init.d/vboxdrv setup: File or directory doesn't exist Version-Release number of selected component (if applicable): 4.0.4 How reproducible: Everytime. Steps to Reproduce: 1. Open Terminal. 2. Login as root. 3. Type urpmi virtualbox & press Enter (or use the graphical way if you prefer that way instead). 4. See that dkms-virtualbox gets installed as well. 5. Run virtualbox. 6. Create a machine & attach an ISO-image. 7. Run the machine. 8. A window will appear telling you the following thing: "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. Users of Ubuntu, Fedora or Mandriva should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary." Conlusion: I found the sh-file for VBox by typing locate VBox.sh & found it in /usr/share/virtualbox After that I tried to execute byt doing the following: [kristoffer@ip7-12 virtualbox]$ ./VBox.sh WARNING: The vboxdrv kernel module is not loaded. Either there is no module available for the current kernel (2.6.38.1-desktop-1.mga) or it failed to load. Please recompile the kernel module and install it by sudo /etc/rc.d/init.d/virtualbox start You will not be able to start VMs until this problem is fixed. Unknown application - VBox.sh Output of rpm -qa | grep virtualbox is: dkms-virtualbox-4.0.4-6.mga1 virtualbox-doc-4.0.4-6.mga1 virtualbox-4.0.4-6.mga1 Reproducible: Steps to Reproduce: