Results 1 to 11 of 11

Thread: Another VirtualBox problem

  1. #1
    Join Date
    2013-Mar
    Posts
    4

    Unhappy Another VirtualBox problem

    Hello guys

    First of all, congrats about the new beloved Kali

    Well, i installed the new version of VirualBox into my Kali machine, but when i start it from terminal, it gives me the following warning message:

    Code:
    WARNING: The character device /dev/vboxdrv does not exist.
    	 Please install the virtualbox-ose-dkms package and the appropriate
    	 headers, most likely linux-headers-686.
    
    	 You will not be able to start VMs until this problem is fixed.
    I tried to install virtualbox-ose-dkms but it tells me it's the newest version, i also tried to install linux-headers-686 but same as the one before it's the newest version...

    and i don't know how to install the driver vboxdvr, So now what ?

  2. #2
    Join Date
    2013-Mar
    Posts
    6
    Try installing "dkms". I had a similar problem w/virtual box, installing "dkms" and rebooting fixed it. :]

  3. #3
    Join Date
    2013-Mar
    Posts
    4
    Code:
    root@kali: virtualbox 
    WARNING: The character device /dev/vboxdrv does not exist.
    	 Please install the virtualbox-ose-dkms package and the appropriate
    	 headers, most likely linux-headers-686.
    
    	 You will not be able to start VMs until this problem is fixed.
    root@kali:~# apt-get install linux-headers-686
    Reading package lists... Done
    Building dependency tree       
    Reading state information... Done
    Package linux-headers-686 is not available, but is referred to by another package.
    This may mean that the package is missing, has been obsoleted, or
    is only available from another source
    
    E: Package 'linux-headers-686' has no installation candidate
    
    root@kali:~# apt-get install linux-headers-`uname -r`
    Reading package lists... Done
    Building dependency tree       
    Reading state information... Done
    linux-headers-686-pae is already the newest version.
    linux-headers-686-pae set to manually installed.
    0 upgraded, 0 newly installed, 0 to remove and 239 not upgraded.
    root@kali:~# apt-get install dkms
    Reading package lists... Done
    Building dependency tree       
    Reading state information... Done
    dkms is already the newest version.
    0 upgraded, 0 newly installed, 0 to remove and 239 not upgraded.
    Didn't make it even though when i rebooted i tried to reinstall the virtualbox-ose-dkms it reinstalled them again successfully witch is weard :\

  4. #4
    Join Date
    2013-Apr
    Posts
    1
    I have the same issue. I can run virtualbox from the menu and create a VM but then when I try to run I get an error message and it fails. Installing 'dkms' didn't help as it just said I already have it.

  5. #5
    Join Date
    2013-Mar
    Posts
    354
    Intall the virtualbox as is:

    aptitude install virtualbox

    It will also install the dkms (Dynamic Kernel Mode Support). This will avoid reinstalling VM if there is an upgrade in kernel.

    Luck.

  6. #6
    Join Date
    2013-Apr
    Posts
    2
    # apt-get purge --remove virtualbox
    Then downloaded the debian wheezy virtualbox.deb https://www.virtualbox.org/wiki/Linux_Downloads
    # dpkg -i virtualbox*.deb
    So far so good... no errors reporting

  7. #7
    Join Date
    2013-May
    Posts
    2
    I downloaded the debian wheezy version of Virtual box. And went ahead as suggested and ran "dpkg -i virtualbox*.deb"

    Heres what I got:

    (Reading database ... 265154 files and directories currently installed.)
    Preparing to replace virtualbox-4.2 4.2.12-84980~Debian~wheezy (using VIRTUALBOX.deb) ...
    [ ok ] Stopping VirtualBox kernel modules:.
    Unpacking replacement virtualbox-4.2 ...
    Setting up virtualbox-4.2 (4.2.12-84980~Debian~wheezy) ...
    addgroup: The group `vboxusers' already exists as a system group. Exiting.
    [ ok ] Stopping VirtualBox kernel modules:.
    [....] Recompiling VirtualBox kernel modules:
    [FAIL] Look at /var/log/vbox-install.log to find out what went wrong ... failed!
    Processing triggers for shared-mime-info ...
    Processing triggers for desktop-file-utils ...
    Processing triggers for gnome-menus ...
    Processing triggers for hicolor-icon-theme ...
    Processing triggers for python-central ...

  8. #8
    Join Date
    2013-Apr
    Posts
    2
    Quote Originally Posted by abdulwali View Post
    I downloaded the debian wheezy version of Virtual box. And went ahead as suggested and ran "dpkg -i virtualbox*.deb"

    Heres what I got:

    (Reading database ... 265154 files and directories currently installed.)
    Preparing to replace virtualbox-4.2 4.2.12-84980~Debian~wheezy (using VIRTUALBOX.deb) ...
    [ ok ] Stopping VirtualBox kernel modules:.
    Unpacking replacement virtualbox-4.2 ...
    Setting up virtualbox-4.2 (4.2.12-84980~Debian~wheezy) ...
    addgroup: The group `vboxusers' already exists as a system group. Exiting.
    [ ok ] Stopping VirtualBox kernel modules:.
    [....] Recompiling VirtualBox kernel modules:
    [FAIL] Look at /var/log/vbox-install.log to find out what went wrong ... failed!
    Processing triggers for shared-mime-info ...
    Processing triggers for desktop-file-utils ...
    Processing triggers for gnome-menus ...
    Processing triggers for hicolor-icon-theme ...
    Processing triggers for python-central ...
    Did you run...
    # apt-get purge --remove virtualbox
    Then do the install with dpkg but be sure you got i386 or 64AMD, whichever you are running...
    # uname -r
    Here is the full package name of the file that I downloaded for i386 Debian wheezy (Kali 7.0)...
    # dpkg -i virtualbox-4.2_4.2.12-84980~Debian~wheezy_i386.deb
    If you get the same error with the groupname then try...
    # delgroup vboxusers
    And go through the process again
    LUCK

  9. #9
    Join Date
    2013-May
    Posts
    2
    not much luck.. quite difficult actually. any suggestions? If not a fix for this issue in virtual box, some other virtual machine client?

  10. #10
    Join Date
    2013-Jul
    Posts
    1
    Try FAUmachine, it's not as snazzy as the virtualbox machine manager, but it works. I am having the same (or similar) issue with the i386 pae headers, and haven't found much in the way of repairing virtualbox (my preferred vmm) yet. There are a few other virtual machine managers out there, but as of right now I don't see a fix for this problem available. Hopefully there will be a fix soon, and we can all go about using our preferred vmm's.

  11. #11
    Join Date
    2013-Jun
    Location
    Malang, Indonesia
    Posts
    9
    Working like a charm for me.... Thanks...
    [B]auastyle blog[/B] <~ http://www.ulil-albab.info
    [B]@auastyle[/B] <~ on [B]twitter[/B]

Similar Threads

  1. virtualbox problem with headers
    By Subzero in forum TroubleShooting Archive
    Replies: 0
    Last Post: 2017-02-20, 08:56
  2. Another VirtualBox problem
    By Ash78 in forum TroubleShooting Archive
    Replies: 0
    Last Post: 2013-03-20, 19:59

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •