On Tuesday 20 October 2009, Hugo Garcia wrote: > On Tue, Oct 20, 2009 at 12:19 PM, upscope <[email protected]> wrote: > >> [...] > >> Cannot access the kernel driver! > >> > >> 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' > >> > >> ---- > >> but there is no '/etc/init.d/vboxdrv setup' installed?! > >> --- > >> > >> Anyone out there building their own VB on openSUSE? > >> > >> -H > >> > >> _______________________________________________ > >> vbox-users mailing list > >> [email protected] > >> http://vbox.innotek.de/mailman/listinfo/vbox-users > > > > The line "/etc/init.d/vboxdrv setup" is a command for building the > > driver. if you look in /etc/init.d you should see a file vboxdrv, if > > there make sure it is executable. > > rwxr-xr-x 1 root root 10976 2009-10-02 04:16 /etc/init.d/vboxdrv > > > > Not you must execute as root. > > the rest of the line setup will compile the driver. Leave off the > > quotes. Also another option is status - will tell if driver is installed. > > > > ebgz:~> /etc/init.d/vboxdrv status > > VirtualBox kernel modules (vboxdrv, vboxnetflt and vboxnetadp) are > > loaded.
/etc/init.d/vboxdrv is not available if you compile VBox yourself. > > If you do not see vboxdrv in /etc/vboxdrv then something went wrong with > > your build. Why not use the ose version located in the oSS repository or > > if you > > that is the problem: it is NOT preseent although it seems the build > completes and I even am able to load the module as per modprobe -l. > > will have to check he build. The make file doesn't quit with an error. > > Is there an expected message at the the end of the build process? It should be obvious if the whole build process was successful. After that, load the three modules with modprobe (as you already did) and verify with lsmod that they are really loaded. Then make sure that the permissions of /dev/vboxdrv and /dev/vboxnetctl are correct. For a non-hardened build the current user must be able to read/write both devices. A hardened build will open these devices as suid root and should not have such problem. > > need the usb support download the free proprietary version from the Sun > > website (http://www.virtualbox.org/wiki/Linux_Downloads)? Then use YaST > > to install it. > > I want to use the Windows XP CD that came with the machine. I > understand that I have to recompile VirtualBox so that returns > identifying strings that are inherent with my BIOS and that XP uses to > verify the activation. Recompiling VBox is not necessary to fake these strings. Have a look at the user manual section 9.14. Kind regards, Frank -- Dr.-Ing. Frank Mehnert Sitz der Gesellschaft: Sun Microsystems GmbH, Sonnenallee 1, 85551 Kirchheim-Heimstetten Amtsgericht München: HRB 161028 Geschäftsführer: Thomas Schröder, Wolfgang Engels, Wolf Frenkel Vorsitzender des Aufsichtsrates: Martin Häring
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
