I've spent all week trying to find an answer to this issue through google
I have installed VirutalBox 6.0.0 on a Windows 10 64-bit host, and I have created a VM and installed the latest CentOS 7 iso (CentOS-7-x86_64-DVD-1810). I have installed VirutalBox Guest Additions in the guest; there were no errors during the installation, and I'm enjoying some of the VirtualBox features that require Guest Additions (e.g. shared clipboard, shared folders, drag-and-drop, etc).
My only problem is that my resolution is limited to sizes no greater than 1024x768 and the "auto-resize guest display" option in VirutalBox is greyed out. I've tried setting up new VMs. I've tried reinstalling guest additions. I've tried reinstalling guest additions after updating the kernel to the latest version, and without updating the kernel at all. I've verified that I have all of the necessary packages to build against my current version of the kernel (e.g. kernel-headers, kernel-devel, etc). I've verified that systemctl shows the guest additions services as starting successfully. I've tried modifying my grub configuration to use vga=ask and selecting one of the alternative resolutions available there, but CentOS never finishes booting if I do that.
I am at wit's end. Does anyone have any other ideas?
Versions:
Windows 10 64-bit host
VirtualBox 6.0.0
CentOS 7 guest using CentOS-7-x86_64-DVD-1810.iso
After trying an insane number of combinations, I was able to get this working with the following procedure
1) Install clean CentOS7
2) Update to latest kernel
3) Remove all kernel packages for the old kernel version
4) Build VBoxLinuxAdditions
What was weird was that this procedure didn't work for the older kernel (e.g. the one that came with my fresh CentOS7 install, prior to updating it with yum); the CentOS7 installer was installing the headers for the newer kernel even if I hadn't installed the newer kernel yet. So there was some sort of version mismatch between what VirtualBox thought it was building against vs what it was actually building against, resulting in nothing working until I had removed all traces of the old kernel.
Related
I have followed this GCP guide with Ubuntu 18 and 20 (have also tried Ubuntu Lite, Debian and Centos 7) but, unfortunately, after completing the lengthy install I get this:
me#gpu:~$ nvidia-smi
NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running
I have tried installing via the script and via the direct downloads from the Nvidia site for Cuda 10. Ready to pull my hair out if that helps! I don't understand how a company that builds a bazillion GPU's can't make the installation process robust?
I have also tried these recommendations with no luck.
I was able to get it working. The mistake I was making was not doing the pre-installation steps before running the cuda_10.1.243_418.87.00_linux.run script. I was under the impression the *.run file would do everything for me. It would help if users were told they MUST do the pre-installation steps. Specifically I had to do this for Ubuntu 18:
sudo nano /etc/modprobe.d/blacklist-nouveau.conf
blacklist nouveau
options nouveau modeset=0
sudo update-initramfs -u
reboot
This seems like a bit of a “hack”, so not sure why nvidia can’t make the installation process more robust? They make a bazillion of these cards. It’s not like some homemade product with a niche user base…
If you've installed the driver so many times and nvidia-smi is still failing to communicate, take a look into prime-select.
Run prime-select query, this way you are going to get all possible options, it should show at least nvidia | intel.
Select prime-select nvidia.
Then, if you see nvidia is already selected, choose a different one, e.g. prime-select intel. Next, switch back to nvidia prime-select nvidia
Reboot and check nvidia-smi.
Plus, it could be a good idea to run again:
sudo apt install nvidia-cuda-toolkit
When it finishes, reboot the machine, and nvidia-smi should work then.
Now, in other cases it works to follow these instructions to install CuDNn and Cuda on VMs cuda_11.2_installation_on_Ubuntu_20.04.
And finally, in some other cases it is caused by unattended-upgrades. Take a look into the settings and adjust them if it is causing unexpected results. This URL has the documentation for Debian, and I was able to see that you already tested with that distro UnattendedUpgrades.
After installing Ubuntu 18.04 on Virtual Box 6.1 the screen is small and we are unable to install Guest Additions.
If you try to access the mounted guest additions ISO image directly, you get mount errors.
Changing the Screen resolution of the Ubuntu worked for me.
Go to Displays Setting and change Resolution.
On the internet people are giving different solutions that could end up corrupting the installed guest OS. After trying multiple times to have the screen size resolved with Ubuntu 18.04, Virtual Box 6.1 running on Windows 10, here are exact steps that will help:
Make sure to install VirtualBox Extension pack from -
https://www.virtualbox.org/wiki/Downloads
Opt to do "normal installation" with following selected - "Download updates while installing Ubuntu" and "Install third-party software for graphics and Wi-fi hardware and additional media formats"
After installation, system will restart but the screen will be small
IMPORTANT STEP: If you click on 9 dots (Show Applications), you should see icon for "Software Update" (spinning circle with A on it). Click on it and ensure all the pending updates are installed
Once all the software updates are completed, open terminal and run following command - sudo apt install gcc make perl
Then click on Devices > Insert Guest Additions CD image
While guest addition is being installed keep focused eye on the output. If any dependencies is missing, you will see it on the screen. If all dependencies are resolved the auto-run should install the guest additions for you and clearly state that install additions will not activate until restart.
Restart the OS and you should see full screen on load.
With latest VirtualBox version 6.1.4, the above did not work as the issue was in Guest Additions 6.1.4. Installing Guest Additions 6.1.5 from https://www.virtualbox.org/wiki/Testbuilds solved the problem. For details refer -https://www.virtualbox.org/ticket/19336
Also I had to assign more display memory. After logging in I have to press Ctrl + F or view > full screen to let the screen scale.
Hope this helps!
I googled before and found that by turning on the "Enable copy and paste" under Guest Isolation, I can copy/cut/paste text from guest to host and vice versa. But I don't see "Guest Isolation" after clicking on Player->Manage->virtual machine settings->option. I have tried to install the VMware tools and I seem to have successfully installed it, but still no use. Is this feature only available in VMware pro?
For Ubuntu (Guest OS), you need to install open-vm-tools and open-vm-tools-desktop.
sudo apt install open-vm-tools open-vm-tools-desktop
Some versions of vmware-tools are buggy (copy&paste does not work). Try an older version (they can be downloaded for free from vmware.com).
Note that newer Linux distributions already include the vmware-tools. They may not be installed by default (see this answer).
I'm using cloud-init to configure my EC2 instances at launch time, currently just on CentOS 7. I need to upgrade to the latest kernel, etc so first I have:
package_upgrade: true
Then I add a bunch of repos and install some packages with yum that ultimately compile some kernel modules with DKMS (Nvidia drivers)
Finally I reboot the system with:
power_state:
mode: reboot
timeout: 30
This all works great! However, when the system comes back up, DKMS reports that the nvidia driver is "added" but not installed and the Nvidia driver doesn't work. If I yum reinstall nvidia-kmod everything works. So obviously what's happening is the kernel module is being compiled and installed for the previous kernel and not the new kernel.
So what is the suggested way to solve this? Is there a way to reboot after the package_upgrade but before any of the other steps? Is there a way to force nvidia-kmod to compile for the new kernel and not the current kernel? Any other ideas?
Looks like the only real option is to create a cloud-init per-boot script that runs dkms-autoinstall. This attempts to compile any "added" kernel module that aren't yet installed on every boot.
Trying to get set up with Vagrant but getting the error:
The "VBoxManage" command or one of its dependencies could not be found.
Please verify VirtualBox is properly installed. You can verify everything
is okay by running "VBoxManage --version" and verifying that the VirtualBox
version is outputted.
Just confused because the Vagrant documentation states:
"The getting started guide will use Vagrant with VirtualBox, since it is free, available on every major platform, and built-in to Vagrant."
Don't want to install VirtualBox separately if its supposed to be included when I installed Vagrant. Running OSX 10.8 if it's relevant, guessing I just need to install VirtualBox? If that's the case, what do they mean in the documentation when they say it's "built-in"?
Installing VirtualBox is required if you plan on using VirtualBox with Vagrant. I'm guessing they meant that the VirtualBox integration is built-in?
Recently, they've abstracted out the VirtualBox specific code and are working on allowing for multiple providers. I believe VMWare is now supported in addition to VirtualBox.
I had this message but my problem was different. I use Vmware_fusion as the provider. Vagrant was not able to detect what provider I am using.It assumed that I am using VirtualBox. Had this issue fixed by calling vagrant up provider flag. Here is the full command
vagrant up --provider vmware_fusion