Guest Additions Install Fails Install without any error
CentOSThis forum is for the discussion of CentOS Linux. Note: This forum does not have any official participation.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Guest Additions Install Fails Install without any error
Don't know why this won't install correctly the 1st time. Earlier this year did an install and it took a few times before it finally installed. Just re-running the same commands over.
Just did an install and no errors. Both vboxadd-install.log and vboxadd-setup.log.2 don't show any errors.
Checking modules shows the following
Code:
vboxsf 81052 0
vboxguest 349038 0 vboxsf
Here are my notes on the steps that I took:
Quote:
install latest kernel
mount VB Guest Additions
install the following package: yum install -y epel-release or go to home page to get the correct URL:
Have You symlinks in Lib/modules/<version>/{build,source}?
Have you compiled in /usr/src/linux-<version>? If not, run 'make distclean' in the source. Then copy the appropriate /boot/config-<version> to the kernel source and rename it to .config. Then run 'make all' with a '-j' option to suit your box. No need to install it; just make it, and don't clean up.
THEN try compiling thekernel modules again for virtualbox.
No on creating the symlinks to /lib/modules/<3.10.0-1127.19.1.el7.x86_64. I have no idea on why to do this. Any examples that you would recommend?
I do see there is a build and source directory. The build directory points to /usr/src/kernels/3.10.0-1127.19.1.el7.x86_65 and source has a softlink to build.
I also don't understand why I would have to compile /usr/src/kernel and then the other commands that you recommended? I would prefer to use the VirtualBox commands, but it isn't offering any meaningful output.
I've never have been successful in compiling my own kernel, but that was along time ago.
The reason for those links is that the package building an external module can do something like 'cd source' and land in the kernel. It seems the symlinks are there.
Just humour me. Virtualbox needs a compiled source. Copy in the config from /boot, and build it. RH did the sweating to make it compile. And as a general rule, don't argue every point with someone trying to help you out. I've been in this mess, and I got myself out.
I don't recommend kernel documentation. There's gigabytes of it and a the longest are 'how-to-shine' type documents that presume you're an idiot, or documents by geeks who have been assimilated into some university. They follow a typical university format:
Name of this document
contents …
Scope …
History …
Contributors …
What this document could have been about
What this document should have been about
Sections …
etc. etc. You hit real information on your third day of reading it.
I was trying to help you to build your virtualbox modules. How did that go?
Not very well...seems like the install kind of worked. Shared folder between the host is working, along with the copy/paste of text to and from the guest to host and vice versa, however the screen size is small. Not sure if there is a way to fix this or not.
Dmesg does show the following, which is probably the problem
Two types of logs output by VB Guest Additions under /var/log:
Code:
vboxadd-install.log
vboxadd-setup.log
Code:
[root@cent07001-docker log]# cat vboxadd-install.log
VirtualBox Guest Additions: Starting.
VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel
modules. This may take a while.
VirtualBox Guest Additions: To build modules for other installed kernels, run
VirtualBox Guest Additions: /sbin/rcvboxadd quicksetup <version>
VirtualBox Guest Additions: or
VirtualBox Guest Additions: /sbin/rcvboxadd quicksetup all
VirtualBox Guest Additions: Building the modules for kernel
3.10.0-1127.19.1.el7.x86_64.
VirtualBox Guest Additions: Running kernel modules will not be replaced until
the system is restarted
This is the current kernel version that I'm running, don't plan on updating it as this is a static CentOS7 that I use for Docker.
[root@cent07001-docker log]# cat vboxadd-setup.log.3
Building the main Guest Additions 6.1.14 module for kernel 3.10.0-1127.19.1.el7.x86_64.
Building the shared folder support module.
Building the graphics driver module.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.