VirtualBox Guest Additions on Fedora 34/33, CentOS/RHEL 8/7/6/5 - Comment Page: 6
This is guide, howto install Oracle VirtualBox Guest Additions on Fedora, CentOS and Red Hat (RHEL). This guide should work with Fedora 34/33/32/31/30, CentOS 8.2/7.8/6.10/5.11, Red Hat (RHEL) 8.2/7.8/6.10/5.11. VirtualBox Guest Additions is special software that can be installed inside Linux virtual machines to improve performance and make integration much more seamless. Among the features provided by these VirtualBox Guest Additions are mouse pointer integration and arbitrary screen solutions (e.g. by resizing the guest window). Check video version of guide: Watch More Videos and Subscribe to if-not-true-then-false.com Youtube Channel Note: Fedora 34/33/32/31/30...
352 comments on “VirtualBox Guest Additions on Fedora 34/33, CentOS/RHEL 8/7/6/5 - Comment Page: 6”« Previous 1 … 4 5 6 7 8 … 15 Next »
Thank you for this guide. I had to add my user to the group vboxsf to gain access to the shared folder with
gpasswd -a myuser vboxsf
Took me a bit to figure out why I did not have permission to access the shared folder once I got the guest additions installed. (I think the first time I ran it, it may have said something about creating the group, but nothing after I followed this guide and ran the script again.)
## Join virtual box shared folder group
usermod -a -G vboxsf <USERNAME>
Really hoping someone out there can help me trying to install guest additions for Centos 6.5 using version 4.3.6 of VirtualBox, this is the output from the install
Verifying archive integrity... All good.
Uncompressing VirtualBox 4.3.6 Guest Additions for Linux............
VirtualBox Guest Additions installer
Removing installed version 4.3.6 of VirtualBox Guest Additions...
Copying additional installer modules ...
Installing additional modules ...
Removing existing VirtualBox DKMS kernel modules [ OK ]
Removing existing VirtualBox non-DKMS kernel modules [ OK ]
Building the VirtualBox Guest Additions kernel modules
Building the main Guest Additions module [ OK ]
Building the shared folder support module [ OK ]
Building the OpenGL support module [FAILED]
(Look at /var/log/vboxadd-install.log to find out what went wrong)
Doing non-kernel setup of the Guest Additions [ OK ]
Installing the Window System drivers
Installing X.Org Server 1.13 modules [ OK ]
Setting up the Window System to use the Guest Additions [ OK ]
You may need to restart the hal service and the Window System (or just restart
the guest system) to enable the Guest Additions.
Installing graphics libraries and desktop services componen[ OK ]
Contents of log:
Uninstalling modules from DKMS
Attempting to install using DKMS
Creating symlink /var/lib/dkms/vboxguest/4.3.6/source ->
DKMS: add completed.
Kernel preparation unnecessary for this kernel. Skipping...
cleaning build area...
make KERNELRELEASE=2.6.32-431.3.1.el6.x86_64 -C /lib/modules/2.6.32-431.3.1.el6.x86_64/build M=/var/lib/dkms/vboxguest/4.3.6/build...........(bad exit status: 2)
Error! Bad return status for module build on kernel: 2.6.32-431.3.1.el6.x86_64 (x86_64)
Consult /var/lib/dkms/vboxguest/4.3.6/build/make.log for more information.
Failed to install using DKMS, attempting to install without
make KBUILD_VERBOSE=1 CONFIG_MODULE_SIG= -C /lib/modules/2.6.32-431.3.1.el6.x86_64/build SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 modules
test -e include/linux/autoconf.h -a -e include/config/auto.conf || ( \
echo " ERROR: Kernel configuration is invalid."; \
echo " include/linux/autoconf.h or include/config/auto.conf are missing."; \
echo " Run 'make oldconfig && make prepare' on kernel src to fix it."; \
Some environment stuff:
sudo rpm -qa kernel\* gcc dkms make bzip2
Linux localhost.localdomain 2.6.32-431.3.1.el6.x86_64 #1 SMP Fri Jan 3 21:39:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
LSB Version: :base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch
Distributor ID: CentOS
Description: CentOS release 6.5 (Final)
All help greatly appreciated
I had to use the info that brandon posted above
ln -s /usr/src/kernels/2.6.32-431.3.1.el6.x86_64/ /usr/src/kernels/2.6.32-431.el6.x86_64
it does not like the extra kernel info 3.1.
and the fix from
Patch for CentOS 6.5 with VBOXADDITIONS_4.3.2/4.3.4
ln -s /usr/include/drm/drm.h drm.h
ln -s /usr/include/drm/drm_sarea.h drm_sarea.h
ln -s /usr/include/drm/drm_mode.h drm_mode.h
ln -s /usr/include/drm/drm_fourcc.h drm_fourcc.h
which is linked from https://forums.virtualbox.org/viewtopic.php?f=3&t=58855
Rock On! It worked. Thanks so much.
Try it in command line
Excellent…worked like a charm for me on Centos 5.4 and VB 4.3.6 R91406
I had to make one change for the export KERN_DIR to work.
export KERN_DIR=’/usr/src/kernels/’`uname -r`-`uname -m`
The closing single quote before first `uname
Thanks very much, this guide saves me!
Awesome! You save my time! Thanks for help guys!
Thank you! This is exactly what I was looking for and so straight-forward! I spent hours last night scouring official install instructions to no avail, and this morning your instructions got it done in minutes!
I was having a number of errors pertaining to OpenGL module getting installed:
Building OpenGL support module … failed
I looked into this further from some of the posts in this thread and what helped me was this :
$ yum whatprovides “*drm/drm.h”
i didn’t have the libdrm-devel package installed. once i installed it…boom. works, thought i’d add this comment for anyone else that encounters this error.
Thank you for your input! What host OS you are using?
Have installed centos6.5 on virtual machine, but when restarting the VM the installed gcc/g++ are not found.
Has anyone of you can tell if the “Fullscreen” mode is functional after applying the procedures described here?
Thanks in advance.
Yes, full screen should work after installing VirtualBox Guest Additions.
anyone have this working on CentOS 7?
has no member named ‘numa_next_reset’
I don’t believe CentOS/RHEL 7 is supported in the current stable Virtualbox release (4.3.12). I run into the same error.
Apparently this will be solved in 4.3.14, the release candidate is already available and should fix the issue. Unfortunately I need it to be available in the stable branch to make any use of it as I need to provide it for multiple users. Guess we’ll just have to wait for 4.3.12 to reach stable. :-(