[opensuse] Driver problem in VirtualBox
I have got VirtualBox installed on my OS v11.1, have configured a VM for WinXP, and am now ready to install the XP guest. VB sees my CDROM drive, and the XP disk is in the drive. Starting the installation process immediatly causes the following error message: ***** VERR_VM_DRIVER_NOT_INSTALLED (rc=-1908) The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Re-setup the kernel module by executing '/etc/init.d/vboxdrv setup' as root. Users of Ubuntu or Fedora should install the DKMS package at first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary. ***** I of course ran the setup as instructed above, with the following result: ***** # /etc/init.d/vboxdrv setup Stopping VirtualBox kernel module done Recompiling VirtualBox kernel module, NOT. It has been packaged. done Starting VirtualBox kernel module failed (No suitable module for running kernel found) # / What would be a "suitable module" for running the kernel? The driver file is indeed present. Here are its details: -rwxr--r-- 1 root root 7816 2009-02-25 21:24 /etc/init.d/vboxdrv Since the file was installed by the VB installation process, I assume that its permisstions and ownership are correct. What exactly is lacking? -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Il giorno gio, 18/06/2009 alle 12.17 +0300, Stan Goodman ha scritto:
I have got VirtualBox installed on my OS v11.1, have configured a VM for WinXP, and am now ready to install the XP guest. VB sees my CDROM drive, and the XP disk is in the drive.
Starting the installation process immediatly causes the following error message:
***** VERR_VM_DRIVER_NOT_INSTALLED (rc=-1908)
The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Re-setup the kernel module by executing
'/etc/init.d/vboxdrv setup'
as root. Users of Ubuntu or Fedora should install the DKMS package at first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary. *****
I of course ran the setup as instructed above, with the following result:
***** # /etc/init.d/vboxdrv setup Stopping VirtualBox kernel module done Recompiling VirtualBox kernel module, NOT. It has been packaged. done Starting VirtualBox kernel module failed (No suitable module for running kernel found) # /
What would be a "suitable module" for running the kernel?
The driver file is indeed present. Here are its details:
-rwxr--r-- 1 root root 7816 2009-02-25 21:24 /etc/init.d/vboxdrv
Since the file was installed by the VB installation process, I assume that its permisstions and ownership are correct.
What exactly is lacking?
Hi, ensure you have installed the right compiling requirements, in order to built the VBox driver: *kernel-source * kernel-syms * Xalan-c * Xerces-c * gcc * make Good Luck! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hi Stan Am Donnerstag 18 Juni 2009 11:17:33 schrieb Stan Goodman:
I have got VirtualBox installed on my OS v11.1, have configured a VM for WinXP, and am now ready to install the XP guest. VB sees my CDROM drive, and the XP disk is in the drive.
I hope you are using the packages containe dwith openSUSE or the ones from the Build Service. If you want to compile it yourself it would be much more difficult to help you and everithing below will not help you.
Starting the installation process immediatly causes the following error message:
***** VERR_VM_DRIVER_NOT_INSTALLED (rc=-1908)
The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Re-setup the kernel module by executing
'/etc/init.d/vboxdrv setup'
as root. Users of Ubuntu or Fedora should install the DKMS package at first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary. *****
For openSUSE that's similar. You will need the virtualbox-ose-kmp rpm matching your kernel installed. Usually this will be automatically pulled in by the virtualbox-ose package.
I of course ran the setup as instructed above, with the following result:
***** # /etc/init.d/vboxdrv setup Stopping VirtualBox kernel module done Recompiling VirtualBox kernel module, NOT. It has been packaged. done Starting VirtualBox kernel module failed (No suitable module for running kernel found) # /
There is no need to run this setup when a suitable kernel module is already installed.
What would be a "suitable module" for running the kernel?
The driver file is indeed present. Here are its details:
-rwxr--r-- 1 root root 7816 2009-02-25 21:24 /etc/init.d/vboxdrv
Since the file was installed by the VB installation process, I assume that its permisstions and ownership are correct.
Thats not the driver. This is only the script to start it via init. The module file is vboxdrv.ko below the /lib/modules folder.
What exactly is lacking?
The simplest thing is, that the module is simply not loaded. You can load it with "sudo /usr/bin/rcvboxdrv start". You can make this permanent with "sudo /sbin/insserv vboxdrv". For me this gives an error message, that it cannot load the vboxfs.ko module. This can be ignored. But a consequence of the error is, that I cannot share files between host and client. An easy workaround is the use of a network connection instead. Herbert -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 18 June 2009 04:17:33 am Stan Goodman wrote:
I have got VirtualBox installed on my OS v11.1, have configured a VM for WinXP, and am now ready to install the XP guest. VB sees my CDROM drive, and the XP disk is in the drive.
<snip>
***** # /etc/init.d/vboxdrv setup Stopping VirtualBox kernel module done Recompiling VirtualBox kernel module, NOT. It has been packaged. done Starting VirtualBox kernel module failed (No suitable module for running kernel found) # /
Stan, I'm sure you have it fixed by now, but if not, here is the short version: (1) Check "lsmod | grep vbox" If you don't see: 18:06 alchemy:~> lsmod | grep vbox vboxnetflt 122220 0 vboxdrv 1719660 1 vboxnetflt then your driver isn't loaded. (2) You did the right thing with /etc/rc.d/vboxdrv setup (or rcvboxdrv setup). If the compile of the driver failed, you have problem with your compile tools. I seriously recommend with all openSuSE installs, that in yast either during install or after, install the patterns for (Yast2 -> SW Management -> Patterns) "Base Development", "C/C++ Development", "Linux Kernel Development" and "Console Tools". This will insure you have the necessary compilers as well as the kernel source (against which to compile needed modules) in the event that you need to compile modules for something (VirtualBox in your case) (3) Additionally, I use the virtualbox package from virtualbox.org and I have not had any problems: http://www.virtualbox.org/wiki/Downloads (4) When installing XP, why not just create an .iso image to install from. Then just choose the option in virtualbox to mount CD-ROM image instead of the actual CD-ROM drive (you are legally able to create a backup of your XP install media -- and the install goes much faster ;-) -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
David C. Rankin -
Herbert Graeber -
Marco Calistri -
Stan Goodman