Problem with the installation of VirtualBox





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







40















I am trying to install virtualbox and make it work but it doesn't seem like I can. In the image
you can see the output.



Command line output



If I run VBoxManage --version I get:



WARNING: The character device /dev/vboxdrv does not exist.
Please install the virtualbox-dkms package and the appropriate
headers, most likely linux-headers-generic.

You will not be able to start VMs until this problem is fixed.
4.3.10_Ubuntur93012


But virtualbox-dkms is already installed and at the latest version. So I tried to reinstall it and i got this:



cli output 2



Any help will be appreciated.



EDIT:



The output after reconfigure (@M.Tarun suggestion):



cli output 3



EDIT 2:



Also installed the sources as @Hmayag instructed, purged virtualbox and installed it again but I got the same problem.










share|improve this question




















  • 1





    Kalispera Antoni. The installer is trying to build the kernel module but fails to locate the kernel source files. The clue is Module build for the currently running kernel was skipped since the kernel sources for this kernel does not seem to be installed. Check that you have those installed. Make sure they match the running kernel version. I think apt-get source linux-image-$(uname -r) should do it.

    – hmayag
    May 13 '14 at 20:25











  • Kalispera:). Unfortunately nothing happened. Please see my second edit.

    – Antonis Gr
    May 13 '14 at 20:37











  • Also installed dpkg-dev and ran the command again but no luck.

    – Antonis Gr
    May 13 '14 at 20:48






  • 2





    You probably have a mismatch between the running kernel and the installed header. Can you add the output of uname -a and dpkg -l | grep linux-headers?

    – Rmano
    May 13 '14 at 21:57






  • 1





    Upgrade to latest kernel. You seem to be running 3.11.

    – bain
    May 14 '14 at 0:11


















40















I am trying to install virtualbox and make it work but it doesn't seem like I can. In the image
you can see the output.



Command line output



If I run VBoxManage --version I get:



WARNING: The character device /dev/vboxdrv does not exist.
Please install the virtualbox-dkms package and the appropriate
headers, most likely linux-headers-generic.

You will not be able to start VMs until this problem is fixed.
4.3.10_Ubuntur93012


But virtualbox-dkms is already installed and at the latest version. So I tried to reinstall it and i got this:



cli output 2



Any help will be appreciated.



EDIT:



The output after reconfigure (@M.Tarun suggestion):



cli output 3



EDIT 2:



Also installed the sources as @Hmayag instructed, purged virtualbox and installed it again but I got the same problem.










share|improve this question




















  • 1





    Kalispera Antoni. The installer is trying to build the kernel module but fails to locate the kernel source files. The clue is Module build for the currently running kernel was skipped since the kernel sources for this kernel does not seem to be installed. Check that you have those installed. Make sure they match the running kernel version. I think apt-get source linux-image-$(uname -r) should do it.

    – hmayag
    May 13 '14 at 20:25











  • Kalispera:). Unfortunately nothing happened. Please see my second edit.

    – Antonis Gr
    May 13 '14 at 20:37











  • Also installed dpkg-dev and ran the command again but no luck.

    – Antonis Gr
    May 13 '14 at 20:48






  • 2





    You probably have a mismatch between the running kernel and the installed header. Can you add the output of uname -a and dpkg -l | grep linux-headers?

    – Rmano
    May 13 '14 at 21:57






  • 1





    Upgrade to latest kernel. You seem to be running 3.11.

    – bain
    May 14 '14 at 0:11














40












40








40


18






I am trying to install virtualbox and make it work but it doesn't seem like I can. In the image
you can see the output.



Command line output



If I run VBoxManage --version I get:



WARNING: The character device /dev/vboxdrv does not exist.
Please install the virtualbox-dkms package and the appropriate
headers, most likely linux-headers-generic.

You will not be able to start VMs until this problem is fixed.
4.3.10_Ubuntur93012


But virtualbox-dkms is already installed and at the latest version. So I tried to reinstall it and i got this:



cli output 2



Any help will be appreciated.



EDIT:



The output after reconfigure (@M.Tarun suggestion):



cli output 3



EDIT 2:



Also installed the sources as @Hmayag instructed, purged virtualbox and installed it again but I got the same problem.










share|improve this question
















I am trying to install virtualbox and make it work but it doesn't seem like I can. In the image
you can see the output.



Command line output



If I run VBoxManage --version I get:



WARNING: The character device /dev/vboxdrv does not exist.
Please install the virtualbox-dkms package and the appropriate
headers, most likely linux-headers-generic.

You will not be able to start VMs until this problem is fixed.
4.3.10_Ubuntur93012


But virtualbox-dkms is already installed and at the latest version. So I tried to reinstall it and i got this:



cli output 2



Any help will be appreciated.



EDIT:



The output after reconfigure (@M.Tarun suggestion):



cli output 3



EDIT 2:



Also installed the sources as @Hmayag instructed, purged virtualbox and installed it again but I got the same problem.







14.04 virtualbox






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 23 '14 at 14:45







Antonis Gr

















asked May 13 '14 at 19:52









Antonis GrAntonis Gr

333149




