VirtualBox 6.1.28 / 6.1.29 on Fedora 35/34/33, CentOS/RHEL 8/7 - Comment Page: 2

Updated on November 28, 2021 by JR 810 comments

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...

See full post →

810 comments on “VirtualBox 6.1.28 / 6.1.29 on Fedora 35/34/33, CentOS/RHEL 8/7 - Comment Page: 2”

« Previous 1 2 3 4 … 27 Next »

Woodsman
26th October 2010, 9:11 pm

Errors I am getting trying to get Virtual Box running on Oracle Linux(Red Hat Enterprise Linux Server release 5.5 (Tikanga))

[[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.18-194.el5 cannot be found at
/lib/modules/2.6.18-194.el5/build or /lib/modules/2.6.18-194.el5/source.
[FAILED]
(Failed, trying without DKMS)
Recompiling VirtualBox kernel modules [FAILED]
(Look at /var/log/vbox-install.log to find out what went wrong)
[[email protected] ~]#

Any help would be appreciated I tried everything I read in the article and comments.
Reply
- JR
  26th October 2010, 9:35 pm
  Hi Woodsman,
  
  Could you post messages from /var/log/vbox-install.log file. After running following command (as root):
```
 /etc/init.d/vboxdrv setup
```
  Reply
K2
28th October 2010, 8:25 am

I got a problem when I try to start using VirtualBox. This is Fedora 13 & here I post the error message from the terminal screen:

[[email protected] yum.repos.d]# VirtualBox
WARNING: The vboxdrv kernel module is not loaded. Either there is no module
available for the current kernel (2.6.34.7-61.fc13.i686.PAE) or it failed to
load. Please recompile the kernel module and install it by

sudo /etc/init.d/vboxdrv setup

You will not be able to start VMs until this problem is fixed.

So I follow the instruction then there is the result:

[[email protected] yum.repos.d]# sudo /etc/init.d/vboxdrv setup
WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.
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.34.7-61.fc13.i686.PAE cannot be found at
/lib/modules/2.6.34.7-61.fc13.i686.PAE/build or /lib/modules/2.6.34.7-61.fc13.i686.PAE/source.
[FAILED]
(Failed, trying without DKMS)
Recompiling VirtualBox kernel modules [FAILED]
(Look at /var/log/vbox-install.log to find out what went wrong)

And there is the message in “/var/log/vbox-install.log”:

Uninstalling modules from DKMS
removing old DKMS module vboxhost version 3.2.10

——————————
Deleting module version: 3.2.10
completely from the DKMS tree.
——————————
Done.
Attempting to install using DKMS

Creating symlink /var/lib/dkms/vboxhost/3.2.10/source ->
/usr/src/vboxhost-3.2.10

DKMS: add Completed.
You can use the –kernelsourcedir option to tell DKMS where it’s located.
Failed to install using DKMS, attempting to install without
Makefile:159: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR= and run Make again. Stop.

I am a beginner of Linux so please help to describe the problem, any help will be appreicated! ^_^
Reply
- JR
  30th October 2010, 8:09 pm
  Hi K2,
  
  Could you post messages from /var/log/vbox-install.log file. After running following command (as root):
```
 /etc/init.d/vboxdrv setup
```
  Also you could try following:
```
yum install gcc kernel-devel kernel-headers
```
  Then do following:
```
KERN_DIR=/usr/src/kernels/`uname -r`
export KERN_DIR
```
  Then try run following again:
```
 /etc/init.d/vboxdrv setup
```
  Reply
  - K2
    31st October 2010, 12:25 pm
    
    Thanks for your help, JR! :D
    I followed your instruction & copy the result below:
    
    [[email protected] yum.repos.d]# /etc/init.d/vboxdrv setup
    WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.
    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.34.7-61.fc13.i686.PAE cannot be found at
    /lib/modules/2.6.34.7-61.fc13.i686.PAE/build or /lib/modules/2.6.34.7-61.fc13.i686.PAE/source.
    [FAILED]
    (Failed, trying without DKMS)
    Recompiling VirtualBox kernel modules [FAILED]
    (Look at /var/log/vbox-install.log to find out what went wrong)
    [[email protected] yum.repos.d]# yum install gcc kernel-devel kernel-headers
    Loaded plugins: presto, refresh-packagekit
    rpmfusion-free-updates | 3.3 kB 00:00
    updates/metalink | 5.0 kB 00:00
    updates | 4.7 kB 00:00
    updates/primary_db | 4.1 MB 00:07
    virtualbox | 951 B 00:00
    Setting up Install Process
    Package gcc-4.4.4-10.fc13.i686 already installed and latest version
    Package kernel-devel-2.6.34.7-61.fc13.i686 already installed and latest version
    Package kernel-headers-2.6.34.7-61.fc13.i686 already installed and latest version
    Nothing to do
    [[email protected] yum.repos.d]# KERN_DIR=/usr/src/kernels/’uname -r’
    [[email protected] yum.repos.d]# export KERN_DIR
    [[email protected] yum.repos.d]# /etc/init.d/vboxdrv setup
    WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.
    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.34.7-61.fc13.i686.PAE cannot be found at
    /lib/modules/2.6.34.7-61.fc13.i686.PAE/build or /lib/modules/2.6.34.7-61.fc13.i686.PAE/source.
    [FAILED]
    (Failed, trying without DKMS)
    Recompiling VirtualBox kernel modules [FAILED]
    (Look at /var/log/vbox-install.log to find out what went wrong)
    
    And this is the messages from /var/log/vbox-install.log file:
    
    Uninstalling modules from DKMS
    removing old DKMS module vboxhost version 3.2.10
    
    ——————————
    Deleting module version: 3.2.10
    completely from the DKMS tree.
    ——————————
    Done.
    Attempting to install using DKMS
    
    Creating symlink /var/lib/dkms/vboxhost/3.2.10/source ->
    /usr/src/vboxhost-3.2.10
    
    DKMS: add Completed.
    You can use the –kernelsourcedir option to tell DKMS where it’s located.
    Failed to install using DKMS, attempting to install without
    /bin/sh: line 0: test: /usr/src/kernels/uname: binary operator expected
    Makefile:177: *** Error: KERN_DIR does not point to a directory. Stop.
    
    Please let me know if any idea to fix this, thanks! ^_^
    Reply
K2
31st October 2010, 12:24 pm

Thanks for your help, JR! :D
I followed your instruction & copy the result below:

[[email protected] yum.repos.d]# /etc/init.d/vboxdrv setup
WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.
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.34.7-61.fc13.i686.PAE cannot be found at
/lib/modules/2.6.34.7-61.fc13.i686.PAE/build or /lib/modules/2.6.34.7-61.fc13.i686.PAE/source.
[FAILED]
(Failed, trying without DKMS)
Recompiling VirtualBox kernel modules [FAILED]
(Look at /var/log/vbox-install.log to find out what went wrong)
[[email protected] yum.repos.d]# yum install gcc kernel-devel kernel-headers
Loaded plugins: presto, refresh-packagekit
rpmfusion-free-updates | 3.3 kB 00:00
updates/metalink | 5.0 kB 00:00
updates | 4.7 kB 00:00
updates/primary_db | 4.1 MB 00:07
virtualbox | 951 B 00:00
Setting up Install Process
Package gcc-4.4.4-10.fc13.i686 already installed and latest version
Package kernel-devel-2.6.34.7-61.fc13.i686 already installed and latest version
Package kernel-headers-2.6.34.7-61.fc13.i686 already installed and latest version
Nothing to do
[[email protected] yum.repos.d]# KERN_DIR=/usr/src/kernels/’uname -r’
[[email protected] yum.repos.d]# export KERN_DIR
[[email protected] yum.repos.d]# /etc/init.d/vboxdrv setup
WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.
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.34.7-61.fc13.i686.PAE cannot be found at
/lib/modules/2.6.34.7-61.fc13.i686.PAE/build or /lib/modules/2.6.34.7-61.fc13.i686.PAE/source.
[FAILED]
(Failed, trying without DKMS)
Recompiling VirtualBox kernel modules [FAILED]
(Look at /var/log/vbox-install.log to find out what went wrong)

And this is the messages from /var/log/vbox-install.log file:

Uninstalling modules from DKMS
removing old DKMS module vboxhost version 3.2.10

——————————
Deleting module version: 3.2.10
completely from the DKMS tree.
——————————
Done.
Attempting to install using DKMS

Creating symlink /var/lib/dkms/vboxhost/3.2.10/source ->
/usr/src/vboxhost-3.2.10

DKMS: add Completed.
You can use the –kernelsourcedir option to tell DKMS where it’s located.
Failed to install using DKMS, attempting to install without
/bin/sh: line 0: test: /usr/src/kernels/uname: binary operator expected
Makefile:177: *** Error: KERN_DIR does not point to a directory. Stop.

Please let me know if any idea to fix this, thanks! ^_^
Reply
MissyB
7th November 2010, 8:10 pm

Sometimes it is soooo hard to love Fedora, but all of my problems have been solved with info on your site – thank you so much! Beats posting on forums and getting patronising responses from people who haven’t bothered to read actual problem! Thank you again!
Reply
- JR
  7th November 2010, 8:51 pm
  
  Hi MissyB, nice to see you here! :)
  
  Glad to hear that my site has been helpful to you! And feel free to ask if you have any problems. I will try my best to answer… :)
  Reply
