Did You Know?
Got a tip? Let us know

We are pleased to announce our new TecMint Q/A section to submit your Linux questions

VirtualBox 4.3 Released – Install on RHEL/CentOS/Fedora and Ubuntu/Linux Mint

Download Your Free eBooks NOW - 10 Free Linux eBooks for Administrators
CW

VirtualBox is an open source cross-platform virtualization software, it can be installed on any operating system and enable you to install and run multiple guest operating systems on same computer. For example, if you install it on your Linux system, you can run Windows XP operating system under it as a Guest OS or run Linux OS on your Windows system and so on. This way, you can install and run as many as guest operating systems as you like, the only limit is disk space and memory.

Install Virtualbox in Linux

Install Virtualbox in Linux

Recently Oracle has released latest stable version of Virtualbox 4.3, the newest version of Virtual box comes with so many major changes and new features added to it.

Whats new in Virtualbox 4.3

  1. Virtual Multi-Touch USB interface
  2. Video Capturing feature for recording Virtual box sessions.
  3. New Popup to display various info and warnings on the top of the VM.
  4. Allows to create and edit general keyboard shortcuts.
  5. Major changes in VT-x code and the AMD-V code for many bug fixes and performance improvements.
  6. Ipv6 support
  7. It introduces a lightweight instruction interpreter for situations that are not handled by hardware virtualization.
  8. Comes with SCSI CD-ROM emulation, while including boot support.
  9. Fixed the problems with Live snapshat to made it work again.
  10. Guest sessions will now be running in dedicated resources, impersonated session processes.
  11. IGuestFile support
  12. Introducing a virtual router mode with NAT.
  13. 3D acceleration for Ubuntu and Fedora is improved.
  14. Multi-monitor support enhanced
  15. Support for Windows 8.1, Windows Server 2012 R2 and Mac OS X 10.9
  16. Use the XDG standard configuration folder instead of .VirtualBox on systems
  17. Support loading HGCM modules with extension pack framework
  18. Fixed udev detection in the init script with Linux 3.x kernels
  19. Shared Clipboard/X11 will now supports BMP-format images

You can see the complete new change log details about VirtualBox 4.3 on their Official Changelog Page.

This guide explains how to install VirtualBox 4.3 on RHEL 6.4/6.3/6.2/6.1/6.0/5.9/5.8/5.6, CentOS 6.4/6.3/6.2/6.1/6.0/5.9/5.8/5.6 and Fedora 19,18,17,16,15,14,13,12 systems using VirtualBox’s own repository with YUM tool.

This guide also explains how to install VirtualBox 4.3 on Ubuntu 13.10/13.04/12.10/12.04 and Linux Mint 15/14/13 systems using VirtualBox’s own repository with APT-GET command.

Installing VirtualBox 4.3 in RHEL/CentOS and Fedora

If you’ve any earlier version of Virtualbox installed, remove that before installing latest version.

# yum remove VirtualBox-4.2

Adding VirtualBox Repository

Next add the VirtualBox own repository to install latest VirtualBox 4.3 on following systems.

For RHEL/CentOS 6.4-5.9
## RHEL 6.4/6.3/6.2/6.1/6.0/5.9/5.8/5.6 and CentOS 6.4/6.3/6.2/6.1/6.0/5.9/5.8/5.6 ##
# cd /etc/yum.repos.d/
# wget http://download.virtualbox.org/virtualbox/rpm/rhel/virtualbox.repo
For RHEL/CentOS 5
## RHEL 5 and CentOS 5 ##
# wget http://dl.fedoraproject.org/pub/epel/5/i386/epel-release-5-4.noarch.rpm
# rpm -Uvh epel-release-5-4.noarch.rpm
For Fedora 19,18,17,16,15,14,13,12
## Fedora 19,18,17,16,15,14,13,12 ##
# cd /etc/yum.repos.d/
# wget http://download.virtualbox.org/virtualbox/rpm/fedora/virtualbox.repo