333149








  • 1





    Kalispera Antoni. The installer is trying to build the kernel module but fails to locate the kernel source files. The clue is Module build for the currently running kernel was skipped since the kernel sources for this kernel does not seem to be installed. Check that you have those installed. Make sure they match the running kernel version. I think apt-get source linux-image-$(uname -r) should do it.

    – hmayag
    May 13 '14 at 20:25











  • Kalispera:). Unfortunately nothing happened. Please see my second edit.

    – Antonis Gr
    May 13 '14 at 20:37











  • Also installed dpkg-dev and ran the command again but no luck.

    – Antonis Gr
    May 13 '14 at 20:48






  • 2





    You probably have a mismatch between the running kernel and the installed header. Can you add the output of uname -a and dpkg -l | grep linux-headers?

    – Rmano
    May 13 '14 at 21:57






  • 1





    Upgrade to latest kernel. You seem to be running 3.11.

    – bain
    May 14 '14 at 0:11














  • 1





    Kalispera Antoni. The installer is trying to build the kernel module but fails to locate the kernel source files. The clue is Module build for the currently running kernel was skipped since the kernel sources for this kernel does not seem to be installed. Check that you have those installed. Make sure they match the running kernel version. I think apt-get source linux-image-$(uname -r) should do it.

    – hmayag
    May 13 '14 at 20:25











  • Kalispera:). Unfortunately nothing happened. Please see my second edit.

    – Antonis Gr
    May 13 '14 at 20:37











  • Also installed dpkg-dev and ran the command again but no luck.

    – Antonis Gr
    May 13 '14 at 20:48






  • 2





    You probably have a mismatch between the running kernel and the installed header. Can you add the output of uname -a and dpkg -l | grep linux-headers?

    – Rmano
    May 13 '14 at 21:57






  • 1





    Upgrade to latest kernel. You seem to be running 3.11.

    – bain
    May 14 '14 at 0:11








1




1





Kalispera Antoni. The installer is trying to build the kernel module but fails to locate the kernel source files. The clue is Module build for the currently running kernel was skipped since the kernel sources for this kernel does not seem to be installed. Check that you have those installed. Make sure they match the running kernel version. I think apt-get source linux-image-$(uname -r) should do it.

– hmayag
May 13 '14 at 20:25





Kalispera Antoni. The installer is trying to build the kernel module but fails to locate the kernel source files. The clue is Module build for the currently running kernel was skipped since the kernel sources for this kernel does not seem to be installed. Check that you have those installed. Make sure they match the running kernel version. I think apt-get source linux-image-$(uname -r) should do it.

– hmayag
May 13 '14 at 20:25













Kalispera:). Unfortunately nothing happened. Please see my second edit.

– Antonis Gr
May 13 '14 at 20:37





Kalispera:). Unfortunately nothing happened. Please see my second edit.

– Antonis Gr
May 13 '14 at 20:37













Also installed dpkg-dev and ran the command again but no luck.

– Antonis Gr
May 13 '14 at 20:48





Also installed dpkg-dev and ran the command again but no luck.

– Antonis Gr
May 13 '14 at 20:48




2




2





You probably have a mismatch between the running kernel and the installed header. Can you add the output of uname -a and dpkg -l | grep linux-headers?

– Rmano
May 13 '14 at 21:57





You probably have a mismatch between the running kernel and the installed header. Can you add the output of uname -a and dpkg -l | grep linux-headers?

– Rmano
May 13 '14 at 21:57




1




1





Upgrade to latest kernel. You seem to be running 3.11.

– bain
May 14 '14 at 0:11





Upgrade to latest kernel. You seem to be running 3.11.

– bain
May 14 '14 at 0:11










10 Answers
10






active

oldest

votes


















58














Basically after you install those two packages you also need to do the reconfiguration:



sudo dpkg-reconfigure virtualbox-dkms
sudo dpkg-reconfigure virtualbox
sudo modprobe vboxdrv


And to fix eth0:



sudo modprobe vboxnetflt





share|improve this answer


























  • please see the edit

    – Antonis Gr
    May 13 '14 at 20:21











  • works fine, thanks! Vagrant 1.7.2; VirtualBox 4.3.10; Ubuntu 14.04

    – Makc
    Jun 2 '15 at 13:07













  • How above commands will deploy for centOS

    – HMS
    Sep 8 '15 at 7:19






  • 1





    If you still have problems make sure that UEFI secure boot is disabled.

    – totymedli
    Mar 1 '17 at 19:29













  • I had issues with virtualbox-dkms support after the kernel upgrade and ended up with installation of the latest version of VirtualBox from the official website site.

    – luart
    Oct 25 '17 at 13:29



















14














I solved this problem by following commands:



sudo apt-get install linux-headers-generic
sudo dpkg-reconfigure virtualbox-dkms





share|improve this answer


























  • Thanks this helped me on ubuntu 14.04 after a dist upgrade somehow linux headers changed

    – sandino
    Aug 24 '15 at 15:31






  • 3





    This helped me. I was able to fix with: sudo apt-get install linux-headers-`uname -r` and then sudo dpkg-reconfigure virtualbox-dkms. Thanks!

    – stitakis
    Jan 12 '17 at 20:48













  • @stitakis your comment should be an answer so I could upvote i properly

    – rioted
    Aug 21 '17 at 14:40





















