WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: virtualbox vboxdrv  (Read 7699 times)

Offline netnomad

  • Hero Member
  • *****
  • Posts: 1027
Re: virtualbox vboxdrv
« Reply #15 on: October 02, 2014, 09:21:46 AM »
hi jason,

now i installed console-setup and configured my keymap with "sudo loadkeys de".
with this configuration the kmap of the non-x-environment is configured.

"sudo setxkbmap de" sets the kmap for the xorg-environment.

after loading virtualbox only the kmap of the xorg-environment is resetted
and i can reload it with "sudo setxkbmap de".

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 9667
Re: virtualbox vboxdrv
« Reply #16 on: October 24, 2014, 03:30:52 PM »
Virtualbox in the standard Wheezy repo does not work with the virtualbox-host-modules-3.8.13-tinycore as the modules are made from Virtualbox 4.3.x but Wheezy has Virtualbox 4.1.x.  To fix this, use the wheezy-backports repo to import from and it has Virtualbox 4.3.x which will work with the above kernel modules.
« Last Edit: October 24, 2014, 04:14:24 PM by Jason W »

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 9667
Re: virtualbox vboxdrv
« Reply #17 on: March 05, 2015, 05:29:34 PM »
dCore-jessie does not work with the existing virtualbox-host-modules-3.8.13-tinycore though the Virtualbox version is the same as the one that the modules was built on.  I will ponder a solution for the x86 dCore ports.

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 9667
Re: virtualbox vboxdrv
« Reply #18 on: March 08, 2015, 04:17:21 PM »
Given this, and that Virtualbox was the holdup for adopting the new kernel across the x86 dCore ports. the next release candidates will have the new kernel.

Offline Onyarian

  • Sr. Member
  • ****
  • Posts: 336
Re: virtualbox vboxdrv
« Reply #19 on: March 15, 2015, 08:40:32 AM »
Hi,

what about the virtualbox-host-modules-3.16.6-tinycore?


Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 9667
Re: virtualbox vboxdrv
« Reply #20 on: March 15, 2015, 11:11:01 AM »
I tried building them once and hit a snag.

We will have to name them virtualbox-host-modules-wheezy-3.16.6-tinycore or something like that since the modules seem to be specific to the version of Virtualbox that is running. 
« Last Edit: March 15, 2015, 05:36:11 PM by Jason W »

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 9667
Re: virtualbox vboxdrv
« Reply #21 on: March 15, 2015, 07:47:49 PM »
I have the creation of the Virtualbox modules scripted to create for a needed particular version.

Right now, we have the kernel packges for dCore-jessie, named:

virtualbox-host-modules-jessie-3.16.6-tinycore
virtualbox-guest-additions-modules-jessie-3.16.6-tinycore

I plan to build for the other dCore ports soon.  Testing now with dCore-jessie virtualbox-qt and the Core iso.


Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 9667
Re: virtualbox vboxdrv
« Reply #22 on: March 16, 2015, 06:40:09 AM »
virtualbox-host-modules-jessie-3.16.6-tinycore  also works with ub-dCore-utopic and ub-dCore-trusty.  I will test on the backports virtualbox-qt on wheezy tonight which is also the same version as the other x86 dCores.  Unless anyone else wants to give it a spin today.  I will remove the 'jessie' from the module package names as they are not particular to jessie.

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 9667
Re: virtualbox vboxdrv
« Reply #23 on: March 17, 2015, 08:20:05 AM »
I think it is logical to name the virtualbox modules for their virtualbox version since it is that version the modules are specific for rather than a Debian repo.  So the modules are now named:

virtualbox-4.3.18-host-modules-3.16.6-tinycore
virtualbox-4.3.18-guest-additions-modules-3.16.6-tinycore

I did try to build modules for dCore-wheezy, but the 4.1.18 package has an issue building with the new kernel, same error here as on the bug report below and the solution in it's follow up.  Use the 4.3.18 virtualbox from wheezy-backports instead.

https://lists.debian.org/debian-backports/2014/03/msg00065.html

Virtualbox-qt is available in the contrib section of wheezy-backports.  Use the below entry in an /opt/debextra file to import it:

http://http.debian.net/debian wheezy-backports contrib

I have tested Virtualbox with each dCore x86 port and all is working as expected.  When a port has an updated Virtualbox package, I will then provide a set of kernel modules for it.
« Last Edit: March 17, 2015, 08:44:19 AM by Jason W »

Offline Onyarian

  • Sr. Member
  • ****
  • Posts: 336
Re: virtualbox vboxdrv
« Reply #24 on: March 17, 2015, 11:35:36 AM »
great, Jason!

works perfect!


Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 9667
Re: virtualbox vboxdrv
« Reply #25 on: March 17, 2015, 12:25:05 PM »
Good news, thanks for testing!

One tip I have found helpful:  If you have virtualbox-qt loaded before you load the kernel module package (virtualbox-4.3.18-host-modules-3.16.6-tinycore), then you will need to modprobe the kernel module manually.

modprobe vboxdrv

I am sure the guest additions will show the same behavior though I have not used guest additions.

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 9667
Re: virtualbox vboxdrv
« Reply #26 on: July 04, 2015, 02:48:44 PM »
I have built virtualbox host and guest modules for dCore-vivid.  Named virtualbox-4.3.26-host-modules-3.16.6-tinycore  and   virtualbox-4.3.26-guest-modules-3.16.6-tinycore.  Tested the host ones in dCore-vivid and all seems well, I don't use the guest additions so could not test.

dCore-utopic and dCore-jessie share the same Virtualbox build of 4.3.18 so those modules tested and works with both - module package names are virtualbox-4.3.18-host-modules-3.16..6-tinycore  and   virtualbox-4.3.18-guest-modules-3.16.6-tinycore.  dCore-wheezy and dCore-trusty have an old enough Virtualbox that does not play well with the newer 3.16.6 kernel so use a newer dCore if you want to use Virtualbox.

« Last Edit: July 04, 2015, 04:06:23 PM by Jason W »