Install Dependency Packages for VirtualBox

VirtualBox uses vboxdrv kernel module to control and allocate physical memory for execution of guest operating systems. Without this module, you can still use the VirtualBox to create and configure virtual machines, but they will not work. So, to make VirtualBox fully functional you will need to update your system first, then install some additional modules like DKMS, kernel-headers and kernel-devel and some dependency packages.

# yum update
# yum install binutils qt gcc make patch libgomp glibc-headers glibc-devel kernel-headers kernel-devel dkms

Install VirtualBox 4.3

Once you’ve installed all the needed dependency packages, you can install latest version of VirtualBox using following command.

# yum install VirtualBox-4.3

Rebuild Kernel Modules for VirtualBox 4.3

The below command will automatically create vboxusers group and user and also search and automatically rebuild required kernel modules. If the below build process fails, you will get a warning messages. Please have a look at /var/log/vbox-install.log to trace why the build process failed.

# /etc/init.d/vboxdrv setup
OR 
# service vboxdrv setup

Troubleshooting

If you get any error message like KERN_DIR or if your kernel source directory not detected automatically by build process, you can set it by using following command. Make sure you change kernel version according to your system as shown in red color.

## RHEL / CentOS / Fedora ##
KERN_DIR=/usr/src/kernels/2.6.18-194.11.1.el5-x86_64

## Export KERN_DIR ##
export KERN_DIR

Installing VirtualBox 4.3 in Ubuntu and Linux Mint

First, uninstall any earlier version of Virtualbox if any.

$ sudo apt-get remove virtualbox-4.2

Next, install latest 4.3 version using official Virtualbox repository. To add the repository, use the following command as shown.

$ echo "deb http://download.virtualbox.org/virtualbox/debian $(lsb_release -sc) contrib" | sudo tee /etc/apt/sources.list.d/virtualbox.list
$ wget -q http://download.virtualbox.org/virtualbox/debian/oracle_vbox.asc -O- | sudo apt-key add -
$ sudo apt-get update
$ sudo apt-get install virtualbox-4.3

Starting VirtualBox 4.3

Simply execute following command to start it from the terminal or use launcher from menu to start.

# VirtualBox
VirtualBox Screenshots
Virtualbox 4.3

Virtualbox 4.3 Preview

Virtualbox Video Capture

Virtualbox Video Capture Support

Virtualbox 4.3 Running VM's

Virtualbox 4.3 Running VM’s

Installing VirtualBox Extension Pack

If you need some additional functionality such as VirtualBox RDP, PXE, ROM with E1000 support and USB 2.0 Host Controller support, etc. You need to download and install the VirtualBox Extension Pack using following wget command.

# wget http://download.virtualbox.org/virtualbox/4.3.0/Oracle_VM_VirtualBox_Extension_Pack-4.3.0-89960.vbox-extpack

To install the extension pack, you must have Virtualbox 4.3 installed, once you downloaded vbox-extpack open with Virtualbox as shown below. If it doesn’t work out, then open Virtaulbox –> Preferences –> Extensions and browse for the vbox-extpack to install it.

Install VirtualBox Extension Pack

Install VirtualBox Extension Pack

VirtualBox Extension Pack

VirtualBox Extension Pack

Updating VirtualBox

If you want to update the VirtualBox with latest version in the future, you can simply run the following command to update it.

On RHEL/CentOS/Fedora
# yum update VirtualBox-4.3
On Ubuntu/Linux Mint
# apt-get install VirtualBox-4.3

Remove VirtualBox

If in case you want to remove VirtualBox completely, just use the following command to remove it completely from your system.

On RHEL/CentOS/Fedora
# cd /etc/yum.repos.d/
# rm -rf virtualbox.repo
# yum remove VirtualBox-4.2
On Ubuntu/Linux Mint
# apt-get remove VirtualBox-4.3

