Perryg wrote:Steps I used to get a working version of 17.10 below screen shot.
The attachment Ubuntu-17.10_working.png is no longer available
- 1) Clean install and ran apt-get update && apt-get dist-upgrade followed with a reboot.
2) Rename /lib/modules/4.13.0-16-generic/kernel/ubuntu/vbox to vbox.old and reboot the guest.
3) Install my guest additions 5.2.1 r118468 followed with a reboot.
After I verified that this worked properly I did an apt-get update && apt-get upgrade and the package returned nothing to do. If you find that your install tries to update I would pin, lock, even go so far as to create a script to stop ubuntu from updating these packages. (search for how to stop apt from installing a package if you don't know how).
I then tested a new install and simply installed the guest additions, rebooted and it does not work properly. I found conflicts with the Ubuntu kernel modules and the official ones I installed which prevented some features from working.
Of course you also have the choice of using their guest additions but we you would need them to support you.
Hello,
I've been having my most frustrating VirtualBox experience ever trying to get Guest Additions working. I'm a long-time VirtualBox user, and greatly appreciate its availability and utility. I've now tried to install Guest Additions with Ubuntu, Mint, ElementaryOS, and CentOS - without success in every case. As you can see, for my use case (development) I prefer the Debian based distros. CentOS was mainly an experiment, as I was sure the GA would install successfully there. Not so. I've seen basically the issue described here with all these distros. At any rate, if I can get things going with Ubuntu 17.10 I should be able to deal with the other Ubuntu based distros as well.
Host environment:
VirtualBox 5.2.0 r118431 (Qt5.6.2)
Windows 10 Enterprise, version 1607, build 14393.953
Xeon E3-1505M v5 2.8 GHz.
16 GB RAM
Guest environment:
Ubuntu 17.10 (kernel: 4.13.0-16-generic)
4 processors
10240 MB RAM
64 GB virtual disk
First off, I needed to do an extra step after the base install, update, and vbox -> vbox.old rename - the Guest Additions installer informed me that I had to install gcc, make and perl. I reverted to the snapshot before the vbox rename, and did that install, rebooted, renamed vbox, and rebooted. As expected, the VM booted without window resizing working, indicating that GA were disabled. I did get a dialog after several seconds stating "System program problem detected", which I presume relates to renaming the vbox kernel module dir.
I then proceeded to insert the GA image, start the install process, and authenticated as superuser. After building for a while, the message "VirtualBox Guest Additions: Look at /var/log/vboxadd-setup.log to find out what went wrong" appeared. That was followed by "VirtualBox Guest Additions: Starting." but it didn't successfully start - no UI resizing on window resize.
Near the top of /var/log/vboxadd-setup.log, there appeared the missive:
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/autoconf.h are missing."; \
echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it."; \
echo >&2 ;
/bin/false)
This seemed strange, in that /usr/src/linux-headers-4.13.0-16-generic/include/config/auto.conf is in fact present. At any rate, I don't recall ever having these issues installing GA previously.
I've uploaded a tarball of the vbox-setup.log in case you want to look at all the gory details.
Thanks much for any help you can provide with this!