[SOLVED] Virtualbox installation throws warnings, packages not in repo?
Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Virtualbox installation throws warnings, packages not in repo?
Hi, I'm migrating to a new computer, and installing Virtualbox. I opted to go for the version available on the website rather than repos. I install all, including dkms. On Virtualbox installation, I received the below message:
Code:
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.
There were problems setting up VirtualBox. To re-start the set-up process, run
/sbin/vboxconfig
as root.
Interestingly, Virtualbox DOES start (I haven't setup any OS yet, though). Is the issue possibly somehow due to UEFI? Any suggestions on how to fix this?
Resolved 2 of my own questions in 1 day, not bad ;-) For anyone else having this issue, my problem was UEFI. I disabled secure boot and I'm all good to go. Not the optimal solution, but at least this works - and necessary considering I fried the Windows partition on my Fedora 24 installation a few days ago. Also, in case anyone else is getting some errors first about needing to run sudo yum install kernel-core-devel-4.6.7-300.fc24.x86_64, it should just be sudo dnf kernel-devel, that's what you need. Virtualbox is specifying the wrong package name.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.