VIRTUALBOX INSTALLATION - 'modprobe vboxdrv failed' after trying to rebuild kernel modules

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
-1
down vote

favorite












I Have been trying to follow this guide: https://www.if-not-true-then-false.com/2010/install-virtualbox-with-yum-on-fedora-centos-red-hat-rhel/ on how to install VirtualBox 5.2 on Fedora 27. It all went pretty smooth until I used the command '/usr/lib/virtualbox/vboxdrv.sh setup' to rebuild the kernel modules. Below you can see that the problem lies on the last line:



 # /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.


vboxdrv.sh: failed: modprobe vboxdrv failed. makes it seem like there is some error. Does anybody know how to fix this and correctly finish the installation and everything?



I have been trying to install VirtualBox on Fedoracorrectly so that I don't get the well-known error rc=-1908 when I try to launch an OS in VirtualBox.







share|improve this question


















  • 2




    Please use 'dmesg' to find out why.
    – Axel Sommerfeldt
    Feb 18 at 21:25














up vote
-1
down vote

favorite












I Have been trying to follow this guide: https://www.if-not-true-then-false.com/2010/install-virtualbox-with-yum-on-fedora-centos-red-hat-rhel/ on how to install VirtualBox 5.2 on Fedora 27. It all went pretty smooth until I used the command '/usr/lib/virtualbox/vboxdrv.sh setup' to rebuild the kernel modules. Below you can see that the problem lies on the last line:



 # /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.


vboxdrv.sh: failed: modprobe vboxdrv failed. makes it seem like there is some error. Does anybody know how to fix this and correctly finish the installation and everything?



I have been trying to install VirtualBox on Fedoracorrectly so that I don't get the well-known error rc=-1908 when I try to launch an OS in VirtualBox.







share|improve this question


















  • 2




    Please use 'dmesg' to find out why.
    – Axel Sommerfeldt
    Feb 18 at 21:25












up vote
-1
down vote

favorite









up vote
-1
down vote

favorite











I Have been trying to follow this guide: https://www.if-not-true-then-false.com/2010/install-virtualbox-with-yum-on-fedora-centos-red-hat-rhel/ on how to install VirtualBox 5.2 on Fedora 27. It all went pretty smooth until I used the command '/usr/lib/virtualbox/vboxdrv.sh setup' to rebuild the kernel modules. Below you can see that the problem lies on the last line:



 # /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.


vboxdrv.sh: failed: modprobe vboxdrv failed. makes it seem like there is some error. Does anybody know how to fix this and correctly finish the installation and everything?



I have been trying to install VirtualBox on Fedoracorrectly so that I don't get the well-known error rc=-1908 when I try to launch an OS in VirtualBox.







share|improve this question














I Have been trying to follow this guide: https://www.if-not-true-then-false.com/2010/install-virtualbox-with-yum-on-fedora-centos-red-hat-rhel/ on how to install VirtualBox 5.2 on Fedora 27. It all went pretty smooth until I used the command '/usr/lib/virtualbox/vboxdrv.sh setup' to rebuild the kernel modules. Below you can see that the problem lies on the last line:



 # /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.


vboxdrv.sh: failed: modprobe vboxdrv failed. makes it seem like there is some error. Does anybody know how to fix this and correctly finish the installation and everything?



I have been trying to install VirtualBox on Fedoracorrectly so that I don't get the well-known error rc=-1908 when I try to launch an OS in VirtualBox.









share|improve this question













share|improve this question




share|improve this question








edited Aug 21 at 1:25









Rui F Ribeiro

34.9k1269113




34.9k1269113










asked Feb 17 at 16:28









user164324

11




11







  • 2




    Please use 'dmesg' to find out why.
    – Axel Sommerfeldt
    Feb 18 at 21:25












  • 2




    Please use 'dmesg' to find out why.
    – Axel Sommerfeldt
    Feb 18 at 21:25







2




2




Please use 'dmesg' to find out why.
– Axel Sommerfeldt
Feb 18 at 21:25




Please use 'dmesg' to find out why.
– Axel Sommerfeldt
Feb 18 at 21:25










1 Answer
1






active

oldest

votes

















up vote
1
down vote













Since the questioner only provided little useful information (no kernel version, no log file / dmesg, ...) I can only ask my cloudy crystal ball here.



It says: Since the installation of VirtualBox 5.2 on Fedora 27 is usually painless (and since the guides from If-not-true-than-false are usually fine), "Secure Boot" might be enabled in the UEFI/BIOS and is preventing the vboxdrv driver from loading.






share|improve this answer




















    Your Answer







    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "106"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    convertImagesToLinks: false,
    noModals: false,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );








     

    draft saved


    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f424827%2fvirtualbox-installation-modprobe-vboxdrv-failed-after-trying-to-rebuild-kern%23new-answer', 'question_page');

    );

    Post as a guest






























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    1
    down vote













    Since the questioner only provided little useful information (no kernel version, no log file / dmesg, ...) I can only ask my cloudy crystal ball here.



    It says: Since the installation of VirtualBox 5.2 on Fedora 27 is usually painless (and since the guides from If-not-true-than-false are usually fine), "Secure Boot" might be enabled in the UEFI/BIOS and is preventing the vboxdrv driver from loading.






    share|improve this answer
























      up vote
      1
      down vote













      Since the questioner only provided little useful information (no kernel version, no log file / dmesg, ...) I can only ask my cloudy crystal ball here.



      It says: Since the installation of VirtualBox 5.2 on Fedora 27 is usually painless (and since the guides from If-not-true-than-false are usually fine), "Secure Boot" might be enabled in the UEFI/BIOS and is preventing the vboxdrv driver from loading.






      share|improve this answer






















        up vote
        1
        down vote










        up vote
        1
        down vote









        Since the questioner only provided little useful information (no kernel version, no log file / dmesg, ...) I can only ask my cloudy crystal ball here.



        It says: Since the installation of VirtualBox 5.2 on Fedora 27 is usually painless (and since the guides from If-not-true-than-false are usually fine), "Secure Boot" might be enabled in the UEFI/BIOS and is preventing the vboxdrv driver from loading.






        share|improve this answer












        Since the questioner only provided little useful information (no kernel version, no log file / dmesg, ...) I can only ask my cloudy crystal ball here.



        It says: Since the installation of VirtualBox 5.2 on Fedora 27 is usually painless (and since the guides from If-not-true-than-false are usually fine), "Secure Boot" might be enabled in the UEFI/BIOS and is preventing the vboxdrv driver from loading.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Feb 22 at 8:50









        Axel Sommerfeldt

        1114




        1114






















             

            draft saved


            draft discarded


























             


            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f424827%2fvirtualbox-installation-modprobe-vboxdrv-failed-after-trying-to-rebuild-kern%23new-answer', 'question_page');

            );

            Post as a guest













































































            Popular posts from this blog

            How to check contact read email or not when send email to Individual?

            Bahrain

            Postfix configuration issue with fips on centos 7; mailgun relay