VirtualBox 6.1.28 / 6.1.29 on Fedora 35/34/33, CentOS/RHEL 8/7 - Comment Page: 16
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...
Thanks very much for this guide. It worked fine to install VB, but I’m having trouble accessing a physical drive, using the instructions I found here. It’s NTFS, and when I try to load the vmdk file for it, I get a permissions problem.
Failed to open the hard disk file /home/USER_NAME/VirtualBox VMs/Windows 8.1/VirtualBox\ VMs\ Windows\ 8.1.vmdk.
Permission problem accessing the file for the medium ‘/home/pat/VirtualBox VMs/Windows 8.1/VirtualBox\ VMs\ Windows\ 8.1.vmdk’ (VERR_ACCESS_DENIED).
Result Code: VBOX_E_FILE_ERROR (0x80BB0004)
Component: Medium
Interface: IMedium {05f2bbb6-a3a6-4fb9-9b49-6d0dda7142ac}
Callee: IVirtualBox {fafa4e17-1ee2-4905-a10e-fe7c18bf5554}
Callee RC: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)
I’m running VB as a user, but a user doesn’t have permission to do a disk mount (also, the drive itself, when I mount it as root, shows it owned and grouped as root, probably because it’s NTFS). Any suggestions?
Hi Rand Simberg,
You could try add your user to disk group:
That did the trick, thanks!
OK, I’ve set it up on a different machine, and am trying to access a physical SSD. I’m getting the same error again:
Failed to open the hard disk file /home/simberg/VirtualBox VMs/Ubuntu.vmdk.
Permission problem accessing the file for the medium ‘/home/simberg/VirtualBox VMs/Ubuntu.vmdk’ (VERR_ACCESS_DENIED).
Result Code: VBOX_E_FILE_ERROR (0x80BB0004)
Component: Medium
Interface: IMedium {05f2bbb6-a3a6-4fb9-9b49-6d0dda7142ac}
Callee: IVirtualBox {fafa4e17-1ee2-4905-a10e-fe7c18bf5554}
Callee RC: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)
I’ve added myself to the “disk” group, but no joy this time.
Hi, im using: CentOS Linux release 7.0.1406 (Core).
64 bits
I’m getting:
Trying to register the VirtualBox kernel modules using DKMSError! echo
Your kernel headers for kernel 3.10.23-xxxx-std-ipv6-64 cannot be found at
/lib/modules/3.10.23-xxxx-std-ipv6-64/build or /lib/modules/3.10.23-xxxx-std-ipv6-64/source.
[FAILED]
(Failed, trying without DKMS)
Recompiling VirtualBox kernel modules [FAILED]
(Look at /var/log/vbox-install.log to find out what went wrong)
/var/log/vbox-install.log:
Uninstalling modules from DKMS
removing old DKMS module vboxhost version 4.3.26
——————————
Deleting module version: 4.3.26
completely from the DKMS tree.
——————————
Done.
Attempting to install using DKMS
Creating symlink /var/lib/dkms/vboxhost/4.3.26/source ->
/usr/src/vboxhost-4.3.26
DKMS: add completed.
Failed to install using DKMS, attempting to install without
Makefile:183: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR= and run Make again. Stop.
I’ve already did:
## Current running kernel on CentOS and Red Hat (RHEL) ##
KERN_DIR=/usr/src/kernels/`uname -r`-`uname -m`
## Export KERN_DIR ##
export KERN_DIR
But it isn’t worked =(
And:
rpm -qa kernel |sort -V |tail -n 1 = kernel-3.10.0-123.20.1.el7.x86_64
uname -r = 3.10.23-xxxx-std-ipv6-64
It isn’t match :P
I’ve already used reboot
But the same.
How to fix it, please?
Thank you!
Hi Diego,
Are you working on some virtual environment?
Looks like that you are running kernel 3.10.23-xxxx-std-ipv6-64 and your installed kernel packages are kernel-3.10.0-123.20.1.
So you need 3.10.23-xxxx-std-ipv6-64 kernel-devel and kernel-headers to get it working.
Hi!
You are right!
My dedicated hosts install a custom kernel (3.10.23-xxxx-std-ipv6-64) =P That cannot be found by yum.
So i had to edit my grub2 conf to start the centos with the right original kernel (kernel-3.10.0-123.20.1.el7.x86_64)
I correct this error and get another: Port forward doesn’t works =P I tried to access apache in vm from internet but its not worked =(
Btw, thank you very much for your guide and help :D
Just a tip I was having issues installing this on Fedora 21 where it failed on the ‘vboxdrv setup’ step
[[email protected]]# /etc/init.d/vboxdrv setup
Stopping VirtualBox kernel modules [ OK ]
Uninstalling old VirtualBox DKMS kernel modules [ OK ]
Trying to register the VirtualBox kernel modules using DKMS[ OK ]
Starting VirtualBox kernel modules [FAILED]
(modprobe vboxdrv failed. Please use ‘dmesg’ to find out why)
dmesg had nothing useful in it.
Turns out it was secure boot in the BIOS which had to be turned off for the above command to work.
This can be done by entering the BIOS when booting the computer. Go to the “security” tab and modify the secure boot status from “enabled” to “disabled”.
Then it all works like a charm. Thanks for the howto it got me most of the way.
This has been kicking my butt…. Thank you. Secure boot disabled worked like a charm.
Never mind, I figure out the problem. I changed ownership of the device to the user, and it worked.
Hello, I have been having trouble getting VirtualBox to load on fedora 21, it keeps saying it cannot find the kernal, Any suggestions as I am at a loss.
Thanks
This is a shame for Fedora project in 2015 year we still need some ‘console-magic_spells’ for make it works in VirtualBox. For example ubuntu, opensuse and derivatives… just work with it without any effort from user!! And this distro position itself as user-friendly? Serious?
Hello Maksim,
Normally Fedora doesn’t have softwares which have closed source components or licences that aren’t compatible with Fedora’s requirements.
So if you want have something similar without any effort, then you can use Boxes+qemu.
Bag for Fedora then… 100% pure open source zealots.. will make no good.
Maksim, I agree, but also understand Fedora Project’s Mission.
Fedora Project is also upstream for RHEL and I understand that they want only pure open source packages, because RHEL releases life cycle is 10+ years. It’s impossible patch closed source/wrong licensed packages.
Muito Obrigado pelo Artigo.
Foi de Grande Ajuda para solucionar os erros no VBox.
Meus Agradecimentos de um usuario brasileiro….
Go Fedora 22 Mate.
Hi,
first of all: thanks for your awesome how-tos! They helped me a lot.
But now I’m stuck at this. My first try to install Virtualbox was to just type
dnf install VirtualBox.x86_64While I had the rpm-fusion-free repository enabled. But this didn’t worked – nothing happened when I tried to run it.
Then I found your tutorial and removed the installed package to start again by following your instructions. Everything was going fine until the end of installation. There I got the following error:
In the log file starts with these lines:
Uninstalling modules from DKMS removing old DKMS module vboxhost version 4.3.28 ------------------------------ Deleting module version: 4.3.28 completely from the DKMS tree. ------------------------------ Done. Attempting to install using DKMS Creating symlink /var/lib/dkms/vboxhost/4.3.28/source -> /usr/src/vboxhost-4.3.28 DKMS: add completed. Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area... make KERNELRELEASE=4.0.6-300.fc22.x86_64 -C /lib/modules/4.0.6-300.fc22.x86_64/build M=/var/lib/dkms/vboxhost/4.3.28/build...(bad exit status: 2) Failed to install using DKMS, attempting to install without make KBUILD_VERBOSE=1 SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 CONFIG_MODULE_SIG= -C /usr/src/kernels/4.0.6-300.fc22.x86_64 modules test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \ echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it."; \ echo >&2 ; \ /bin/false)I think this part is essential but if you need more information you can view the entire logfile here.
I’m using Fedora 22 with kernel version 4.0.6-300.fc22.x86_64.
Can you give ma a hint about what’s going wrong here?
Keep up this useful blog!
Cheers,
Noir
Hi Noir,
Could you first post output of following command:
got it to install, but had to remove
rpm -Uvh http://dl.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm
on x86_64 (I tried x86_64 in place of i386, but I was getting epel issues on subsequent yum installs)
Hi laferrierejc,
Do you use CentOS 6?
Actually
http://dl.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm
and
http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm
Are exactly same noarch packages.
Hello.
I’m using CentOS 7 1503-01 64 bit (3.10.0-229.7.2.el7.x86_64).
During the “service vboxdrv setup” I got a lot of messages like these:
ldconfig: Can’t link /usr/lib64/libkeyutils.so.1 to libkeyutils.so.1.5
ldconfig: Can’t link /usr/lib64/libcap-ng.so.0 to libcap-ng.so.0.0.0
ldconfig: Can’t link /usr/lib64/libgcrypt.so.11 to libgcrypt.so.11.8.2
ldconfig: Can’t link /usr/lib64/liblldp_clif.so.1 to liblldp_clif.so.1.0.0
ldconfig: Can’t link /usr/lib64/libext2fs.so.2 to libext2fs.so.2.4
though really they linked fine. Then I checked that all 4 kernel modules are successfully loaded.
My problem is: when I start virtualbox & and am trying to create a virtual machine (for Linux CentOS 7 64 bit), I see only 32bit versions of Linux in the VM creation menu. While I need a 64-bit one.
What I did wrong?
The “Intel Virtualization Technology” (VT-x) was disabled in the BIOS.
Enabling it solved the issue.
Thank you very much, detailed instructions and good explanation. I didn’t have any problem and all run as it was expected.
Error: Cannot retrieve metalink for repository: epel. Please verify its path and try again
this error came
Hello sajan,
Try following:
On Fedora 22:
No package kernel-PAE-devel available.
Error: no package matched: kernel-PAE-devel
Hi KNERD,
Are you using 32-bit system and PAE kernel?
Could you post output of following commands:
The issue was Fedora was by default loading the debug kernel.
Stopping VirtualBox kernel modules [ OK ]
Uninstalling old VirtualBox DKMS kernel modulesError! There are no instances of module: vboxhost
5.0.4 located in the DKMS tree.
[ OK ]
Trying to register the VirtualBox kernel modules using DKMS[ OK ]
Starting VirtualBox kernel modules [FAILED]
(modprobe vboxdrv failed. Please use ‘dmesg’ to find out why)
help guys i’m new to linux
I had the same issue on Fedora 21 and was able to resolve it by disabling secure boot.
Hope that helps.
Ken.
Dont forget to switch back to non-root user before running the VirtualBox command, otherwise you might see a bunch of nasty error messages
Thanks for the detailed write up, and for updating it every time there is a new version of fedora!
Using Centos 5.11 kernel 2.6.18-406.el5
After add virtualbox.repo, and do yum update, i got error like this:
http://download.virtualbox.org/virtualbox/rpm/el/5/x86_64/repodata/repomd.xml: [Errno -1] pygpgme is not working so repomd.xml can not be verified for virtualbox
Trying other mirror.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: virtualbox. Please verify its path and try again
Is there anything that i missed?
Hi Yoseph,
You are totally right, this Oracle’s repo file (/etc/yum.repos.d/virtualbox.repo) looks like following:
Please open it and comment repo_gpgcheck=1 out:
Save file and try again. Please let me know if this problem persists.
Your solution is disable GPG key checking?
Yes, it works. Thanks.
I hope this is just temporary solutions for now…
Hopely someone on VirtualBox can fix this a.s.ap
Am I right?
Yes solution is disable repodata gpg checking. Packages gpg keys are checked still normally.
This repo works normally on RHEL/CentOS 6 and RHEL/CentOS 7. I think that they should run createrepo and sign repodata on RHEL/CentOS 5 to get it working.
Repodata is signed using GnuPG 1.4.12
RHEL/CentOS 5 have GnuPG 1.4.5
RHEL/CentOS 6 have GnuPG 2.0.14
RHEL/CentOS 7 have GnuPG 2.0.22