Bijon
14th November 2010, 10:07 am

Hi,

Thank you so much for your great post. I have just completed set-up virtualbox on my Centos VPS by simply copying and pasting the commands. Keep up great job. I’ll be back if I need further help.

Thanks
Reply
Brian
3rd December 2010, 8:53 pm

Can someone type what needs to be reconfigured in the Kernel? This is the spot i am stuck on.
Reply
BrianBrian
3rd December 2010, 9:24 pm

the RC–1908 not installed is the issue
Reply
brian
3rd December 2010, 11:32 pm

where is this to be pasted?!

## Current running kernel on Fedora ##
KERN_DIR=/usr/src/kernels/`uname -r`

## Current running kernel on CentOS and Red Hat (RHEL) ##
KERN_DIR=/usr/src/kernels/`uname -r`-`uname -m`

## Fedora example ##
KERN_DIR=/usr/src/kernels/2.6.33.5-124.fc13.i686

## CentOS and Red Hat (RHEL) example ##
KERN_DIR=/usr/src/kernels/2.6.18-194.11.1.el5-x86_64

## Export KERN_DIR ##
export KERN_DIR
Reply
Brian
4th December 2010, 6:51 am

I am new to Fedora ………..I have successfully installed all steps accept this one……

Add KERN_DIR environment variable