3














The reason for the problem is that you have booted the 3.11 kernel while the dpkg-reconfigure expects a 3.13 kernel. That's why you get the message 'no suitable module for the running kernel'.



Be sure to update your bootloader.



In my case the bootloader is updated from another OS (Debian) and booting to that and running sudo update-grub solved the problem.






share|improve this answer

































    2














    I used the vendor’s official guide for Debian-based Linux distributions:



    printf 'deb http://download.virtualbox.org/virtualbox/debian %s contribn' "$(lsb_release -cs)" | sudo tee /etc/apt/sources.list.d/virtualbox.list

    wget -qO- https://www.virtualbox.org/download/oracle_vbox{,_2016}.asc | sudo apt-key add -

    sudo apt-get purge virtualbox
    sudo apt-get update
    sudo apt-get install virtualbox-5.0 dkms





    share|improve this answer


























    • worked for me as well!

      – ʀᴇᴅ_ᴅᴇᴠɪʟ226
      Jan 18 '16 at 9:48



















    1














    I wasn't able to fix the problem with any other solution suggested, so I made a fresh 14.04 installation and everything is fine now.






    share|improve this answer































      1














      In my case, the issue was having virtualbox-4.1 installed alongside virtualbox-4.2. Once I uninstalled 4.1, I could run sudo /etc/init.d/vboxdrv setup and sudo modprobe vboxdrv just fine, as well as start VMs.






      share|improve this answer































        1














        You have to check the version of gcc your are using. I was facing the same problem of virtualbox kernel compilation.
        I fixed the issue using this post https://www.virtualbox.org/ticket/12467



        You probably are using a outdated version of gcc that is different of the gcc used by the Linux kernel.



        Check the default version your are using :



        gcc -v


        Mine is gcc version 4.4.7 (Ubuntu/Linaro 4.4.7-8ubuntu1)



        And the gcc version your kernel was compiled with



        dmesg | more
        [ 0.000000] Linux version 3.13.0-83-generic (buildd@lgw01-55) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #127-Ubuntu SMP Fri Mar 11 00:25:37 UTC 2016 (Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35)


        or with



        dpkg -l gcc


        If the gcc versions are different like on my system, switch your default gcc compiler



        sudo update-alternatives --config gcc


        then virtualbox-dkms installation should works fine



        sudo apt-get --reinstall install virtualbox-dkms





        share|improve this answer































          0














          The clue is here: Please install the virtualbox-dkms package and the appropriate
          headers, most likely linux-headers-generic.



          Since you have the first, it must still want the second.



          sudo apt-get install linux-headers-generic



          Then make sure everything is up to date.



          sudo apt-get update



          sudo apt-get upgrade






          share|improve this answer





















          • 2





            Sorry just forgot to write that I have them too. linux-headers-generic is already the newest version. is the output when i try to install them.

            – Antonis Gr
            May 13 '14 at 20:11






          • 2





            Thank you, I added that information to your question to insure that you get accurate answers

            – Elder Geek
            May 13 '14 at 20:15



















          0














          I had the same issue. I found that the source of the problem is most probably that I'm using a custom kernel.



          Downloading the latest .deb package from virtualbox.org, and installing it by dpkg -i has solved the problem in my case.






          share|improve this answer































            -1














            Try



            sudo /etc/init.d/vboxdrv setup





            share|improve this answer






















              protected by Community Oct 23 '17 at 9:19



              Thank you for your interest in this question.
              Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



              Would you like to answer one of these unanswered questions instead?














              10 Answers
              10






              active

              oldest

              votes








              10 Answers
              10






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes









              58














              Basically after you install those two packages you also need to do the reconfiguration:



              sudo dpkg-reconfigure virtualbox-dkms
              sudo dpkg-reconfigure virtualbox
              sudo modprobe vboxdrv


              And to fix eth0:



              sudo modprobe vboxnetflt





              share|improve this answer


























              • please see the edit

                – Antonis Gr
                May 13 '14 at 20:21











              • works fine, thanks! Vagrant 1.7.2; VirtualBox 4.3.10; Ubuntu 14.04

                – Makc
                Jun 2 '15 at 13:07













              • How above commands will deploy for centOS

                – HMS
                Sep 8 '15 at 7:19






              • 1





                If you still have problems make sure that UEFI secure boot is disabled.

                – totymedli
                Mar 1 '17 at 19:29













              • I had issues with virtualbox-dkms support after the kernel upgrade and ended up with installation of the latest version of VirtualBox from the official website site.

                – luart
                Oct 25 '17 at 13:29
















              58














              Basically after you install those two packages you also need to do the reconfiguration:



              sudo dpkg-reconfigure virtualbox-dkms
              sudo dpkg-reconfigure virtualbox
              sudo modprobe vboxdrv


              And to fix eth0:



              sudo modprobe vboxnetflt





              share|improve this answer


























              • please see the edit

                – Antonis Gr
                May 13 '14 at 20:21











              • works fine, thanks! Vagrant 1.7.2; VirtualBox 4.3.10; Ubuntu 14.04

                – Makc
                Jun 2 '15 at 13:07













              • How above commands will deploy for centOS

                – HMS
                Sep 8 '15 at 7:19






              • 1





                If you still have problems make sure that UEFI secure boot is disabled.

                – totymedli
                Mar 1 '17 at 19:29













              • I had issues with virtualbox-dkms support after the kernel upgrade and ended up with installation of the latest version of VirtualBox from the official website site.

                – luart
                Oct 25 '17 at 13:29














              58












              58








              58







              Basically after you install those two packages you also need to do the reconfiguration:



              sudo dpkg-reconfigure virtualbox-dkms
              sudo dpkg-reconfigure virtualbox
              sudo modprobe vboxdrv


              And to fix eth0:



              sudo modprobe vboxnetflt





              share|improve this answer















              Basically after you install those two packages you also need to do the reconfiguration:



              sudo dpkg-reconfigure virtualbox-dkms
              sudo dpkg-reconfigure virtualbox
              sudo modprobe vboxdrv


              And to fix eth0:



              sudo modprobe vboxnetflt






              share|improve this answer














              share|improve this answer



              share|improve this answer








              edited May 13 '14 at 22:48









              Eric Carvalho

              42.6k17118148




              42.6k17118148










              answered May 13 '14 at 19:58









              M.TarunM.Tarun

              3,49162562




              3,49162562













              • please see the edit

                – Antonis Gr
                May 13 '14 at 20:21











              • works fine, thanks! Vagrant 1.7.2; VirtualBox 4.3.10; Ubuntu 14.04

                – Makc
                Jun 2 '15 at 13:07













              • How above commands will deploy for centOS

                – HMS
                Sep 8 '15 at 7:19






              • 1





                If you still have problems make sure that UEFI secure boot is disabled.

                – totymedli
                Mar 1 '17 at 19:29













              • I had issues with virtualbox-dkms support after the kernel upgrade and ended up with installation of the latest version of VirtualBox from the official website site.

                – luart
                Oct 25 '17 at 13:29



















              • please see the edit

                – Antonis Gr
                May 13 '14 at 20:21











              • works fine, thanks! Vagrant 1.7.2; VirtualBox 4.3.10; Ubuntu 14.04

                – Makc
                Jun 2 '15 at 13:07













              • How above commands will deploy for centOS

                – HMS
                Sep 8 '15 at 7:19






              • 1





                If you still have problems make sure that UEFI secure boot is disabled.

                – totymedli
                Mar 1 '17 at 19:29













              • I had issues with virtualbox-dkms support after the kernel upgrade and ended up with installation of the latest version of VirtualBox from the official website site.

                – luart
                Oct 25 '17 at 13:29

















              please see the edit

              – Antonis Gr
              May 13 '14 at 20:21





              please see the edit

              – Antonis Gr
              May 13 '14 at 20:21













              works fine, thanks! Vagrant 1.7.2; VirtualBox 4.3.10; Ubuntu 14.04

              – Makc
              Jun 2 '15 at 13:07







              works fine, thanks! Vagrant 1.7.2; VirtualBox 4.3.10; Ubuntu 14.04

              – Makc
              Jun 2 '15 at 13:07















              How above commands will deploy for centOS

              – HMS
              Sep 8 '15 at 7:19





              How above commands will deploy for centOS

              – HMS
              Sep 8 '15 at 7:19




              1




              1





              If you still have problems make sure that UEFI secure boot is disabled.

              – totymedli
              Mar 1 '17 at 19:29







              If you still have problems make sure that UEFI secure boot is disabled.

              – totymedli
              Mar 1 '17 at 19:29















              I had issues with virtualbox-dkms support after the kernel upgrade and ended up with installation of the latest version of VirtualBox from the official website site.

              – luart
              Oct 25 '17 at 13:29





              I had issues with virtualbox-dkms support after the kernel upgrade and ended up with installation of the latest version of VirtualBox from the official website site.

              – luart
              Oct 25 '17 at 13:29













              14














              I solved this problem by following commands:



              sudo apt-get install linux-headers-generic
              sudo dpkg-reconfigure virtualbox-dkms





              share|improve this answer


























              • Thanks this helped me on ubuntu 14.04 after a dist upgrade somehow linux headers changed

                – sandino
                Aug 24 '15 at 15:31






              • 3





                This helped me. I was able to fix with: sudo apt-get install linux-headers-`uname -r` and then sudo dpkg-reconfigure virtualbox-dkms. Thanks!

                – stitakis
                Jan 12 '17 at 20:48













              • @stitakis your comment should be an answer so I could upvote i properly

                – rioted
                Aug 21 '17 at 14:40


















              14














              I solved this problem by following commands:



              sudo apt-get install linux-headers-generic
              sudo dpkg-reconfigure virtualbox-dkms





              share|improve this answer


























              • Thanks this helped me on ubuntu 14.04 after a dist upgrade somehow linux headers changed

                – sandino
                Aug 24 '15 at 15:31






              • 3





                This helped me. I was able to fix with: sudo apt-get install linux-headers-`uname -r` and then sudo dpkg-reconfigure virtualbox-dkms. Thanks!

                – stitakis
                Jan 12 '17 at 20:48













              • @stitakis your comment should be an answer so I could upvote i properly

                – rioted
                Aug 21 '17 at 14:40
















              14












              14








              14







              I solved this problem by following commands:



              sudo apt-get install linux-headers-generic
              sudo dpkg-reconfigure virtualbox-dkms





              share|improve this answer















              I solved this problem by following commands:



              sudo apt-get install linux-headers-generic
              sudo dpkg-reconfigure virtualbox-dkms






              share|improve this answer














              share|improve this answer



              share|improve this answer








              edited Aug 20 '14 at 5:52









              amc

              4,85462746




              4,85462746










              answered Aug 20 '14 at 3:40









              user318571user318571

              14112




              14112













              • Thanks this helped me on ubuntu 14.04 after a dist upgrade somehow linux headers changed

                – sandino
                Aug 24 '15 at 15:31






              • 3





                This helped me. I was able to fix with: sudo apt-get install linux-headers-`uname -r` and then sudo dpkg-reconfigure virtualbox-dkms. Thanks!

                – stitakis
                Jan 12 '17 at 20:48













              • @stitakis your comment should be an answer so I could upvote i properly

                – rioted
                Aug 21 '17 at 14:40





















              • Thanks this helped me on ubuntu 14.04 after a dist upgrade somehow linux headers changed

                – sandino
                Aug 24 '15 at 15:31






              • 3





                This helped me. I was able to fix with: sudo apt-get install linux-headers-`uname -r` and then sudo dpkg-reconfigure virtualbox-dkms. Thanks!

                – stitakis
                Jan 12 '17 at 20:48













              • @stitakis your comment should be an answer so I could upvote i properly

                – rioted
                Aug 21 '17 at 14:40



















              Thanks this helped me on ubuntu 14.04 after a dist upgrade somehow linux headers changed

              – sandino
              Aug 24 '15 at 15:31





              Thanks this helped me on ubuntu 14.04 after a dist upgrade somehow linux headers changed

              – sandino
              Aug 24 '15 at 15:31




              3




              3





              This helped me. I was able to fix with: sudo apt-get install linux-headers-`uname -r` and then sudo dpkg-reconfigure virtualbox-dkms. Thanks!

              – stitakis
              Jan 12 '17 at 20:48







              This helped me. I was able to fix with: sudo apt-get install linux-headers-`uname -r` and then sudo dpkg-reconfigure virtualbox-dkms. Thanks!

              – stitakis
              Jan 12 '17 at 20:48















              @stitakis your comment should be an answer so I could upvote i properly

              – rioted
              Aug 21 '17 at 14:40







              @stitakis your comment should be an answer so I could upvote i properly

              – rioted
              Aug 21 '17 at 14:40













              3














              The reason for the problem is that you have booted the 3.11 kernel while the dpkg-reconfigure expects a 3.13 kernel. That's why you get the message 'no suitable module for the running kernel'.



              Be sure to update your bootloader.



              In my case the bootloader is updated from another OS (Debian) and booting to that and running sudo update-grub solved the problem.






              share|improve this answer






























                3














                The reason for the problem is that you have booted the 3.11 kernel while the dpkg-reconfigure expects a 3.13 kernel. That's why you get the message 'no suitable module for the running kernel'.



                Be sure to update your bootloader.



                In my case the bootloader is updated from another OS (Debian) and booting to that and running sudo update-grub solved the problem.






                share|improve this answer




























                  3












                  3








                  3







                  The reason for the problem is that you have booted the 3.11 kernel while the dpkg-reconfigure expects a 3.13 kernel. That's why you get the message 'no suitable module for the running kernel'.



                  Be sure to update your bootloader.



                  In my case the bootloader is updated from another OS (Debian) and booting to that and running sudo update-grub solved the problem.






                  share|improve this answer















                  The reason for the problem is that you have booted the 3.11 kernel while the dpkg-reconfigure expects a 3.13 kernel. That's why you get the message 'no suitable module for the running kernel'.



                  Be sure to update your bootloader.



                  In my case the bootloader is updated from another OS (Debian) and booting to that and running sudo update-grub solved the problem.







                  share|improve this answer














                  share|improve this answer



                  share|improve this answer








                  edited Mar 12 '17 at 19:59









                  Zanna

                  51.5k13141244




                  51.5k13141244










                  answered Jul 15 '14 at 20:08









                  PitPit

                  311




                  311























                      2














                      I used the vendor’s official guide for Debian-based Linux distributions:



                      printf 'deb http://download.virtualbox.org/virtualbox/debian %s contribn' "$(lsb_release -cs)" | sudo tee /etc/apt/sources.list.d/virtualbox.list

                      wget -qO- https://www.virtualbox.org/download/oracle_vbox{,_2016}.asc | sudo apt-key add -

                      sudo apt-get purge virtualbox
                      sudo apt-get update
                      sudo apt-get install virtualbox-5.0 dkms





                      share|improve this answer


























                      • worked for me as well!

                        – ʀᴇᴅ_ᴅᴇᴠɪʟ226
                        Jan 18 '16 at 9:48
















                      2














                      I used the vendor’s official guide for Debian-based Linux distributions:



                      printf 'deb http://download.virtualbox.org/virtualbox/debian %s contribn' "$(lsb_release -cs)" | sudo tee /etc/apt/sources.list.d/virtualbox.list

                      wget -qO- https://www.virtualbox.org/download/oracle_vbox{,_2016}.asc | sudo apt-key add -

                      sudo apt-get purge virtualbox
                      sudo apt-get update
                      sudo apt-get install virtualbox-5.0 dkms





                      share|improve this answer


























                      • worked for me as well!

                        – ʀᴇᴅ_ᴅᴇᴠɪʟ226
                        Jan 18 '16 at 9:48














                      2












                      2








                      2







                      I used the vendor’s official guide for Debian-based Linux distributions:



                      printf 'deb http://download.virtualbox.org/virtualbox/debian %s contribn' "$(lsb_release -cs)" | sudo tee /etc/apt/sources.list.d/virtualbox.list

                      wget -qO- https://www.virtualbox.org/download/oracle_vbox{,_2016}.asc | sudo apt-key add -

                      sudo apt-get purge virtualbox
                      sudo apt-get update
                      sudo apt-get install virtualbox-5.0 dkms





                      share|improve this answer















                      I used the vendor’s official guide for Debian-based Linux distributions:



                      printf 'deb http://download.virtualbox.org/virtualbox/debian %s contribn' "$(lsb_release -cs)" | sudo tee /etc/apt/sources.list.d/virtualbox.list

                      wget -qO- https://www.virtualbox.org/download/oracle_vbox{,_2016}.asc | sudo apt-key add -

                      sudo apt-get purge virtualbox
                      sudo apt-get update
                      sudo apt-get install virtualbox-5.0 dkms






                      share|improve this answer














                      share|improve this answer



                      share|improve this answer








                      edited Feb 15 at 0:47









                      David Foerster

                      28.7k1367113




                      28.7k1367113










                      answered Nov 20 '15 at 12:46









                      Adnrii VeklychevAdnrii Veklychev

                      211




                      211













                      • worked for me as well!

                        – ʀᴇᴅ_ᴅᴇᴠɪʟ226
                        Jan 18 '16 at 9:48



















                      • worked for me as well!

                        – ʀᴇᴅ_ᴅᴇᴠɪʟ226
                        Jan 18 '16 at 9:48

















                      worked for me as well!

                      – ʀᴇᴅ_ᴅᴇᴠɪʟ226
                      Jan 18 '16 at 9:48





                      worked for me as well!

                      – ʀᴇᴅ_ᴅᴇᴠɪʟ226
                      Jan 18 '16 at 9:48











                      1














                      I wasn't able to fix the problem with any other solution suggested, so I made a fresh 14.04 installation and everything is fine now.






                      share|improve this answer




























                        1














                        I wasn't able to fix the problem with any other solution suggested, so I made a fresh 14.04 installation and everything is fine now.






                        share|improve this answer


























                          1












                          1








                          1







                          I wasn't able to fix the problem with any other solution suggested, so I made a fresh 14.04 installation and everything is fine now.






                          share|improve this answer













                          I wasn't able to fix the problem with any other solution suggested, so I made a fresh 14.04 installation and everything is fine now.







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered May 21 '14 at 12:02









                          Antonis GrAntonis Gr

                          333149




                          333149























                              1














                              In my case, the issue was having virtualbox-4.1 installed alongside virtualbox-4.2. Once I uninstalled 4.1, I could run sudo /etc/init.d/vboxdrv setup and sudo modprobe vboxdrv just fine, as well as start VMs.






                              share|improve this answer




























                                1














                                In my case, the issue was having virtualbox-4.1 installed alongside virtualbox-4.2. Once I uninstalled 4.1, I could run sudo /etc/init.d/vboxdrv setup and sudo modprobe vboxdrv just fine, as well as start VMs.






                                share|improve this answer


























                                  1












                                  1








                                  1







                                  In my case, the issue was having virtualbox-4.1 installed alongside virtualbox-4.2. Once I uninstalled 4.1, I could run sudo /etc/init.d/vboxdrv setup and sudo modprobe vboxdrv just fine, as well as start VMs.






                                  share|improve this answer













                                  In my case, the issue was having virtualbox-4.1 installed alongside virtualbox-4.2. Once I uninstalled 4.1, I could run sudo /etc/init.d/vboxdrv setup and sudo modprobe vboxdrv just fine, as well as start VMs.







                                  share|improve this answer












                                  share|improve this answer



                                  share|improve this answer










                                  answered Dec 18 '14 at 20:36









                                  Anthony NaddeoAnthony Naddeo

                                  1613




                                  1613























                                      1














                                      You have to check the version of gcc your are using. I was facing the same problem of virtualbox kernel compilation.
                                      I fixed the issue using this post https://www.virtualbox.org/ticket/12467



                                      You probably are using a outdated version of gcc that is different of the gcc used by the Linux kernel.



                                      Check the default version your are using :



                                      gcc -v


                                      Mine is gcc version 4.4.7 (Ubuntu/Linaro 4.4.7-8ubuntu1)



                                      And the gcc version your kernel was compiled with



                                      dmesg | more
                                      [ 0.000000] Linux version 3.13.0-83-generic (buildd@lgw01-55) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #127-Ubuntu SMP Fri Mar 11 00:25:37 UTC 2016 (Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35)


                                      or with



                                      dpkg -l gcc


                                      If the gcc versions are different like on my system, switch your default gcc compiler



                                      sudo update-alternatives --config gcc


                                      then virtualbox-dkms installation should works fine



                                      sudo apt-get --reinstall install virtualbox-dkms





                                      share|improve this answer




























                                        1














                                        You have to check the version of gcc your are using. I was facing the same problem of virtualbox kernel compilation.
                                        I fixed the issue using this post https://www.virtualbox.org/ticket/12467



                                        You probably are using a outdated version of gcc that is different of the gcc used by the Linux kernel.



                                        Check the default version your are using :



                                        gcc -v


                                        Mine is gcc version 4.4.7 (Ubuntu/Linaro 4.4.7-8ubuntu1)



                                        And the gcc version your kernel was compiled with



                                        dmesg | more
                                        [ 0.000000] Linux version 3.13.0-83-generic (buildd@lgw01-55) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #127-Ubuntu SMP Fri Mar 11 00:25:37 UTC 2016 (Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35)


                                        or with



                                        dpkg -l gcc


                                        If the gcc versions are different like on my system, switch your default gcc compiler



                                        sudo update-alternatives --config gcc


                                        then virtualbox-dkms installation should works fine



                                        sudo apt-get --reinstall install virtualbox-dkms





                                        share|improve this answer


























                                          1












                                          1








                                          1







                                          You have to check the version of gcc your are using. I was facing the same problem of virtualbox kernel compilation.
                                          I fixed the issue using this post https://www.virtualbox.org/ticket/12467



                                          You probably are using a outdated version of gcc that is different of the gcc used by the Linux kernel.



                                          Check the default version your are using :



                                          gcc -v


                                          Mine is gcc version 4.4.7 (Ubuntu/Linaro 4.4.7-8ubuntu1)



                                          And the gcc version your kernel was compiled with



                                          dmesg | more
                                          [ 0.000000] Linux version 3.13.0-83-generic (buildd@lgw01-55) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #127-Ubuntu SMP Fri Mar 11 00:25:37 UTC 2016 (Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35)


                                          or with



                                          dpkg -l gcc


                                          If the gcc versions are different like on my system, switch your default gcc compiler



                                          sudo update-alternatives --config gcc


                                          then virtualbox-dkms installation should works fine



                                          sudo apt-get --reinstall install virtualbox-dkms





                                          share|improve this answer













                                          You have to check the version of gcc your are using. I was facing the same problem of virtualbox kernel compilation.
                                          I fixed the issue using this post https://www.virtualbox.org/ticket/12467



                                          You probably are using a outdated version of gcc that is different of the gcc used by the Linux kernel.



                                          Check the default version your are using :



                                          gcc -v


                                          Mine is gcc version 4.4.7 (Ubuntu/Linaro 4.4.7-8ubuntu1)



                                          And the gcc version your kernel was compiled with



                                          dmesg | more
                                          [ 0.000000] Linux version 3.13.0-83-generic (buildd@lgw01-55) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #127-Ubuntu SMP Fri Mar 11 00:25:37 UTC 2016 (Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35)


                                          or with



                                          dpkg -l gcc


                                          If the gcc versions are different like on my system, switch your default gcc compiler



                                          sudo update-alternatives --config gcc


                                          then virtualbox-dkms installation should works fine



                                          sudo apt-get --reinstall install virtualbox-dkms






                                          share|improve this answer












                                          share|improve this answer



                                          share|improve this answer










                                          answered Mar 23 '16 at 10:15









                                          JohnWolfJohnWolf

                                          112




                                          112























                                              0














                                              The clue is here: Please install the virtualbox-dkms package and the appropriate
                                              headers, most likely linux-headers-generic.



                                              Since you have the first, it must still want the second.



                                              sudo apt-get install linux-headers-generic



                                              Then make sure everything is up to date.



                                              sudo apt-get update



                                              sudo apt-get upgrade






                                              share|improve this answer





















                                              • 2





                                                Sorry just forgot to write that I have them too. linux-headers-generic is already the newest version. is the output when i try to install them.

                                                – Antonis Gr
                                                May 13 '14 at 20:11






                                              • 2





                                                Thank you, I added that information to your question to insure that you get accurate answers

                                                – Elder Geek
                                                May 13 '14 at 20:15
















                                              0














                                              The clue is here: Please install the virtualbox-dkms package and the appropriate
                                              headers, most likely linux-headers-generic.



                                              Since you have the first, it must still want the second.



                                              sudo apt-get install linux-headers-generic



                                              Then make sure everything is up to date.



                                              sudo apt-get update



                                              sudo apt-get upgrade






                                              share|improve this answer





















                                              • 2





                                                Sorry just forgot to write that I have them too. linux-headers-generic is already the newest version. is the output when i try to install them.

                                                – Antonis Gr
                                                May 13 '14 at 20:11






                                              • 2





                                                Thank you, I added that information to your question to insure that you get accurate answers

                                                – Elder Geek
                                                May 13 '14 at 20:15














                                              0












                                              0








                                              0







                                              The clue is here: Please install the virtualbox-dkms package and the appropriate
                                              headers, most likely linux-headers-generic.



                                              Since you have the first, it must still want the second.



                                              sudo apt-get install linux-headers-generic



                                              Then make sure everything is up to date.



                                              sudo apt-get update



                                              sudo apt-get upgrade






                                              share|improve this answer















                                              The clue is here: Please install the virtualbox-dkms package and the appropriate
                                              headers, most likely linux-headers-generic.



                                              Since you have the first, it must still want the second.



                                              sudo apt-get install linux-headers-generic



                                              Then make sure everything is up to date.



                                              sudo apt-get update



                                              sudo apt-get upgrade







                                              share|improve this answer














                                              share|improve this answer



                                              share|improve this answer








                                              edited May 14 '14 at 13:13

























                                              answered May 13 '14 at 19:58









                                              Elder GeekElder Geek

                                              27.6k1055130




                                              27.6k1055130








                                              • 2





                                                Sorry just forgot to write that I have them too. linux-headers-generic is already the newest version. is the output when i try to install them.

                                                – Antonis Gr
                                                May 13 '14 at 20:11






                                              • 2





                                                Thank you, I added that information to your question to insure that you get accurate answers

                                                – Elder Geek
                                                May 13 '14 at 20:15














                                              • 2





                                                Sorry just forgot to write that I have them too. linux-headers-generic is already the newest version. is the output when i try to install them.

                                                – Antonis Gr
                                                May 13 '14 at 20:11






                                              • 2





                                                Thank you, I added that information to your question to insure that you get accurate answers

                                                – Elder Geek
                                                May 13 '14 at 20:15








                                              2




                                              2





                                              Sorry just forgot to write that I have them too. linux-headers-generic is already the newest version. is the output when i try to install them.

                                              – Antonis Gr
                                              May 13 '14 at 20:11





                                              Sorry just forgot to write that I have them too. linux-headers-generic is already the newest version. is the output when i try to install them.

                                              – Antonis Gr
                                              May 13 '14 at 20:11




                                              2




                                              2





                                              Thank you, I added that information to your question to insure that you get accurate answers

                                              – Elder Geek
                                              May 13 '14 at 20:15





                                              Thank you, I added that information to your question to insure that you get accurate answers

                                              – Elder Geek
                                              May 13 '14 at 20:15











                                              0














                                              I had the same issue. I found that the source of the problem is most probably that I'm using a custom kernel.



                                              Downloading the latest .deb package from virtualbox.org, and installing it by dpkg -i has solved the problem in my case.






                                              share|improve this answer




























                                                0














                                                I had the same issue. I found that the source of the problem is most probably that I'm using a custom kernel.



                                                Downloading the latest .deb package from virtualbox.org, and installing it by dpkg -i has solved the problem in my case.






                                                share|improve this answer


























                                                  0












                                                  0








                                                  0







                                                  I had the same issue. I found that the source of the problem is most probably that I'm using a custom kernel.



                                                  Downloading the latest .deb package from virtualbox.org, and installing it by dpkg -i has solved the problem in my case.






                                                  share|improve this answer













                                                  I had the same issue. I found that the source of the problem is most probably that I'm using a custom kernel.



                                                  Downloading the latest .deb package from virtualbox.org, and installing it by dpkg -i has solved the problem in my case.







                                                  share|improve this answer












                                                  share|improve this answer



                                                  share|improve this answer










                                                  answered Mar 23 '15 at 11:29









                                                  Attila FulopAttila Fulop

                                                  550720




                                                  550720























                                                      -1














                                                      Try



                                                      sudo /etc/init.d/vboxdrv setup





                                                      share|improve this answer




























                                                        -1














                                                        Try



                                                        sudo /etc/init.d/vboxdrv setup





                                                        share|improve this answer


























                                                          -1












                                                          -1








                                                          -1







                                                          Try



                                                          sudo /etc/init.d/vboxdrv setup





                                                          share|improve this answer













                                                          Try



                                                          sudo /etc/init.d/vboxdrv setup






                                                          share|improve this answer












                                                          share|improve this answer



                                                          share|improve this answer










                                                          answered May 21 '14 at 12:09









                                                          Abdul KadirAbdul Kadir

                                                          30819




                                                          30819

















                                                              protected by Community Oct 23 '17 at 9:19



                                                              Thank you for your interest in this question.
                                                              Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



                                                              Would you like to answer one of these unanswered questions instead?



                                                              Popular posts from this blog

                                                              Human spaceflight

                                                              Can not write log (Is /dev/pts mounted?) - openpty in Ubuntu-on-Windows?

                                                              File:DeusFollowingSea.jpg