virtualbox vboxdrv

[Onyarian]

Hi,

I'm working with ub-dCore-trusty.

I have importsce virtualbox-4.3.sce from the debextra "http://download.virtualbox.org/virtualbox/debian trusty contrib"

When I run virtualbox comes up the virtualbox-manager OK.
Then when I select the virtualOS there is the error:

Kernel driver not installed (rc=-1908)

The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or
there is a permision 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 compiles the vboxdrv kernel module if necessary.

Then I importsce build-essential, linux-headers-generic, linux-source and module-assistant,
to recompile the driver, but I can't do it

tc@ubt-dC5x-ordjd:~$ sudo /etc/init.d/vboxdrv setup
/sbin/modprobe: invalid option -- 'c'
BusyBox v1.20.2 (2012-08-07 01:31:01 UTC) multi-call binary.

Usage: modprobe [-alrqvsDb] MODULE [symbol=value]...

        -a      Load multiple MODULEs
        -l      List (MODULE is a pattern)
        -r      Remove MODULE (stacks) or do autoclean
        -q      Quiet
        -v      Verbose
        -s      Log to syslog
        -D      Show dependencies
        -b      Apply blacklist to module names too

Stopping VirtualBox kernel modules ...done.
Recompiling VirtualBox kernel modules ...failed!
  (Look at /var/log/vbox-install.log to find out what went wrong)

and /var/log/vbox-install.log says:

Makefile:183: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again.  Stop.

What should I do to recompile the vboxdrv?

Thanks

[Jason W]

I am actually working on this very thing right now.  I plan to build the kernel modules and will upload them to be imported to make it easy to run virtualbox on dCore.  I will also build modules for Core as well.

When the modules are built and availble, it should just be a matter of

importsce virtualbox
importsce virtualbox-modules-3.8.13-tinycore


The Linux source would need to be our 3.8.13 kernel.  Give me a couple days and I should have it.  I am new to virtualbox and will give it some testing before I upload the modules.

[Onyarian]

Ok Jason, glad to hear this, thank you very much.

[Jason W]

Ok, I have built the Virutalbox kernel modules on TC 5.x, which is where the main dCore kernel was built so it is compatible with both.  Also made a startup script for Virtualbox for it to run as expected.  I am running a live cd distro through VB on dCore-jessie now, sound and network and all is working nicely.

I will visit the guest-additions later.  Use below commands to use Virtualbox on dcore:

importsce virtualbox-host-modules-3.8.13-tinycore
importsce virtualbox

[Onyarian]

Hi Jason,

I have imported and then loadsce virtualbox-host-modules-3.8.13-tinycore and virtualbox-qt and I have now this new error:

Failed to start the virtual machine WinXP

Failed to load VMMR0.r0
 (VERR_SUPLIB_SYMLINKS_ARE_NOT_PERMITTED).

Result code: NS_ERROR_FAILURE (0x80004005)
Component: Console
Interface: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}

my lsmod:

tc@ubt-dC5x-ordjd:~$ lsmod
Module                  Size  Used by
pci_stub               12288  1
vboxpci                16384  0
vboxnetadp             24576  0
vboxnetflt             20480  0
vboxdrv               188416  3 vboxnetadp,vboxnetflt,vboxpci
dm_crypt               16384  1
ipt_REJECT             12288  1
xt_conntrack           12288  1
xt_LOG                 16384  0
nf_conntrack_ftp       12288  0
iptable_nat            12288  0 ...

I have proved with different virtual machines (winxp and TC) with the same error

Here you can see a screenshot:

[Jason W]

Oh, I see what it is without looking at the screen shot.  I used cp instead of /bb/cp in the startup script to copy the /usr/lib/virtualbox directory to the filesystem.  Fixed, please re-import and test.

[Onyarian]

Hi Jason,

I have reimported the two packages (first I remove it from /import/debs and /sce directories to force the import), and the results are the same as before
 

[netnomad]

hi friends,

i can confirm this behavior

Failed to start the virtual machine WinXP
Failed to load VMMR0.r0 (VERR_SUPLIB_SYMLINKS_ARE_NOT_PERMITTED).

Fehlercode:
NS_ERROR_FAILURE (0x80004005)
Komponente:
Console
Interface:
IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}

[Jason W]

Ok, there was a typo in the startup script.  But now there is also a cdrom related udev rule I need to tend to.  I will aim to fix and test it in the next few days.  Thank you for your patience.

[netnomad]

hi jason,

the last cut is pretty good for me ,
my winxp loads without error-messages, but my kmap gets resetted.

i config my kmap with the help of my ~/.xinitrc with the command "setxkbmap de".

after loading virtualbox i get an us-kmap and i have to load my personal kmap again.

[Onyarian]

With the last post of netnomad I have newly import the two packages and YES, now runs OK.

Perhaps it wasn't updated the repository the last time I re-imported.

Thanks   

(Seems I don't have the problem with the kmap like netnomad, I will prove later again, at this moment I don't have time)

Edit: I can confirm that I don't have any problems with my kmap  (as boot code:  lang=es_ES@euro kmap=es)
         (and in .filetool.lst: usr/share/kmap/es.kmap
                                           usr/share/kmap/qwerty )

[Jason W]

Thank you netnomad and Onyarian for testing and posting results.  I have taken some measures in base dCore to deal with cdrom and other groups that the main user needs to belong to but require a re-login to effect.  I have uploaded an updated dCore-jessie.gz and dCore.gz, see the release posings, please test though it should just work.

[Onyarian]

Hi Jason,

I'm working, and with great satisfaction, with ub-dCore-trusty, is possible to update this and correct the version at boot?

Thanks

[netnomad]

hi jason,

my virtualbox-winxp seems to be pretty stable,
but nevertheless i loose my locale-keymap de.

so i have to exit to prompt, logoff and after the new logon i get my localised kmap de back.

is there still a misconfiguration on my side or is it just the state of the current virtualbox-package?

[Jason W]

netnomad - It is working for Onyarian and I don't use kmaps, so I am not sure what it could be.  I could boot with a locale setting and test, I may do that tonight.

Onyarian - I will update ub-dCore-trusty.  I was going to leave the Ubuntus as is and focus on Debian, but it is not really costing anything to leave them up and update them from time to time.  Also, Trusty has exposed an issue that I thought was fixed in Jessie, perhaps the changes in Jessie simply bought enough time during tc-config to allow UUID and LABEL waitusb as it is not working in Trusty when set up the same as Jessie.  On testing with the systemd udev,  it seems that being able to use the blkid command and list the UUID/LABEL does not mean the device has settled and is ready to mount.  Also, when dmesg says the device is "Available" it also does not mean it can be mounted at that instant. But evidently it means the device is able to be scanned and added to fstab.  I will test the "dry run" option of mount after the rebuildfstab function as a dry run mount should mean that mounting will work at that time.