## Current running kernel on Fedora ##
KERN_DIR=/usr/src/kernels/`uname -r`

## Current running kernel on CentOS and Red Hat (RHEL) ##
KERN_DIR=/usr/src/kernels/`uname -r`-`uname -m`

## Fedora example ##
KERN_DIR=/usr/src/kernels/2.6.33.5-124.fc13.i686

## CentOS and Red Hat (RHEL) example ##
KERN_DIR=/usr/src/kernels/2.6.18-194.11.1.el5-x86_64

## Export KERN_DIR ##
export KERN_DIR

can someone tell me what this means?
Reply
- JR
  4th December 2010, 1:42 pm
  Hi Brian,
  
  On Fedora paste following lines to console as root:
```
KERN_DIR=/usr/src/kernels/`uname -r`
export KERN_DIR
```
  Then install VirtualBox using YUM (as root):
```
yum install VirtualBox-3.2
```
  Or if you have already installed VirtualBox then setup vbox kernel drivers with following command (as root):
```
/etc/init.d/vboxdrv setup
```
  Reply
  - Brian
    4th December 2010, 8:01 pm
    
    I tried the following steps……… only to receive a failed error………….then i opened by
    
    sudo gedit /etc/init.d/vboxdrv setup
    
    now that I have vboxdrv setp opened w gedit text editor any advice on wht needs to be compiled?
    Reply
    - JR
      5th December 2010, 2:57 pm
      
      Do not edit vboxdrv init script, because it should work quite right.
      
      Please post full error messages what you get?
      Reply
