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

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

1 22 23 24 25 26 27
    1. Gracias, funciono perfecto

      Reply
    2. Excellent, very good Jr works very well in Fedora 29.

      Reply
    3. Thanks a lot. Your post saved me quite some time.

      Reply
    4. Hello,
      After following the above steps for Fedora 29 got the following:
      ARNING: The vboxdrv kernel module is not loaded. Either there is no module
      available for the current kernel (4.19.15-300.fc29.x86_64) or it failed to
      load. Please recompile the kernel module and install it by

      sudo /sbin/vboxconfig

      You will not be able to start VMs until this problem is fixed.
      [[email protected] ~]$ sudo /sbin/vboxconfig
      vboxdrv.sh: Stopping VirtualBox services.
      vboxdrv.sh: Starting VirtualBox services.
      vboxdrv.sh: Building VirtualBox kernel modules.
      vboxdrv.sh: failed: modprobe vboxdrv failed. Please use ‘dmesg’ to find out why.

      There were problems setting up VirtualBox. To re-start the set-up process, run
      /sbin/vboxconfig
      as root.
      The results of uname -r and rpm -qa | grep -i kernel-devel have shown both are the same version.
      Please, help out to resolve this.
      Best,

      Reply
      • Hello sean,

        Could you post output of following command:

        dnf list installed |grep -i virtualbox

        /sbin/vboxconfig is a wrong command, it should be /usr/lib/virtualbox/vboxdrv.sh setup.

        Reply
        • I’m having the same exact issue, and the output for dnf list installed |grep -i virtualbox is:
          VirtualBox-6.0.x86_64 6.0.4_128413_fedora29_1 @virtualbox
          virtualbox-guest-additions.x86_64 5.2.24-1.fc29 @updates

          any help would be greatly appreciated!

          Reply
          • Hi JL,

            What problem you mean exactly? I don’t know why you are running /sbin/vboxconfig command? Right command is /usr/lib/virtualbox/vboxdrv.sh setup.

            Reply
            • he JR
              i have the same problem and i have fedora 30
              i tried the last command like below
              # /usr/lib/virtualbox/vboxdrv.sh setup
              vboxdrv.sh: Stopping VirtualBox services.
              vboxdrv.sh: Starting VirtualBox services.
              vboxdrv.sh: Building VirtualBox kernel modules.
              This system is currently not set up to build kernel modules.
              Please install the Linux kernel “header” files matching the current kernel
              for adding new hardware support to the system.
              The distribution packages containing the headers are probably:
              kernel-devel kernel-devel-5.0.9-301.fc30.x86_64

              Reply
    5. I’ve followed the steps however as a Root i get the following:

      # /usr/lib/virtualbox/vboxdrv.sh setup
      vboxdrv.sh: Stopping VirtualBox services.
      vboxdrv.sh: Starting VirtualBox services.
      vboxdrv.sh: Building VirtualBox kernel modules.
      vboxdrv.sh: failed: modprobe vboxdrv failed. Please use ‘dmesg’ to find out why.

      Any idea?

      Reply
      • Hi Carrol,

        Could you post output of dmesg command when you run /usr/lib/virtualbox/vboxdrv.sh setup?

        Reply
        • Do you need whole file? I tried dmesg | grep vbox but return nothing… if you need whole file let me know. Thanks!

          Reply
    6. Muito obrigado pela ajuda.

      Reply
    7. [[email protected] ~]# dnf install VirtualBox-6.0
      [BFedora 29 [=== ] — B/s | 0 B –:– Fedora 29 – i386 – Virtua 0.0 B/s | 0 B 00:33
      Failed to synchronize cache for repo ‘virtualbox’, ignoring this repo.
      Last metadata expiration check: 0:02:18 ago on Thu 07 Feb 2019 01:36:51 GMT.
      No match for argument: VirtualBox-6.0
      Error: Unable to find a match

      Reply
      • Hello emma,

        Do you have working Internet connection? Or maybe Oracle’s site was down.

        Reply
    8. when ever i try to install virtualBox-6.0 i keep giving me [email protected] yum.repos.d]# dnf install VirtualBox-6.0
      Last metadata expiration check: 0:24:59 ago on Sun 10 Feb 2019 03:23:38 GMT.
      No match for argument: VirtualBox-6.0
      Error: Unable to find a match

      Reply
      • Hi emm,

        Did you downloaded repo file on step 2.?

        Could you post output of following command:

        dnf repolist
        Reply
        • I also have this issue.
          There’s no 6.0.
          Repolist:

          repo id repo name status
          base/7/x86_64 CentOS-7 – Base 10,097
          elrepo ELRepo.org Community Enterprise Linux Repository – el7 139
          epel/x86_64 Extra Packages for Enterprise Linux 7 – x86_64 13,517
          extras/7/x86_64 CentOS-7 – Extras 323
          packages-microsoft-com-mssql-server-rhel7 packages-microsoft-com-mssql-server-rhel7 24
          packages-microsoft-com-teams packages-microsoft-com-teams 10
          rpmfusion-free-updates/x86_64 RPM Fusion for EL 7 – Free – Updates 248
          tuxad/x86_64 Extra Packages for Enterprise Linux 7 – x86_64 2
          updates/7/x86_64 CentOS-7 – Updates 1,115
          repolist: 25,475

          Reply
          • Hi Frank,

            You don’t have virtualbox repo? Re-check step 2.

            Reply
    9. On my Fedora 28, I had to export the KERN_VER instead of KERN_DIR.

      export KERN_VER=4.20.11-100.fc28.x86_64

      Reply
    10. Thank you for this article, straight to the point.

      Reply
    11. icon missing on desktop

      Reply
    12. Thanks, all quite straightforward even for a casual user.

      Reply
    13. It doesn’t work on fedora 30, because drivers must be signed.

      Reply
      • Hi soho,

        It works, but you should disable secure boot from UEFI/BIOS.

        Reply
    14. Thanks a lot. replace command worked for me

      vb extpack install –replace Downloads/Oracle_VM_VirtualBox_Extension_Pack-6.0.10.vbox-extpack

      Oracle_VM_VirtualBox_Extension_Pack-6.0.12.vbox-extpack
      VirtualBox Extension Pack Personal Use and Evaluation License (PUEL)

      License version 10, 20 July 2017

      PLEASE READ THE FOLLOWING ORACLE VM VIRTUALBOX EXTENSION PACK PERSONAL
      USE AND EVALUATION LICENSE CAREFULLY BEFORE DOWNLOADING OR USING THE
      ORACLE SOFTWARE. THESE TERMS AND CONDITIONS CONSTITUTE A LEGAL AGREEMENT
      BETWEEN YOU AND ORACLE.

      Do you agree to these license terms and conditions (y/n)? y

      License accepted. For batch installation add
      –accept-license=56be48f9xxx
      to the VBoxManage command line.

      0%…10%…20%…30%…40%…50%…60%…70%…80%…90%…100%
      Successfully installed “Oracle VM VirtualBox Extension Pack”.

      Reply
    15. Hi!

      I have the problem

      /sbin/vboxconfig
      vboxdrv.sh: Stopping VirtualBox services.
      vboxdrv.sh: Starting VirtualBox services.
      vboxdrv.sh: You must sign these kernel modules before using VirtualBox:
      vboxdrv vboxnetflt vboxnetadp vboxpci
      See the documenatation for your Linux distribution..
      vboxdrv.sh: Building VirtualBox kernel modules.
      vboxdrv.sh: failed: modprobe vboxdrv failed. Please use ‘dmesg’ to find out why.

      There were problems setting up VirtualBox. To re-start the set-up process, run
      /sbin/vboxconfig
      as root. If your system is using EFI Secure Boot you may need to sign the
      kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load
      them. Please see your Linux system’s documentation for more information.

      Reply
1 22 23 24 25 26 27

Leave a Reply to Jim Raden 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