VirtualBox 6.1.28 / 6.1.29 on Fedora 35/34/33, CentOS/RHEL 8/7 - Comment Page: 4

Oracle VirtualBox is a powerful x86 and AMD64/Intel64 virtualization product for enterprise as well as home use. VirtualBox is a general-purpose full virtualizer for x86 hardware. Targeted at server, desktop and embedded use, it is now the only professional-quality virtualization solution that is also Open Source Software. Check video guide howto install VirtualBox 6.1.28/6.1.29 on Fedora 35/34/33 using .run installer: Check video guide howto install VirtualBox 6.1.28 on Fedora 34/33 using Oracle's own dnf repo: Watch More Videos and Subscribe to if-not-true-then-false.com Youtube Channel VirtualBox supports a large number of guest operating...

810 comments on “VirtualBox 6.1.28 / 6.1.29 on Fedora 35/34/33, CentOS/RHEL 8/7 - Comment Page: 4

1 2 3 4 5 6 27
    1. Wow ! this is awesome.! worked perfectly on my centos 5.6

      Reply
    2. I successfully installed and run VirtualBox on fedora 14, but i notice an error while shutting down my machine, the error said panic occurred switching back text to console. Google cant answer my query so I decided to put it here. Thanks in Advance ^_^

      Reply
    3. thanks for this stuff JR, it works. but when im going to shut down my fedora machine, i got an error near shutdown, last line is panic occurred switching back text to console.

      Reply
      • Hi openx,

        Do you get that error on virtual machine or your host machine?

        Reply
    4. Hi. I am trying to install virtualbox-4.1 on ubuntu 11.04.
      I actually updated my previous version of ubuntu to this.

      When i try to open my virtualbox-4.1. I am get the following error.

      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. Users of Ubuntu, Fedora or Mandriva should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary.

      when i give ‘/etc/init.d/vboxdrv setup’ as a root it shows error like this.

      [email protected]:/home/karthick_sj88# /etc/init.d/vboxdrv setup
      * Stopping VirtualBox kernel modules * done.
      * Uninstalling old VirtualBox DKMS kernel modules * done.
      * Trying to register the VirtualBox kernel modules using DKMS
      Error! Bad return status for module build on kernel: 2.6.38-10-generic (i686)
      Consult the make.log in the build directory
      /var/lib/dkms/vboxhost/4.0.0/build/ for more information.

      * Failed, trying without DKMS
      * Recompiling VirtualBox kernel modules
      * Look at /var/log/vbox-install.log to find out what went wrong

      I also installed dkms and it is up to date. But still i am facing that error. Here is the vbox-install.log

      Uninstalling modules from DKMS
      removing old DKMS module vboxhost version 4.0.0

      ——————————
      Deleting module version: 4.0.0
      completely from the DKMS tree.
      ——————————
      Done.
      Attempting to install using DKMS

      Creating symlink /var/lib/dkms/vboxhost/4.0.0/source ->
      /usr/src/vboxhost-4.0.0

      DKMS: add Completed.

      Kernel preparation unnecessary for this kernel. Skipping…

      Building module:
      cleaning build area….
      make KERNELRELEASE=2.6.38-10-generic -C /lib/modules/2.6.38-10-generic/build M=/var/lib/dkms/vboxhost/4.0.0/build….(bad exit status: 2)
      0
      0
      Failed to install using DKMS, attempting to install without
      Makefile:185: *** Error: KERN_DIR does not point to a directory. Stop.

      Thanks in advance

      Reply
    5. Thanks for the info.

      With Virtual Box 4.1, setting KERN_DIR isn’t sufficient. Your KERN_DIR actually has to be:

      ## Current running kernel on CentOS and Red Hat (RHEL) ##
      KERN_DIR=/usr/src/kernels/`uname -r`-`uname -m`

      This isn’t what the devel packages install (at least, this isn’t what I have, and I don’t think I renamed them). The devel pacakge had /usr/src/kernels/2.6.18-194.26.1.el5-x86_64. Once I created KERN_DIR with the uname chant, above, and added a symlink /usr/src/kernels/2.6.18-194.el5-x86_64, the Guest Additions installer was happy. Prior to that, it kept telling me that KERN_DIR was not a directory.

      I’m 99% sure I exported KERN_DIR in both scenarios; so it is possible that 4.1.0 VBox doesn’t honor KERN_DIR on CentOS anymore, it generates it internally (and never tells you what it is looking for). Your post saved me the trouble of digging through their shell script. Thanks!

      Reply
      • Hello,

        I am having problem installing VB4.1.x on OEL 5.6.

        I followed the instructions on this blog to update the packages. ie

        —————————————————————————————————-

        [[email protected] kernels]# yum update kernel kernel-devel kernel-headers
        Loaded plugins: rhnplugin, security
        This system is not registered with ULN.
        ULN support will be disabled.
        Skipping security plugin, no data
        Setting up Update Process
        No Packages marked for Update
        [[email protected] kernels]#

        ________________________________________

        then I tried to do the installation and this error comes up…

        ___________________________________________________________________
        Makefile:172: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DI
        R= and run Make again. Stop.
        ____________________________________________________________________

        so I set my KERN_DIR variable to

        [[email protected] kernels]# export KERN_DIR=/usr/src/kernels/`uname -r`-`uname -m`
        [[email protected] kernels]# echo $KERN_DIR
        /usr/src/kernels/2.6.32-100.26.2.el5-x86_64
        [[email protected] kernels]#

        when I cd to

        [[email protected] kernels]# ls -l
        total 16
        drwxr-xr-x 19 root root 4096 Sep 18 21:25 2.6.18-238.el5-x86_64
        drwxr-xr-x 19 root root 4096 Sep 18 21:45 2.6.18-238.el5-xen-x86_64
        lrwxrwxrwx 1 root root 25 Sep 18 21:45 2.6.18-238.el5xen-x86_64 -> 2.6.18-238.el5-xen-x86_64

        there is directory with 100 in it for my current version of uname -r
        that is
        [[email protected] tmp]# uname -r
        2.6.32-100.26.2.el5

        Any advice will be much appreciated as I am stuck here….

        Reply
        • Hi Rajesh,

          Could you post following info:

          
          yum info kernel kernel-devel kernel-headers
          
          Reply
    6. Hi JR A couple of months back i followed ur how-to and installed VB 4.1.
      Now i want to upgrade to 4.1.4.
      simple “yum update Virtualbox” is enough for this????
      And one more issue i am facing is if i keep open VB machine for some time on my centos 5.6 it is having some memory leak.
      To get the centos login window i have to kill VB processes running.
      If not i cant see any login screen to type my centos password.
      Can u please help me on this.

      Reply
      • Hi revo,

        Updating should be easy…you can use following command if you have VB-4.1 installed:

        
        yum update VirtualBox-4.1
        

        And if you have VB-4.0 installed then run:

        
        yum install VirtualBox-4.1
        

        You might to need to run also following command with working KERN_DIR:

        
        /etc/init.d/vboxdrv setup
        

        Memory leak issues is bit more problematic, but you can try this VirtualBox 4.1.4 version and check what happens with it?

        Reply
        • Hi JR
          i updated my virtual box using yum update VirtualBox-4.1. And ran setup also.
          And this time no memory leaks . It is saying that usb accessibility is not possible. And asking to add user to vboxusers for enabling. How to do this???
          Thanks.

          Reply
          • Hi revo,

            Excellent to hear that memory leaks problems are solved. :)

            You can add your user to vboxusers with following command:

            
            usermod -a -G vboxusers user_name
            
            ## Real example ##
            usermod -a -G vboxusers revo
            
            Reply
    7. Hello JR,
      Can’t get the box working. Help needed please…
      I have gnome (centos 5.4) running on a clearos system.
      can’t install vmbox 3.1 on centos 5.4
      [[email protected] yum.repos.d]# /etc/init.d/vboxdrv setup
      Stopping VirtualBox kernel module [ OK ]
      Recompiling VirtualBox kernel module [MISLUKT]
      (Look at /var/log/vbox-install.log to find out what went wrong)
      Makefile:152: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR= and run Make again

      Installed Packages
      kernel-PAE.i686 2.6.18-194.8.1.v5 installed
      kernel-devel.i686 2.6.18-194.8.1.v5 installed
      kernel-devel.i686 2.6.18-274.3.1.el5 installed
      kernel-headers.i386 2.6.18-274.3.1.el5 installed
      php.i386 5.1.6-27.v5.3.1 installed
      php-cli.i386 5.1.6-27.v5.3.1 installed
      php-common.i386 5.1.6-27.v5.3.1 installed
      php-imap.i386 5.1.6-27.v5.3.1 installed
      php-kolab.noarch 2.2.0-3.2.v5 installed
      php-ldap.i386 5.1.6-27.v5.3.1 installed
      php-mbstring.i386 5.1.6-27.v5.3.1 installed
      php-mysql.i386 5.1.6-27.v5.3.1 installed
      php-pdo.i386 5.1.6-27.v5.3.1 installed
      phpMyAdmin.noarch 3.2.3-1.1.v5 installed
      phpsysinfo.noarch 2.5.4-4.2.v5 installed

      Can you help me?

      Reply
      • Hi hoek,

        Did you set KERN_DIR variable and exported it?

        Reply
    8. […] Thats it simple right here is the original source click here […]

      Reply
      • Hi Greg,

        Thanks for note.

        I actually fixed this part of guide to working directly also with CentOS 6 and Red Hat (RHEL) 6.

        Now if you use:

        
        wget http://download.virtualbox.org/virtualbox/rpm/rhel/virtualbox.repo
        

        It should work normally with CentOS 6/5.6 and Red Hat (RHEL) 6/5.6. :)

        Reply
    9. If anyone is interested these are the steps I followed to install VirtualBox 4.1 on a clean installation of Oracle 64bit Enterprise Linux 5.7

      — Install Enterprise Linux

      — Register on Linux Network
      rpm –import /usr/share/rhn/RPM-GPG-KEY
      up2date-nox –register

      — Register to following channels on Linux Network
      Enterprise Linux 5 Add ons (x86_64)
      Enterprise Linux 5 Latest (x86_64)
      Oracle Software for Enterprise Linux 5 (x86_64)
      Oracle Linux 5 Latest (x86_64)

      — To install DKMS — Extra Packages for Enterprise Linux (EPEL) v5
      rpm -Uvh http://download.fedora.redhat.com/pub/epel/5/x86_64/epel-release-5-4.noarch.rpm

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

      cd /etc/yum.repos.d/
      wget http://download.virtualbox.org/virtualbox/rpm/rhel/virtualbox.repo
      yum install VirtualBox-4.1

      shutdown -r now

      — Re-Setup the kernel module by
      /etc/init.d/vboxdrv setup — as root

      — FINISHED

      Reply
      • Hi Mark,

        Thank you very much! This is excellent guide, I think I have to improve mine with some things… :)

        Reply
    10. Well, the guide is excellent, but there is something wrong with the yum guys: ALL THESE commands, steps and decisions should do it automatically by typing “yum install -y virtualbox”! If not, what is the sense of yum??

      Reply
    11. Just to say thanks! worked great – Fedora 16 – Virtualbox 4.1.6. Reboot is a must people!! mine only sorted the kernel after that! Cheers again!

      Reply
    12. Thanks for the guide!

      FYI,

      I know you don’t talk about installing the extension packs here but I thought it would be relevant to post my issue/solution. I had an issue installing the extension pack on F16x86. Turns out that there is an issue with bash (see: http://fedoraforum.org/forum/showthread.php?t=272450). So when installing the extension pack, VirtualBox gives some cryptic error about no shell something or other.

      The solution is to run:

      yum reinstall bash

      Then try reinstalling the extension pack.

      Reply
      • I had the same issue (F16 x86_64) and can confirm that this worked for me.. :)

        Reply
1 2 3 4 5 6 27

Leave a Reply to Thomas Tessier Cancel reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Close