VirtualBox 5.2 on Fedora 28/27, CentOS/RHEL 7.5/6.9 - Comment Page: 22

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. VirtualBox supports a large number of guest operating systems: [inttf_post_ad1] Windows 3.x Windows NT 4.0 Windows 2000 Windows XP Windows Server 2003 Windows Server 2008 Windows Vista Windows 7 Windows 8 Windows 8.1 Windows 10 DOS Linux (Kernel 2.4, 2.6, 3.0, 3.2, 3.4, 3.10, 3.16, 3.18, 4.1, 4.4, 4.7, 4.8, 4.9, 4.10, 4.11, 4.12, 4.13, 4.14, 4.15,...

698 comments on “VirtualBox 5.2 on Fedora 28/27, CentOS/RHEL 7.5/6.9 - Comment Page: 22

1 20 21 22 23
    1. KERN_VER sometimes is needed

      Reply
    2. Excellent guide , got the application install in no time.
      thanks

      Reply
    3. vboxdrv.sh: failed: modprobe vboxdrv failed. Please use ‘dmesg’ to find out why
      ths msg pops when i re configure the kernel. please help it is still a problem for me

      Reply
      • Hello Akshat,

        Do you see anything interesting on your dmesg output?

        What distro you use and is it fully updated?

        Reply
    4. Works like a charm!
      Thank you very much!

      Reply
    5. Great Info!!
      I’ve been trying make work VirtualBox for my Laravel project with Vagrant loosing a lot of time looking for a solution, and all the problem seemed to be a bad installation of VirtualBox. Fortunately I found this tutorial that solved my problems. Thank you very much!

      Reply
    6. It might be worth mentioning that “Secure Boot” needs to be disabled in the UEFI/BIOS setup, otherwise it prevents the VirtualBox kernel driver (vboxdrv) from loading.

      Reply
    7. Thanks, very useful.

      Reply
    8. thank you very much for sharing!

      Reply
    9. There should be a way to run /usr/lib/virtualbox/vboxdrv.sh setup on upgrade of virtualbox and or kernel.

      Also there should be a way to have it save each machines state stop them and update virtualbox and restore all the machines that where running.

      I’ll work on scripts to do that but they ought to exist already.

      Reply
    10. hi. everything went fine but i got an error when i executed /usr/lib/virtualbox/vboxdrv.sh setup

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

      i’m using fedora workstation 27 kernel-4.15.9-300.fc27.x86_64

      Reply
      • Hi anj,

        What shows your dmesg command after failed build? I tested this just with kernel 4.15.10 and VirtuaBox 5.2.8 and it’s working normally for me.

        Reply
    11. step 5:
      $ /usr/lib/virtualbox/vboxdrv.sh setup
      vboxdrv.sh: Stopping VirtualBox services.
      /usr/lib/virtualbox/vboxdrv.sh: строка 205: /etc/udev/rules.d/60-vboxdrv.rules: Permission denied
      vboxdrv.sh: Building VirtualBox kernel modules.
      /usr/lib/virtualbox/vboxdrv.sh: строка 401: /var/log/vbox-install.log: Permission denied
      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.

      Reply
      • Hi Stas,

        Did you run this /usr/lib/virtualbox/vboxdrv.sh setup command as root user?

        Reply
    12. In fedora 27 with uefi boot you have to sign the modules with your Machine Owner Key. I followed something like this for the MOK creation: https://gist.github.com/gabrieljcs/68939c7eeadfabfdbc6b40100130270d

      And then run this (after having vboxdrv setup failing in modprobe vboxdrv):

      for A in $(dirname $(modinfo -n vboxdrv))/*.ko; do
      /usr/src/kernels/$(uname -r)/scripts/sign-file sha256 /root/MOK.priv /root/MOK.der “$A”
      done

      Reply
      • Hi Luca Gervasi,

        Alternatively you can disable secure boot from UEFI.

        Reply
    13. On Fedora 28 the repository cannot load and the system deactivate it…

      What happened?

      Reply
      • Hi Miguel,

        There is not Fedora 28 repo yet, you can use Fedora 27 version until Oracle releases Fedora 28 repo.

        Reply
1 20 21 22 23

Leave a 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