Virtualbox Guest Additions Problem
Chrystal Dueno
I ran into this problem recently (Sep. 2017) trying to install Guest Additions into Oracle VM VirtualBox Manager version 5.1.28 in a newly-installed VM for Ubuntu version 16.04. The host is Windows 10.
For me, the solution was discovering that you have to add an Empty optical drive in the virtual machine settings! If you try to "help" by pre-loading the VBoxGuestAdditions.iso, it doesn't work. The shortcut on the Devices menu "Insert Guest Additions CD image ..." wants to find an empty optical drive to use!
I had the same problem and manual installation with sudo apt-get didn't work for me. Different Virtual Box has different guests additions version so it's better to install the guest additions that comes with Virtual Box. So I installed it in this way:
First, boot up the Ubuntu VM. Then press Devices > Insert Guest Additions CD. The CD has now inserted but you won't see anything. If you try to press Insert Guest Additions CD again you will get the error.
The problem many times that happens is that the iso file you installed is already mounted. Just go to Devices-Optical Device-Remove Virtual Disk from Guest installation. Then Manually mount the Guestadditions.iso file by going to Devices-Optical Drive-Choose Disk image then go to the folder where you installed ubuntu, find the guestadditions.iso file and then mount it. Once mounted, simply again click the Devices-Install Guest additions, enter your userID password for Ubuntu and the wizard will then continue to install the guest additions :)
Same error for me with Macos. I was hitting the error Could not mount the media/drive '/Applications/VirtualBox.app/Contents/MacOS/VBoxGuestAdditions.iso' (VERR_PDM_MEDIA_LOCKED). The guest additions iso was already downloaded previously. All steps are done within VM.
For windows 10 as host start the VM click on devices --> Optical Devices --> choose disk image --> go to C:\Program Files\Oracle\VirtualBox --> select VBoxGuestAdditions.iso from there -->Click Ok --> A small window will appear Click Force Unmount --> now again click on devices with ubuntu logged in -->Click on insert Guest Additions CD image --> click run --> after the successfull insert your ubuntu will start coming on fullscreen.
Click on start button in your virtual boxLogin to your ubuntu machineon top of the machine you'll find controls for your virtual boxclick on View > Seamless Mode (Right hand side Ctrl + L key)that's all you will be in maximized viewIf you want to enter in full screen mode click on view > Full-screen mode (Right handside Ctrl + F key)
I am having really annoying problem and have spent hours trying to fix. I have searched ad nauseum and found others with same problem but none of the solutions work. I go to Devices to Install Guest Additions and find that instead it says Insert Guest Additions CD. When I try that it says it cannot insert and asks if I want to force mount. I try that and I get error that it cannot force unmount because it is locked (I get an error that is similar to this). What the heck is going on? Appreciate any advice. Thank you!
If the guest vm is not showing any installer popup while you click install on guest addition folder or while running from the terminal as,sudo ./runasroot.sh or sudo ./autorun.shTry this command for the file in that folder with VBoxLinuxAdditions.run as,
You have to do it in the guest ist selves. Just check that virtualbox has the version you like to have.
The iso should be updated automatically.
You just have to use the " Insert Guest Additions CD image option":
Almost not used windows since I said goodbye to it. I would like to have a minimal image were i could use some software, but without all the crap who comes with it. Unfortunately I always removed it again because of the size of it.
I have noticed a recommendation to change CPU topology from default to 1 socket 2-3 cpus 2 threads in Chris Titus videos, and VMs indeed seem to run better.
Give KVM a try! Virtualbox is type 2 hypervisor and will run much slower.
Just sudo dnf install @virtualization (if you are not on Silverblue).
Just a quick update: I created a VM for Win10 using virt-manager, and thanks to the valuable resources posted here (and some others), installation and configuration were a breeze. Everything is working just fine, and I will be able to drop VirtualBox entirely. So, big thanks to everyone that replied here, especially @caesar and @andym , for opening my eyes
host os-windows 10
guest os -manjao kde minimal
i mount the guest additions image and run autorun.sh
it asks me for sudo password
i enter it and it tells that could not find an interactive shell to start
shell-fish,bash
From your Manjaro guest installation system, just open Pamac and look for virtualbox-guest-utils and install it, or from terminal
pamac install virtualbox-guest-utils
or
sudo pacman -S virtualbox-guest-utils
www.linuxtechi[.]com/install-virtualbox-guest-additions-on-rhel/
www.linkedin[.]com /pulse/installing-virtualbox-guest-additions-centosrhel-enhanced-soran
forums.virtualbox[.]org /viewtopic.php?t=1091421
technixleo[.]com /install-and-use-virtualbox-on-centos-rhel/
kifarunix[.]com /install-virtualbox-guest-additions-on-rocky-linux-9/
With that said, this worked fine for myself. I was not able to replicate your issue with a standard installation of Rocky Linux. In my case, I used the XFCE desktop. GNOME (Workstation) and others should work the same way.
So, the short version of this long story is that GA seems to have installed, at least partially, but with some problems. There still are errors during compiles for the GA installation yet some of it works.
If you are continuing to have issues, I would suggest uninstalling all the drivers, rebooting, and trying to install them again. You could also start clean and just reinstall Rocky Linux 9 entirely to the VM and run through the installation steps for the guest additions.
Long time linux user but first go around with archlinux. I'm very impressed by the speed of archlinux and everything has installed/worked great so far except installing the vbox guest additions. Once I get everything like I want it I can see installing this on one of laptops.
As far as I know I have installed all of the prereqs but I still can't get the kernel modules built with the vbox additions. I have installed gcc, linux-headers, make, dkms, autoconf, automake and several other dev tools. Below is the first error in var/log/vboxadd-setup.log.
Actually I did install those but they didn't seem to provide the functionality the additions typically provide. Ahh...My vbox host is 6.1.2. Those additions are old. I will download a more recent version of the extensions and try again. If that doesn't work I will update both to 6.1.4.
I'm not sure why resizing won't work. I have 3 other Linux guests as well as Solaris, BSD and windows and I am able to resize and go full screen on all of them. I'll play around with VBoxClient a bit and if that doesn't work I may start over now and apply some lessons I have learned on this first try with archlinux.
You are installing the VBox host packages in the host, and the guest* package(s) in the guest, yes?
I have these (Arch host, with Arch guest) and have no problem with screen resize (although recent updates seem to have broken bidirectional clipboard, unrelated):
For some reason the 15.2 repo still provides a range of VBox packages, for instance virtualbox-guest-x11 has several versions available from 6.0.6 through 6.1.2 : please check that you actually installed a version matching your host (6.1.2 apparently).
Probably. Definitely in vmware-tools. The copy/paste buffer and keyboard/mouse shared memory areas allow access to the host. If the virtual is rooted it's trivial to determine the type of virtualization used and hack/install your own client tools. AFAIK, only vmware has had example code to hack over these API channels and that's been patched for quite some time.
That being said the changes of you getting hacked this way are probably close to zero. I wouldn't concern myself until we start to see published hacks using these methods. Or rather, there's plenty of other things to spend time on securing first. Shared file access, not using a DMZ, improper firewalling, weak passwords, bad file permissions are all more important.
Always remember, social networking hacks, mis-configured systems and disgruntled employees and plain stupidity (selling data loaded harddrives on ebay, password taped to the monitor, etc.) are the top four entry points for most reported large system hacks.
OpenBSD has the right attitude. Don't install it unless it's absolutely needed. You can install the network driver from the client tools on it's own. "Secure" virtuals should not have shared file access, consoles, etc..
The guest is sandboxed. Guest additions are installed on the guest OS. I don't see how it's any more of a security risk than having that machine on your network as a physical system...I suppose you could come up with some scenarios of a more direct threat if you have host-to-guest drive sharing enabled.
There are some vulnerabilities in any software, and virtualization software is no different. However, the vulnerabilities are currently hard to do and little known or understood - thus not much of a threat. There is the threat that a user may try to "break" the virtualized sandbox; however, as I mentioned, this is currently not likely to occur.
The exploits are over data channels and shared memory. Host OS doesn't matter per se. It's the individual code involved and the access controls/permissions on the host. (selinux/apparmor/tomoyo for linux)
I found that the Oracle certificate that had been used to sign the Guest Additions device drivers, security catalog files, and so on, has a certification path for which the only trusted root certificate, in a new installation of Windows Server 2022, is a DigiCert Assured ID Root CA certificate signed by Microsoft. That root certificate expired on April 15, 2021, as described in this Microsoft document:
d3342ee215