You can also Download VirtualBox 4.3 for other Linux, Windows and Mac OS X platforms.

Ravi Saive

Owner at TecMint.com
Simple Word a Computer Geek and Linux Guru who loves to share tricks and tips on Internet. Most Of My Servers runs on Open Source Platform called Linux.

Linux Services & Free WordPress Setup

Our post is simply ‘DIY’ aka ‘Do It Yourself, still you may find difficulties and want us to help you out. We offer wide range of Linux and Web Hosting Solutions at fair minimum rates. Please submit your orders by Clicking Here.

81 Responses

  1. John R says:

    This was perfect! Thanks for publishing, it really saved me a lot of time. I didn’t see anything in the docs on how to pull down all of the dependencies and I was constantly failing installs. This time I received errors on the DKMS not being there, but it still compiled and I was able to import an appliance built on an OSX computer without a problem.

  2. Darin says:

    I’ve been everywhere trying to get this to work and it won’t no matter what I do.

    I’ve set the KERN_DIR variable. see:

    [root@derwood kernels]# set | grep KERN
    KERN_DIR=/usr/src/kernels/2.6.32-279.11.1.el6.centos.plus.x86_64

    [root@derwood kernels]# ls
    2.6.32-279.11.1.el6.centos.plus.x86_64
    [root@derwood kernels]# pwd
    /usr/src/kernels

    Yet when I try to set up vboxdev, I get this:

    Error! Your kernel headers for kernel 2.6.32-279.el6.x86_64 cannot be found at
    /lib/modules/2.6.32-279.el6.x86_64/build or /lib/modules/2.6.32-279.el6.x86_64/source.
    [FAILED]
    (Failed, trying without DKMS)
    Recompiling VirtualBox kernel modules [FAILED]

    It points to the wrong directory.. This is on a fresh install of Centos 6.3. No updates applied to it.

    Any ideas would be appreciated.

    • Ravi Saive says:

      @Darin – Have you installed required dependency packages like kernel-headers kernel-devel?

      If not please install it, The error clearly saying that “kernel headers cannot be found”.

      Please install and try again..

      • Darin says:

        @Ravi
        Yeah.. I had the headers and kernel-devel installed. I figured out the problem.
        For some reason, the kernel headers were for a newer kernel.. I uninstalled the headers, did a full yum update, then reinstalled everything and it worked properly. Don’t know why yum did that but its fixed.

        • Toonz says:

          The reboot did the trick because the yum update caused you to have a higher kernel version. Next time u should just reboot and you will see that your kernel will be updated also (uname -r and ls in the src dir)

      • Raju says:

        Hi Ravi
        I tried to install virtualbox on centos 5.9 but it failed
        It was upgraded to 2.6.18-348.16.1.el5-xen-x86_64 and vertualbox does not support xen
        How to rectify the problem
        Thanks
        Ojha

  3. Suresh P R says:

    Thank you very much Ravi . It perfectly worked and once again thank you……..

  4. rene cardoso says:

    I am very impressed by your achivements, I was greatly helpfull to me , I just transfer a virtual box (cloned) from a win 7 ultimate host to a centos host , inside my vm i had a centos server running my web sites,
    Thank you so much!!!! I had a kernell problem when I moved and try to install the clone files (vdi) , Because I am a newbie on linux, and I am loving it, but I don’t quite understand how everything works, But I made it , Thanks to God, and your nice explanation here , I find it out that you have to do by rpm and repo files otherwise will not work at all, at the begin I had installed by the binary package … :( , then to fix it I have removed the installation and follow your steps on how to install and works just great!!!! May God Bless you Greatly!!!!!.. Thank you!!!…

  5. Nicholas Barraco says:

    Thank you so much! This really helped me out.

  6. Prasad says:

    Thanks Ravi you are a star , thanks a ton……

  7. Arfat says:

    Hello Friends,

    I am getting the below error while yum update after downloading virtualbox.repo

    [root@025 yum.repos.d]# yum -y update
    Loaded plugins: aliases, changelog, downloadonly, fastestmirror, kabi, presto, refresh-packagekit, security, tmprepo, verify,
    : versionlock
    Loading support for CentOS kernel ABI
    Loading mirror speeds from cached hostfile
    * base: mirror.nbrc.ac.in
    * epel: mirrors.ispros.com.bd
    * extras: mirror.nbrc.ac.in
    * updates: mirror.nbrc.ac.in
    virtualbox/primary | 226 B 00:00
    http://download.virtualbox.org/virtualbox/rpm/el/6/x86_64/repodata/primary.xml.gz: [Errno -1] Metadata file does not match checksum
    Trying other mirror.
    Error: failure: repodata/primary.xml.gz from virtualbox: [Errno 256] No more mirrors to try.

    Please Help.

  8. Derwood says:

    Ravi,
    Centos 6.4 is out and so is VirtualBox 4.2.10. Any pointers for upgrading from Centos 6.3 and VirtualBox 4.2.6?
    I figure a yum update and a reboot to go to Centos 6.4. Then what? Do a service vboxdrv setup? and a yum update VirtualBox-4.2?

    Think anything else will be needed?

    • Ravi Saive says:

      @Derwood,

      I have already written a fair article that show you how to upgrade from any CentOS 6.x to CentOS 6.4.

      I have updated this article to Virtualbox 4.2.10, simple follow the above steps to install it. If any please do let me know..

      • Derwood says:

        Well, I upgraded from CentOS 6.3 to CentOS 6.4, and also update Virtualbox to 4.2.10. Everything went fine except for one small problem.

        I have no text visible in any window or on any of the task bars.
        I managed to get Virtualbox started by blind guessing where its icon was and I got the VMs to start after it started. So they’re up, but still no text in the windows.

        here’s a screenshot from a vnc session:

        http://i11.photobucket.com/albums/a188/derwood5555/desktop_zps3676fb15.png

        Any ideas?

        • Ravi Saive says:

          No idea man, try rebooting the machine may work..

          • derwood says:

            Yeah.. I tried rebooting.. It’s apparently a problem with the nouveau driver. It has issues.
            I’m either going to have to put a different video card in or install nvidia proprietary drivers.

  9. Marcelo says:

    Thank you very much!!!

  10. derwood says:

    I figured it out.. I had to blacklist the nouveau module on the grub line, and then do Xorg -configure to generate a new xorg.conf.

    It’s working again.

  11. Sachin says:

    “KERN_DIR or if your kernel source directory not detected automatically by build process”
    I got this error msg on RHEL 6.4.

    KERN_DIR=/usr/src/kernels/2.6.18-194.11.1.el5-x86_64
    export KERN_DIR

    Exactly where i can run this commands ? or write in conf file ? or run on terminal ?

  12. Andres Maurer says:

    Hi. I have installed VirtualBox over a Centos system but when I try to start VirtualBox I get a message

    Failed to open the X11 display.

    What can I do ?

    Thanks

    Andres

    • Ravi Saive says:

      I think you trying to launch program from the terminal, that’s the reason you getting such error. If you are already in X Window, try to start from the Application Menu.

      • Andres Maurer says:

        Hi. Thank you for your answer. How do I know if I am in X Windows. I am issuing the command from the command line and as a Root user.

        Regards

  13. Andres Maurer says:

    I am sorry, before that error message I get this one.

    When trying to recompile kernel modules by issuing

    service vboxdrv setup

    I get this message

    TSC mode is “synchronous”, kernel timer mode is “normal”

    Thanks

    Andres

    • Ravi Saive says:

      Try to uninstall and re-install again VirtualBox and start the service this way.

      # /etc/init.d/vboxdrv setup
      
      • Andres Maurer says:

        Hi. I did so but I keep getting the same error and the kernel does’t compile.

        • Ravi Saive says:

          Which CentOS version you using? Have you installed all the required packages as shown above in this article? after installing virtualbox you restarted system. I think any of the below packages missed, install them.

          # yum install dkms binutils gcc make patch libgomp glibc-headers 
          glibc-devel kernel-headers kernel-devel
          
  14. Andres Maurer says:

    Hi. I did that and have exactly the same behaviour.
    Error messages

    TSC mode is ‘synchronous’, kernel mode is ‘normal’
    vboxpci: IOMMU not found (not compiled)

    Thanks

  15. Anthony says:

    Good post, however , you don’t need to run the setup and if dkms is installed it will automatically rebuild the kernel module. If you set up the kernels and build tools and then install Virtualbox as stated in this article.

    http://minimallinux.blogspot.co.uk/2012/07/centos-6-install-virtualbox-guest-os.html

    You should be fine.

  16. litorve says:

    I have followed the steps for installing virtualbox 4.2 in my newly installed fedora 17 OS and having the problem is:
    1. When i started the virtualbox and created a xp system and when i clicked on start then i got this-

    Kernel driver not installed (rc=-1908)

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

    2. after abort this window a second window showing the message this–

    Failed to open a session for the virtual machine xp.

    The virtual machine ‘xp’ has terminated unexpectedly during startup with exit code

    1.
    Result Code: NS_ERROR_FAILURE (0×80004005)
    Component: Machine
    Interface: IMachine {22781af3-1c96-4126-9edf-67a020e0e858}

    after that i have installed jre but it still having problems same as above.

    please reply what to do?

  17. Aniket Lamba says:

    Loaded plugins: langpacks, presto, refresh-packagekit
    Setting up Remove Process
    No Match for argument: VirtualBox-4.2
    Cairo-Dock | 2.9 kB 00:00
    Dropbox | 951 B 00:00
    adobe-linux-i386 | 951 B 00:00
    adobe-linux-x86_64 | 951 B 00:00
    google-chrome | 951 B 00:00
    google-earth | 951 B 00:00
    google-talkplugin | 951 B 00:00
    livna | 3.6 kB 00:00
    rpmfusion-free-updates | 3.3 kB 00:00
    skype | 1.2 kB 00:00
    updates/metalink | 6.2 kB 00:00
    No Packages marked for removal
    [root@core yum.repos.d]# ^C
    [root@core yum.repos.d]#

    I am using Fedora 15 and donno why I am getting this error. :/

  18. Anand says:

    Ravi, does this installation works on Centos 5.3? and, Is the web interface included in this installation?

  19. David says:

    Well, after try everything i had to run “yum update” then “service vboxdrv setup ”
    and works great!
    I loaded virtualbox without any strange message and i’m ready to put a Winbloods guest

    THANKS for your appreciable HELP!!

  20. David says:

    i forgot to tell you that i’m using Centos 6.4 with a 2.6.32-358.14.1.el6.i686 kernel and Virtualbox is 4.2.16 version…

    Thanks!!

  21. Scott C says:

    Thanks! Huge help! I was struggling to get this work on 3.10.9-200.fc19.x86_64.

  22. Anand says:

    Hi Ravi, I am getting this same error as Andres Maurer
    “Failed to open the X11 display!”
    I am on CentOS 6.4 and logging in via putty.

    • Ravi Saive says:

      You cannot start Virtualbox from PUTTY, you need to be logged in GUI mode to start it. PUTTY is made for to access CLI, not GUI.

  23. Raju says:

    I gives an error with Xen kernel which is created after upgradation of centos 5.6 to 5.9
    These are the errors. Please suggest to rectify the problem.
    Thanks

    (Running VirtualBox in a Xen environment is not supported)

  24. Miguel says:

    Thank you very much for this guide. It worked for me. I had wasted a few hours and I didn’t know how to fix a trouble in the installation of Virtual Box.
    This guide is very clear.

  25. j2 says:

    Hi Ravi, I follow the instructions step by step on installing VirtualBox-4.3. My distro is fedora 19. But still I’m having a problem.

    here’s the details:

    $cd /etc/yum.repos.d/
    $wget http://download.virtualbox.org/virtualbox/rpm/fedora/virtualbox.repo
    $yum -y update
    $yum -y install binutils qt gcc make patch libgomp glibc-headers glibc-devel kernel-headers kernel-devel dkms
    $yum -y install VirtualBox-4.3

    Here’s the Error:

    VirtualBox-4.3-4.3.0_89960_fed FAILED ] 79 B/s | 26 MB 220:34:39 ETA
    http://download.virtualbox.org/virtualbox/rpm/fedora/19/i386/VirtualBox-4.3-4.3.0_89960_fedora18-1.i686.rpm: [Errno 12] Timeout on http://download.virtualbox.org/virtualbox/rpm/fedora/19/i386/VirtualBox-4.3-4.3.0_89960_fedora18-1.i686.rpm: (28, ‘Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds’)
    Trying other mirror.

    Error downloading packages:
    VirtualBox-4.3-4.3.0_89960_fedora18-1.i686: [Errno 256] No more mirrors to try.

    • Ravi Saive says:

      Its seems your internet speed is very slow, its transferring data less than 1000 bytes as shown error.

      • j2 says:

        I see. thanks for the reply. Is there any alternative solution for that?

      • Dave says:

        I have the same issue.
        This is not an internet speed issue, this is something else or something deeper. I have had this issue with Virtualbox installation from the repo for over 8 hours now, I just watched a full length Bollywood movie, ran Flash plugin on Chrome, Firefox and Opera (mostly youtube) on Ubuntu and Centos 6.5, downloaded 150+ MB worth of yum updates yet virtualbox.org wont even ping from the command line.

        But if I go via normal browser http, virtualbox.org loads fine and the downloads seem to be working too.

        I hate to do rpm installs when yum repos can do the trick.

        So if this keeps happening over the next 24 hours, I guess this means I use rpm installation as given on the virtualbox.org site?

        Will that work or is it a known bad thing to do?

        thanks,
        dave

  26. Nick says:

    I can’t get bridged networking to work in FC19. Has anyone else gotten this to work?

  27. Chris says:

    In Fedora 19 (today), there is no /etc/init.d/vboxdrv file. I’m trying to get virtualbox running via vagrant, and when I try a “vagrant box add…” I get an error that the kernel module is not loaded.

    This might be useful:
    $ systemctl status systemd-modules-load.service
    systemd-modules-load.service – Load Kernel Modules
    Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static)
    Active: failed (Result: exit-code) since Mon 2013-11-11 13:04:38 CST; 11s ago
    Docs: man:systemd-modules-load.service(8)
    man:modules-load.d(5)
    Process: 6298 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)

    Nov 11 13:04:38 x1-idlelion-net systemd-modules-load[6298]: Failed to insert ‘vboxdrv’: Required key not available
    Nov 11 13:04:38 x1-idlelion-net systemd[1]: systemd-modules-load.service: main process exited, code=exited, status=1/FAILURE
    Nov 11 13:04:38 x1-idlelion-net systemd[1]: Failed to start Load Kernel Modules.
    Nov 11 13:04:38 x1-idlelion-net systemd[1]: Unit systemd-modules-load.service entered failed state.

    The “required key not available” is a big red flag for me, but I’m not sure how to proceed. Any help greatly appreciated.

  28. Thommy M. says:

    Hi,

    I followed the instructions above and all was OK until the latest step.
    How can I get the vboxdrv to compile against the correct headers? I’m on Fedora 18.

    # /etc/init.d/vboxdrv setup
    Stopping VirtualBox kernel modules [ OK ]
    Uninstalling old VirtualBox DKMS kernel modules [ OK ]
    Removing old VirtualBox pci kernel module [ OK ]
    Removing old VirtualBox netadp kernel module [ OK ]
    Removing old VirtualBox netflt kernel module [ OK ]
    Removing old VirtualBox kernel module [ OK ]
    Trying to register the VirtualBox kernel modules using DKMSError! echo
    Your kernel headers for kernel 3.11.4-101.fc18.x86_64 cannot be found at
    /lib/modules/3.11.4-101.fc18.x86_64/build or /lib/modules/3.11.4-101.fc18.x86_64/source.
    [FAILED]
    (Failed, trying without DKMS)
    Recompiling VirtualBox kernel modules [ OK ]
    Starting VirtualBox kernel modules [FAILED]
    (modprobe vboxdrv failed. Please use ‘dmesg’ to find out why)
    [root@leia ~]# echo $KERN_DIR
    /usr/src/kernels/3.11.7-100.fc18.x86_64
    # uname -r
    3.11.4-101.fc18.x86_64
    # yum -y install kernel-devel kernel-headers-$(uname -r)
    Loaded plugins: fastestmirror, langpacks, presto, refresh-packagekit
    Repository google-chrome is listed more than once in the configuration
    Loading mirror speeds from cached hostfile
    * fedora: mirror.proserve.nl
    * rpmfusion-free: mirror.proserve.nl
    * rpmfusion-free-updates: mirror.proserve.nl
    * rpmfusion-nonfree: mirror.proserve.nl
    * rpmfusion-nonfree-updates: mirror.proserve.nl
    * updates: mirror.proserve.nl
    Package kernel-devel-3.11.7-100.fc18.x86_64 already installed and latest version
    No package kernel-headers-3.11.4-101.fc18.x86_64 available.
    Nothing to do

  29. Thommy M. says:

    Sorry for wasting bandwidth, it was only a reboot that was needed to align the running kernel with the header files. Silly me…

  30. Edrisse Chermak says:

    Dear all,
    I’m on Fedora 19 and up to date. I got the error message you put in “Troubleshooting”.
    Then I applied the KERN_DIR operation with my kernel version :

    [root@localhost ]# KERN_DIR=/usr/src/kernels/3.11.9-200.fc19.i686/
    [root@localhost ]# export KERN_DIR

    Unfortunately, I still get an error I don’t understand :

    [root@localhost ]# /etc/init.d/vboxdrv setup
    Stopping VirtualBox kernel modules [ OK ]
    Uninstalling old VirtualBox DKMS kernel modules [ OK ]
    Removing old VirtualBox pci kernel module [ OK ]
    Removing old VirtualBox netadp kernel module [ OK ]
    Removing old VirtualBox netflt kernel module [ OK ]
    Removing old VirtualBox kernel module [ OK ]
    Trying to register the VirtualBox kernel modules using DKMSError! echo
    Your kernel headers for kernel 3.9.5-301.fc19.i686 cannot be found at
    /lib/modules/3.9.5-301.fc19.i686/build or /lib/modules/3.9.5-301.fc19.i686/source.
    [FAILED]
    (Failed, trying without DKMS)
    Recompiling VirtualBox kernel modules [ OK ]
    Starting VirtualBox kernel modules [FAILED]
    (modprobe vboxdrv failed. Please use ‘dmesg’ to find out why)

    [root@localhost ]# tail dmesg
    [23018.339440] vboxdrv: version magic ’3.11.9-200.fc19.i686 SMP mod_unload 686 ‘ should be ’3.9.5-301.fc19.i686 SMP mod_unload 686 ‘

    any idea ?
    Thanks,

  31. Edrisse Chermak says:

    Well, I guess there’s a kernel downgrade story there since I don’t see any 3.9 version on my /usr/src/kernels/ .. But no problem, because I choosed a simpler solution : switching to kvm/qemu ^^
    Cheers,
    Edrisse

  32. gogomilky says:

    CENTOS 6.4 kernel -2.6.32-358.el6.x86_64

    everything was fine to the finaly step when I received a message that libpython requires
    then I installed “yum installed python-devel.x86_64″ but the same problem persist on the end of installation process?

    What I should to do ?
    thanks

  33. Christian says:

    I’m running a CentOs 6.5 Kernel Linux 2.6.32-431.1.2.0.1.el6.686 and install Virtualbox 4.3.6

    All goes fine until the end of the instalation process but launching VirtualBox on a command line give the following :

    # VirtualBox
    Segmentation fault (core dumped)

    With no more information.

    Any idea ?
    Christian.

    • Christian says:

      Sorry for the lack of information but it’s impossible to launch it. Th elast vBox.log I get is a really old and not one generated by a recent session.
      On another hand there is tons of segmentation faul issues genrated by VirtualBox for various reasons that it is a nightmare to find if my problem was met or not.
      The debug mode sounds like unable to be activated.
      i’m feeling a little bit disarmed.

      Christian.

      • oz says:

        Hi Christian I have the same issue on centos 6.x

        VirtualBox[6343]: segfault at b3e14000 ip 01e6ccbc sp bffa8c94 error 7 in libQtGui.so.4.6.2[1d51000+9ff000]

        Did u find any solution ?

  34. devx says:

    awsome examples thank you so much ravi bhai

  35. massy says:

    Hi,
    When I run this command:
    service vboxdrv setup
    the error is shown,what should I do?

    Stopping VirtualBox kernel modules [ OK ]
    Uninstalling old VirtualBox DKMS kernel modules [ OK ]
    Trying to register the VirtualBox kernel modules using DKMSError! echo
    Your kernel headers for kernel 2.6.32-431.3.1.el6.x86_64 cannot be found at
    /lib/modules/2.6.32-431.3.1.el6.x86_64/build or /lib/modules/2.6.32-431.3.1.el6.x86_64/source.
    [FAILED]
    (Failed, trying without DKMS)
    Recompiling VirtualBox kernel modules [FAILED]
    (Look at /var/log/vbox-install.log to find out what went wrong)

  36. anon says:

    make sure the kmod version matches you kernel version

  37. anon says:

    kmod_virtual box

  38. Zane says:

    VirtualBox: supR3HardenedMainGetTrustedMain: dlopen(“/usr/lib/virtualbox/VirtualBox.so”,) failed: /usr/lib64/libGL.so.1: undefined symbol: _XGetRequest

  39. Zane says:

    Does anybody help me with the problem?

    • Ravi Saive says:

      I think you’re using Ubuntu distribution, if yes, just re-install the Virtualbox with the help of following command.

      $ sudo apt-get install virtualbox-3.2 --reinstall
      
      • Ravi Saive says:

        Another reason is, your libGL.so.1 might be installed on different directly. Just find the libGL.so.1 and copy to /usr/lib/virtualbox/ will fix your problem.

  40. Zane says:

    I copied libGL.so.1 from /usr/lib64 to /usr/lib/virtualbox , The error information is changed as below.

    VirtualBox: supR3HardenedMainGetTrustedMain: dlopen(“/usr/lib/virtualbox/VirtualBox.so”,) failed: /usr/lib/virtualbox/libGL.so.1: undefined symbol: _XGetRequest

  41. Zane says:

    Hi Ravi, could you explain me what’s the reason of the problem?

    • Ravi Saive says:

      Sorry bro, didn’t find any solution, even I am confuse why such error coming. It would be great if you could give me access to your machine via teamviewer.

Leave a Reply

This work is licensed under a (cc) BY-NC | TecMint uses cookies. By using our services, you comply to use of our cookies. More info: Privacy Policy.
© 2012-2014 All Rights Reserved.