VirtualBox 6.1.28 / 6.1.29 on Fedora 35/34/33, CentOS/RHEL 8/7 - Comment Page: 6
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...
Oh, found a solution. I found this command in a book: yum install make automake autoconf gcc kernel-devel dkms
Worked fine after that :)
Excellent! :)
Great site. I have same issue : unable to run vboxdrv setup using dkms after upgrading kernel (2.6.41.1-1.fc15.x86_64). I use the symbolik link tip (ln -s /usr/src/kernels/`uname -r`/include/linux/amd-iommu.h /usr/src/kernels/`uname -r`/arch/x86/include/asm/amd_iommu.h) and it’s run.
A suggestion : is it possible to begin with the most recent comments first ?
Hi Berni,
Nice to hear that you got it working… :)
Good suggestion, it is possible yes, but I have to also think some other changes too, like “Leave a Comment” form position/redesign and maybe paging for comments… :)
Thank you, worked like a charm on centos 6 x64!
this is the error i get when running /etc/init.d/vboxdrv setup:
[[email protected] arch]# /etc/init.d/vboxdrv setup
Stopping VirtualBox kernel modules [ OK ]
Uninstalling old VirtualBox DKMS kernel modules [ OK ]
Removing old VirtualBox pci kernel module [ OK ]
Removing old VirtualBox netadp kernel module [ OK ]
Removing old VirtualBox netflt kernel module [ OK ]
Removing old VirtualBox kernel module [ OK ]
Trying to register the VirtualBox kernel modules using DKMSError! echo
Your kernel headers for kernel 3.1.5-2.fc16.i686.PAE cannot be found at
/lib/modules/3.1.5-2.fc16.i686.PAE/build or /lib/modules/3.1.5-2.fc16.i686.PAE/source.
[FAILED]
(Failed, trying without DKMS)
Recompiling VirtualBox kernel modules [ OK ]
Starting VirtualBox kernel modules [FAILED]
(modprobe vboxdrv failed. Please use ‘dmesg’ to find out why)
how do i troubleshoot that? thanks!
i just got it working! thanks for this tutorial! i’m now performing a minimal Fedora 16 install on Virtualbox. sweet! :-D
Hi hoychoy,
Excellent to hear that you got it working! :D
Perfect instructions, i installed it on Fedora 16 and it is running as it should,
thanks for posting instructions
Cheers
HI
I’m not regular user of fedora..
but now i want to use PuTTY with fedora-16 installed on my virtual box..
when i type ifconfig it shows me lo and p2p1 connection
it shows me inet add instead of ip adress
when i try to insert that address in puTTY
it gives me Timeout error
As suggested i tried many ways like disabling firewall..
But no use..
Please help me out with this.. M working on big project and this shit happened.. Please suggest.. What to do?
Hi chaitanya,
First check your VirtualBox network card configuration? You should get ip for your interface.
Next check your Fedora 16 network configuration, is it using DHCP or static network settings?
RTR3Init failed with rc=-1912 (rc=-1912)
The VirtualBox kernel modules do not match this version of VirtualBox. The installation of VirtualBox was apparently not successful. Executing
‘/etc/init.d/vboxdrv setup’
may correct this. Make sure that you do not mix the OSE version and the PUEL version of VirtualBox.
how to remove this error please help.
thanx
Hi Kunal,
Could you post output of following command:
Did you tried to run?
usermod -a -G vboxusers user_name
returns
usermod: user ‘user_name’ does not exist
On a fresh Fedora 16 install. Thanks!
Hi James,
You should use real user name (like your own user name):
I confirm successful installation and it works fine.
Just aside note that needed packages are kernel-devel(obligatory) and dmks(optional – works without this, but required for recompiling VB modules along side with the linux kernel, other way it should be done manually with ‘service vboxdrv setup’).
yum install kernel-devel
yum install dmks
Salutations!
To correct myself : dkms
yum install dkms
sorry :)
Hi Igor,
Actually both kernel-devel and dkms are on dependency packages list on step 4. Full list is binutils gcc make patch libgomp glibc-headers glibc-devel kernel-headers kernel-devel dkms or PAE kernel users yum install binutils gcc make patch libgomp glibc-headers glibc-devel kernel-headers kernel-PAE-devel dkms… :)
I am having a problem installing Virtualbox under Fedora 14 (Amahi). I have followed every step in your guide but I cannot manage to rebuild kernel modules. Whenever I try to execute
/etc/init.d/vboxdrv setupI have tried your troubleshooting guide as well but I keep getting the following error message:
[[email protected] ~]# KERN_DIR=/usr/src/kernels/`uname -r`
[[email protected] ~]# export KERN_DIR
[[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
Error! Your kernel source for kernel 2.6.35.6-45.fc14.x86_64 cannot be found at
/lib/modules/2.6.35.6-45.fc14.x86_64/build or /lib/modules/2.6.35.6-45.fc14.x86_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)
What can be wrong? Could you give me a hand to figure this out? Cheers!
I don’t know what was wrong. I tried several of the tips listed above, rebooted the system and voila… it worked! I manage to run /etc/init.d/vboxdrv setup without errors. I installed my first virtual machine in Fedora 14/Amahi. I now have an up and running virtual machine with Windows 7 x64 running inside Fedora 14/Amahi. This is amazing stuff! Thank you very much.
The basic install worked for me. I ended up here and realized I had forgotten to do a yum install gcc. All good now!
This has worked perfectly. Many thanks!
Hi, I have installed the virtualbox and it works fine. But I’m trying to create a Fedora VM inside it.
Fedora Lives start normally (In fallback mode), but when I try to install on disk I get an error at the end and I can’t finish the installation.
It don’t give me any kind of report, just an error.
Some one have this issue or know how to fix it?
Thanks
Hi Rafael,
Could you tell your virtual machine specs (Fedora version, RAM…)?
So you get error without any error message? Could you even take screenshot of this situation?
Or you can start anaconda installer from command line with following command:
Do you see any error messages then?
Hi JR.
Thansk for your helping.
My VM specs is the follow:
[General]
Name: Fedora 64
OS Type: Fedora (64 bit)
[System]
Base Memory: 2048 MB
Processor(s): 1
Execution Cap: 100%
Boot Order: Floppy, CD/DVD-ROM, Hard Disk
VT-x/AMD-V: Enabled
Nested Paging: Enabled
[Display]
Video Memory: 12 MB
3D Acceleration: Disabled
2D Video Acceleration: Disabled
Remote Desktop Server: Disabled
[Storage]
-Controladora IDE
IDE Secondary Master (CD/DVD): Fedora-16-x86_64-Live-Desktop.iso (604.00 MB)
-Controladora SATA
SATA Port 0: Fedora 64.vdi (Normal, 8.00 GB)
[Audio]
Host Driver: ulseAudio
Controller: ICH AC97
[Network]
Adapter 1: Intel PRO/1000 MT Desktop (NAT)
[Serial Ports]
Disabled
[USB]
Device Filters: 0 (0 active)
[Shared Folders]
None
I did what you ask, but I still get error. This time, I could get an Log, but is too long to put here. You can download it .
I hope that you can understand my english and help me.
Thanks again
I did a mistake on the link
download error log
I got a long and probably better on. Sorry by my multiples posts
Download Long Log
Your error message is due to too small root partition. This is actually bug and you can find full bug report here. Normally 2330 MB should be enough but some reason it needs over 4016 MB.
You can try to create over 4016 MB root partition (example 4500 MB) and try to install it again…do you got it working then?
Hey JR.
Really thanks, you have solved my problem. I have never thinked that the root disk size could be the reason for my problem.
You’re a good expert and a patient guy.
Thanks again
Excellent to hear that you got it working! :)
Thank you for compliment!