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

Multi tool use
Multi tool use

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.




fedora virtualbox kernel-modules




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.




fedora virtualbox kernel-modules




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.




fedora virtualbox kernel-modules




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.





fedora virtualbox kernel-modules





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
































































            mMLDH,e0jVSwZQr2LZw,qjjfvXo2CYLj0mB3u
            -
            p,fQNQbwx 1fbztwBz6byTiJnMrG C Cje75 Nr

            Popular posts from this blog

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

            Image
            Clash Royale CLAN TAG #URR8PPP up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this question asked Sep 26 at 0:12 ToanLuong 49 9 add a comment  |  up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this questi...
            Read more

            How many registers does an x86_64 CPU actually have?

            Image
            Clash Royale CLAN TAG #URR8PPP up vote 2 down vote favorite I am currently learning reverse engineering and am studying the flags register. I had in my mind that rflags was just another name for one of the 16 general purpose registers, for example rax or rbx . But it looks like rflags is actually an additional register. So that makes 17 registers in total... how many more could there be? I have spent at least an hour on this and found numerous different answers. The best answer so far is this, which says that there are 40 registers in total. 16 General Purpose Registers 2 Status Registers 6 Code Segment Registers 16 SSE Registers 8 FPU/MMX Registers But if I add that up, I get 48. Could anybody provide an official answer on how many registers an x86_64 CPU has (e.g. an Intel i7). Additionally, I have seen references to 'hardware' and 'architectural' registers. What are those registers and how many are there? register x86-64 share | improve this...
            Read more

            Displaying single band from multi-band raster using QGIS

            Image
            Clash Royale CLAN TAG #URR8PPP 1 How can I extract a single band from multi-band raster in QGIS? I have an remote sensed image which has 6 bands (including NDVI band), I want to display each band separately, but have no idea how to do. I have seen some questions similar here but none worked for me. The original image (has 6 bands) is: I want to display the band 6 which should be like this: But I tried gdal_translate, and couldn't get the correct result. What I have got is: qgis raster multi-band share | improve this question edited Mar 5 at 0:53 Summer asked Mar 4 at 6:42 Summer Summer 23 6 Is this any help gis.stackexchange.com/questions/220658/… ? if not gis.stackexchange.com/questions/62133/… might help. – Michael Stimson Mar 4 at 6:46 Thanks for answering but when I used gdal_translate, qgis showed that 'Error 4: Kayena.tif: No such file or directory". Would you know how to fi...
            Read more