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

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 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: 15

1 13 14 15 16 17 27
    1. Hi.

      Nice howto.

      I am having the same problem as some of the people above. have tried to look trought your awnsers but I can’t fins what I have done wrong/missing.

      Have a newly installed fedora 20 (less than 1 day old).

      My problem:

      [[email protected] yum.repos.d]# /etc/init.d/vboxdrv setup
      Stopping VirtualBox kernel modules [ OK ]
      Uninstalling old VirtualBox DKMS kernel modules [ OK ]
      Trying to register the VirtualBox kernel modules using DKMS[ OK ]
      Starting VirtualBox kernel modules [MISSLYCKADES]
      (modprobe vboxdrv failed. Please use ‘dmesg’ to find out why)

      (MISSLYCKADES means failed in Swedish).

      Some output that you have requested before from others:

      [[email protected] yum.repos.d]# uname -a
      Linux localhost.localdomain 3.13.9-200.fc20.x86_64 #1 SMP Fri Apr 4 12:13:05 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

      [[email protected] yum.repos.d]# rpm -qa kernel |sort -V |tail -n 1

      [[email protected] yum.repos.d]# yum list installed |grep kernel |sort
      abrt-addon-kerneloops.x86_64 2.2.0-1.fc20 @updates
      kernel-devel.x86_64 3.13.9-200.fc20 @updates
      kernel-headers.x86_64 3.13.9-200.fc20 @updates
      kernel-modules-extra.x86_64 3.11.10-301.fc20 @koji-override-0/$releasever
      kernel-modules-extra.x86_64 3.13.9-200.fc20 @updates
      kernel.x86_64 3.11.10-301.fc20 @koji-override-0/$releasever
      kernel.x86_64 3.13.9-200.fc20 @updates

      dmesg and cpu info:


      Thanks in advanced.


      • Hi Krister,

        Thank you for nice initial info.

        Unfortunately I can’t download your dmesg.txt, because I can’t run that .exe and I don’t have premium account.

        Everything else looks very good.

        You can also try following as root and post output here:

        modprobe vboxdrv
    2. Hi.

      Thanks for getting back so soon.

      Funny that you cant download the dmesg.txt. Can’t you press the to link “download dmesg.txt”, something like that I have the Swedish translation. If you need it let me know than I will find some other way beside posting it here.

      The output that you requested:
      [[email protected] ~]# modprobe vboxdrv
      modprobe: ERROR: could not insert ‘vboxdrv’: Required key not available

      • Hi Krister,

        Actually I don’t need that dmesg file anymore. Reason why modprobe vboxdrv fails is secure boot. You can check my earlier comment about VirtualBox and secure boot.

        So go to bios and disable secure boot and then run setup again. If you still have problems, please let me know.

    3. Works perfectly, thank you.


      • Excellent to hear that you got it working!

    4. fedora has a new kernel, i got error: Your kernel headers for kernel 3.13.9-200.fc20.x86_64 cannot be found at
      /lib/modules/3.13.9-200.fc20.x86_64/build or /lib/modules/3.13.9-200.fc20.x86_64/source.

      • Hi Fabse,

        Did you updated also kernel-headers and kernel-devel packages?

        Could you post output of following commands:

        uname -a
        rpm -qa kernel\* |sort -V
    5. There is a much easier way to install programs to newest versions of Fedora by using “Yumex”

      • Hi cito,

        First you have to of course install Yumex. And quick look shows that the VirtualBox is not even available if you install just Yumex or am I wrong?

        It’s nice that there is alternatives, like Yumex, but for me yum and PackageKit is enough…

    6. No package VirtualBox-4.3 available. Any ideas?

    7. if you run into erros during /etc/init.d/vboxdrv setup

      then do

      uname -r

      to get the kernel version. and do

      yum install kernel-devel-{ouput from uname -r}

      you should be all set after that..atleast for me on F19

      • Thanks Praveen – that was the ticket for my KERN_DIR errors. That and installing GCC compiler

    8. I have a linode VPS and I’m getting this error:

      Trying to register the VirtualBox kernel modules using DKMSError! echo
      Your kernel headers for kernel 3.14.4-x86_64-linode40 cannot be found at
      /lib/modules/3.14.4-x86_64-linode40/build or /lib/modules/3.14.4-x86_64-linode40/source.
      (Failed, trying without DKMS)
      Recompiling VirtualBox kernel modules [FAILED]

      any way for me to get those kernel modules manually installed?

      • Hi jcy,

        All (old discussions) what I found from the Internet about Linode kernel packages was that, they do not ship any kernel-headers or kernel-devel packages. But their xen kernels are vanilla kernels and it’s possible to build those packages yourself. I really can’t say that they use vanilla kernels nowadays.

        Linode have excellent support, so maybe you could ask directly from Linode support if they have kernel-headers and kernel-devel packages available for your kernel.

    9. Hi,

      I followed your tutorial for installing virtualbox on my centos machine.(it is the first link on google search).

      After importing my vm I saw that it allows me to allocate only 4GB ram from the 32 GB I have on my host system. The EPEL repositories you have mentioned are both for 32 bit hosts, but they works on 64 bit hosts anyways. Since most of the systems now are 64 bit, and many people will come to this link and follow the installation instructions as such, it would be awesome if you could modify this page and add instructions for 64bit hosts wherever applicable.

      • Hi Akshay,

        This EPEL package is noarch package so it doesn’t make any difference if you install x86_64 package, try following:

        wget -O epel-i386.rpm
        wget -O epel-x86_64.rpm
        md5sum epel-*


        2cd0ae668a585a14e07c2ea4f264d79b  epel-i386.rpm
        2cd0ae668a585a14e07c2ea4f264d79b  epel-x86_64.rpm

        Exactly same package. Arch is determined in repo file. That’s why I have mentioned only 32-bit url, but you can of course download exactly same file from x86_64 url too (if you want). So this guide is totally 64-bit compatible.

        I just tested this on 64-bit Fedora and I can allocate more than 4GB ram.

        Could you first post output of following command:

        uname -a
    10. Next time be sure to use

    11. Virtualbox only run as root
      But can’t run as user.

      Message :

      Failed to create the VirtualBox COM object.

      The application will now terminate.

      Callee RC: NS_BASE_STREAM_WOULD_BLOCK (0x80470007)

      • Hi Ruben,

        Could you first change normal user and post output of following commnand:

    12. Hi,
      I’ve upgraded my system to Fedora 21, and I try to install Virtualbox using the method above, but it doesn’t work :(
      I am unable to use VBox on F21 which is a very bad thing :(
      Could you help me how to install VBox on F21?

      • Hi VChris,

        You could use Fedora 20 VirtualBox on Fedora 21, but you have to modify your /etc/yum.repos.d/virtualbox.repo file looks like following:

        name=Fedora 20 - $basearch - VirtualBox

        I use this on Fedora Rawhide (Fedora 22), so it should work also on Fedora 21. I update this guide, when official VirtualBox Fedora 21 exists.

        Please let me know do you get it working or if you have some problems.

        • Thanks for your reply, it works :)

          • Excellent! You are welcome! :)

        • I don’t feel comfortable using the “old” 20 link for a 21 installation. Can’t this lead to dependency conflicts or other unwanted behavior? I guess the guys at Oracle will soon provide a 21 repo. I hope…

          • Hi Nick,

            Actually VirtualBox packages looks exactly same for Fedora 18, Fedora 19 and Fedora 20 (I guess that F19 and F20 are just symlinks to F18 builds). I didn’t checked md5sums, but I have personally used just latest available version on rawhide very long time without any problems.

            Of course this might lead some problems, but if you need VirtualBox now, then this one way to install it. And when Oracle releases Fedora 21 repo, then you could change repo file back to normal without hardcoded parts.

            But I hope too that Oracle releases Fedora 21 repo soon.

          • Hi Nick and VChris,

            Now VirtualBox Fedora 21 repo is available. :) I updated this guide too.

            • Awesome, thanks for the info! :)

            • Thanks for the good news :)

    13. Hi,

      I followed the steps without any problem, but when I try to run VirtualBox I get a message saying

      Failed to create the VirtualBox COM object
      The application will now terminate
      Callee RC: NS_ERROR_FACTORY_NOT_REGISTERED (0x80040154)

      Any ideas on how to fix this?

      Thanks a lot for your help

      • Hi Franz,

        This sounds like a problem with permissions.

        Did you add your user to vboxusers group on step 6.?

        Could you try to start VirtualBox from command line to see more information about the error?

        • Hi Jr,

          thanks foor your reply. In fact it was a permission issue with the /tmp folder and some leftovers in the /tmp folders from a previous VB installation which I removed. All is working now.

          drwxrwxrwt. 11 root root 20480 Jan 16 10:14 tmp

          Thank You

          • Thanks a lot! I was experiencing the same issue, blowing away the contents of /tmp/.vbox* sorted the issue out for me

      • Hi Anon,

        Did you installed dependencies on step 4.?

        Following packages should be installed:

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

        So kernel-devel package should be also installed after step 4.

    14. Hey, all went very smooth, but VB crash as click as soon as selection option :(

      • Hi Gurpreet,

        Could you start VirtualBox from command line and check output when it crash.

        Could you also post output of following command:

        uname -a
1 13 14 15 16 17 27

Leave a Reply to Consuelo 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.