VirtualBox 6.1.28 / 6.1.29 on Fedora 35/34/33, CentOS/RHEL 8/7 - Comment Page: 26
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...
Success!! Virtualbox on Fedora 33! Thank you so much!
I guess when Oracle officially releases the F33 rpm, I just need to do a usual yum update? Thank you!
Excellent!
You will need also repo file and then normal dnf/yum update should do the trick when next version is available. Check step 2.2., but you can’t install it yet, because Fedora 33 repo doesn’t exists.
Thanks a lot! I depend on VirtualBox on a daily basis for work, and after upgrading to F33 I could not run it anymore until an official package was released. Your tips just provided me the workaround I needed =)
Hello Andre,
Excellent! Nice to hear that this helped you. Later you can use official repos and upgrade this version.
Fantastic and complete!
Thanks!
You are a hero bro!
Thanks a lot it was really helpful
Hoi,
on your current guide you mention to install the package VirtualBox-6.1 and not VirtualBox.
Could you please explain where the difference is and why you are using VirtualBox-6.1 instead of VirtualBox?
When I would install with:
“dnf install VirtualBox” it would install in addition “VirtualBox-kmodsrc”, “VirtualBox-server” and “akmod-VirtualBox”. These packages are not listed in your guide, do I not need them?
Kind regards :)
Hoi,
on your current guide you mention to install the package VirtualBox-6.1 and not VirtualBox.
Could you please explain where the difference is and why you are using VirtualBox-6.1 instead of VirtualBox?
When I would install with:
“dnf install VirtualBox” it would install in addition “VirtualBox-kmodsrc”, “VirtualBox-server” and “akmod-VirtualBox”. These packages are not listed in your guide, do I not need them?
Kind regards :)
Sorry if that message comes twice, after first pressing “Post Comment” came a 504 gateway timeout…
Hello Woraz,
VirtualBox-6.1 is from Oracle’s own repo and VirtualBox from RPMFusion repo. Both should work, but as you might guess, Oracle’s own repo is always updated earlier, when they release new version.
followed procedure on fedora 33. upon launching virtualbox and attempting to add an iso only 32-bit versions were listed within virtualbox as possible guest systems
Hello ahd,
Please check your BIOS/UEFI that you have all virtualization settings enabled.
yes, that did the trick. thanks very much.
Always saving my life!!. Thank you for share!
This works, thanks!
It did *not* work for me on a Fedora 33 host logged into Gnome on Wayland, but it *does* work if I log into Gnome on XOrg.
The guest in both cases was current (Nov ’20) Manjaro.
Hello Jim,
What you get if you start VirtualBox from command line (on Wayland)? And any error on dmesg?
Thanks for the tutorial, I have successfully installed virtualbox on fedora 33, and it seems that the enhancements are not working!
Do you mean extension pack or guest additions? Guest additions install guide is here: https://www.if-not-true-then-false.com/2010/install-virtualbox-guest-additions-on-fedora-centos-red-hat-rhel/ and you can download extension pack from here.
After installing on Fedora 33 you have to create signing keys and then sign the kernel modules :
openssl req -new -x509 -newkey rsa:2048 -keyout MOK.priv -outform DER -out MOK.der -nodes -days 36500 -subj “/CN=VBOX/”
sudo /usr/src/kernels/`uname -r`/scripts/sign-file sha256 ./MOK.priv ./MOK.der $(modinfo -n vboxdrv)
sudo /usr/src/kernels/`uname -r`/scripts/sign-file sha256 ./MOK.priv ./MOK.der $(modinfo -n vboxnetadp)
sudo /usr/src/kernels/`uname -r`/scripts/sign-file sha256 ./MOK.priv ./MOK.der $(modinfo -n vboxnetflt)
Hello Ghostdog,
You have to sign your modules, only if you have secure boot enabled on BIOS/UEFI.
With secure boot enabled you have to sign all your kernel modules, not only VirtualBox modules.
What is Secure boot?
Secure boot is a setup using UEFI firmware to check cryptographic signatures on the boot-loader and associated OS kernel to ensure they have not been tampered with or bypassed in the boot process. Secure boot activates a lock-down mode in the Linux kernel which disables various features kernel functionality:
Loading kernel modules that are not signed by a trusted key.
Using kexec to load an unsigned kernel image.
Hibernation and resume from hibernation.
User-space access to physical memory and I/O ports.
Module parameters that allow setting memory and I/O port addresses.
Writing to MSRs through /dev/cpu/*/msr.
Use of custom ACPI methods and tables.
You will miss also many Linux kernel features, if you have secure boot enabled.
Afetr dnf install ~/rpmbuild/RPMS/x86_64/VirtualBox-6.1-6.1.16_140961_fedora33-1.x86_64.rpm
I get an error saying package not signed. Error: GPG check failed….
Hello David,
Maybe this come from VirtualBox repo, try:
Or disable VirtualBox repo.
Thank you so much! Your guide worked flawlessly for my upgrade to Fedora 33 this evening.
Thanks for share!! It worked on Fedora 33.
This guide worked like a charm. Thank you very much. I have installed virtual box. I have not yet created or imported any VMs though, but it looks promising.