Brian
4th December 2010, 8:07 pm

/lib/modules//lib/modules/2.6.35.6-48.fc14.i686.PAE/build

in this link………it says the link is broken in the /build
Reply

RC–1908 KERNEL not installed

How can this be taken care of?

Hi rosco,

First install following packages:


yum install gcc kernel-devel kernel-headers

Set KERN_DIR environment variable:


## Current running kernel on Fedora ##
KERN_DIR=/usr/src/kernels/`uname -r`
 
## Current running kernel on CentOS and Red Hat (RHEL) ##
KERN_DIR=/usr/src/kernels/`uname -r`-`uname -m`
 
## Export KERN_DIR ##
export KERN_DIR

Then install VirtualBox or run kernel driver setup:


yum install VirtualBox-3.2
## OR ##
/etc/init.d/vboxdrv setup

Romz
8th December 2010, 12:03 pm

How can i solved this problem I’m using Fedora 14

GLib-GIO:ERROR:gdbusconnection.c:2270:initable_init: assertion failed: (connection->initialization_error == NULL)
Aborted (core dumped)
Reply
- JR
  9th December 2010, 8:03 am
  Hi Romz,
  
  Are you sure that you installed the correction version of VirtualBox?
  
  Could you post full output from console after running VirtualBox command?
  
  And following command output:
```
yum list installed |grep -i virtualbox
```
  Reply
earl
13th December 2010, 2:07 am

besides being root………what else do you key in before this?

## Current running kernel on Fedora ##
KERN_DIR=/usr/src/kernels/`uname -r`

## Current running kernel on CentOS and Red Hat (RHEL) ##
KERN_DIR=/usr/src/kernels/`uname -r`-`uname -m`

## Export KERN_DIR ##
export KERN_DIR

every since i started using Fedora 14.I cannot use the virtual machines! none of them!
Reply

YOUV’E GOT TO BE MORE SPECIFIC !

WILL YOU PLEASE SET AN EXAMPLE FOR THOSE WHOM NEVER USED FEDORA?

WHAT DOES KERN_DIR mean? do I change uname with something else?

is there any tutorials on seting KERN_DIR?

KERN_DIR=/usr/src/kernels/`uname -r`

## Current running kernel on CentOS and Red Hat (RHEL) ##
KERN_DIR=/usr/src/kernels/`uname -r`-`uname -m`

## Export KERN_DIR ##
export KERN_DIR

Hi earl,

You should simply run following commands on Fedora as root:


## Set KERN_DIR environment variable with following command ##
KERN_DIR=/usr/src/kernels/`uname -r`

## You could verify what happens after this command with following command ##
echo $KERN_DIR
## Output Shouls look something like following ##
/usr/src/kernels/2.6.35.9-64.fc14.i686

## Then export KERN_DIR environment variable ##
export KERN_DIR

You could also use following method:


## Print the kernel release ##
uname -r
## Output something like ##
2.6.35.9-64.fc14.i686

## Set KERN_DIR environment variable using your kernel release ##
KERN_DIR=/usr/src/kernels/2.6.35.9-64.fc14.i686

## You could verify KERN_DIR variable with following command ##
echo $KERN_DIR

## Export your KERN_DIR environment variable ##
export KERN_DIR

Is this specific enough? Did you get the point?

Clyde
13th December 2010, 3:31 am

this is what i keyed in

KERN_DIR=/usr/src/kernels/2.6.35.9-64.fc14.i686

yes.this is my kernel

followed by

export

where is my error?!
Reply
- JR
  13th December 2010, 9:04 am
  Hi Clyde,
  
  If your kernel release is 2.6.35.9-64.fc14.i686 then just run following:
```
KERN_DIR=/usr/src/kernels/2.6.35.9-64.fc14.i686
export KERN_DIR
```
  Check more information from here.
  Reply

« Previous 1 2 3 4 … 27 Next »

810 comments on “VirtualBox 6.1.28 / 6.1.29 on Fedora 35/34/33, CentOS/RHEL 8/7 - Comment Page: 2”

Leave a Reply to JR Cancel reply