Downloaded VirtualBox 4.3.6 and after attempting to install in Mavericks (OSX 10.9.1) I get a generic error "The installation failed".
Going through the logs and after running the uninstall tool I arrived at the conclusion that VirtualBox cannot unload there particular kernel extensions: org.virtualbox.kext.VBoxUSB, and org.virtualbox.kext.VBoxDrv.
The exact errors are:
(kernel) Can't unload kext org.virtualbox.kext.VBoxUSB; classes have instances:
(kernel) Kext org.virtualbox.kext.VBoxUSB class org_virtualbox_VBoxUSB has 1 instance.
Failed to unload org.virtualbox.kext.VBoxUSB - (libkern/kext) kext is in use or retained (cannot unload).
(kernel) Can't remove kext org.virtualbox.kext.VBoxDrv; services failed to terminate - 0xdc008018.
Failed to unload org.virtualbox.kext.VBoxDrv - (libkern/kext) kext is in use or retained (cannot unload).
Manually attempting to unload the kexts with sudo kextunload -b org.virtualbox.kext.VBoxUSB produces exact results.
Is there any way to remove these? I ran the VirtualBox uninstaller so I'm positive I don't need these for anything else yet they are preventing me from doing a clean VirtualBox install.
Repaired disk permissions, rebooted, ran uninstall script again, and the next installation was successful.
I was able to clean install 4.3.22-98236-OSX (which I had originally), but upgrading to 4.3.30-101610-OSX OR 5.0.0-101573-OSX would fail and throw an error during installation.
Removing /mach_kernel folder solved the "Failed to install" issue for me.
Related
I have created the VM using GCP Console in browser.
While creating VM, I selected the VM Image as "c2-deeplearning-pytorch-1-8-cu110-v20210619-debian-10". Also, I selected GPU as T4.
VM gets created and started and it shows green icon in browser.
Then I try to connect from "gcloud compute ssh " and it asks if I want to install nVidia Driver and I do Y, then it gives error for lock file and driver is not installed as:
This VM requires Nvidia drivers to function correctly. Installation
takes ~1 minute. Would you like to install the Nvidia driver? [y/n] y
Installing Nvidia driver. install linux headers:
linux-headers-4.19.0-16-cloud-amd64 E: dpkg was interrupted, you must
manually run 'sudo dpkg --configure -a' to correct the problem.
Nvidia driver installed.
I try to verify if driver is installed by running python code as:
import torch
torch.cuda.is_available() #returns False.
Anybody else faced this issue?
This is the correct way to install NVIDIA driver on a GCP instance:
cd /
sudo apt purge nvidia-*
Reboot
cd /
sudo wget https://developer.download.nvidia.com/compute/cuda/11.2.2/local_installers/cuda_11.2.2_460.32.03_linux.run
sudo sh cuda_11.2.2_460.32.03_linux.run
Adjust your config accordingly as it pops options in the terminal
Reboot
Solution to my problem was:
Run manually : sudo dpkg --configure -a
Disconnect from machine.
Connect again using SSH. Select Y again when asked to install nVidia Driver.
It works then.
Make sure you are running as root. I know this sounds silly, but if you use their notebook instances the default user is not root and if you try to ssh into the instance and run something like gpustat etc or run custom code, you might get errors like NVIDIA drivers are not loaded or such.
If you make sure your user (which is called jupyter in the default case) is in the sudoers then all will work fine.
It is often very complicated to install or reinstall GPU drivers on GCP instances. Make sure you actually need to reinstall before you attempt other solutions.
My current installation of Redash is somehow corrupted (installing it in a new PC worked fine so I know my local copy is broken), and I want to basically remove it fully and install it again.
I cannot find any documentation of how to uninstall it,
I don't find it installed as a service
I don't find it installed as a application
So how do I reinstall it???
Deleting the redash installation folder will uninstall the redash but if your installation executable is damaged then reinstalling it again alone might not help.
Check if you have any errors with your supervisor demon:
This supervisor demon is automatically started on port number 9001 on your local machine.
Go to http://127.0.0.1:9001/ and see if all the services/workers are up.
If there are any errors post back the log here.
Check if redash has created dir - /opt/redash/, Remove it if exists.
Run this bash for re-install - https://github.com/getredash/redash/blob/master/setup/ubuntu/bootstrap.sh
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.
error: file /lib/modules/3.14.32-xxxx-grs-ipv6-64/kernel: No such file or directory
This system is not currently set up to build kernel modules (system extensions).
Running the following commands should set the system up correctly:
yum install devel-
(The last command may fail if your system is not fully updated.)
yum install devel
vboxdrv.sh: failed: Look at /var/log/vbox-install.log to find out what went wrong.
error: file /lib/modules/3.14.32-xxxx-grs-ipv6-64/kernel: No such file or directory
This system is not currently set up to build kernel modules (system extensions).
There were problems setting up VirtualBox. To re-start the set-up process, run
/sbin/vboxconfig
as root.
Please try to disable the secure boot option and try to install the virtual box in CentOS. I've also tried the following command with root but it didn't solve the problem. After disabling the secure boot option in bios fixed the problem.
/sbin/vboxconfig
I'm running virtualbox 4.1 on Debian. If I try to start a VM with a bridged NIC I get this error:
error: Failed to open/create
the internal network 'HostInterfaceNetworking-eth0' (you might need to
modprobe vboxnetflt to make it accessible) (VERR_PERMISSION_DENIED).
VBoxManage: error: Failed to attach the network LUN
(VERR_PERMISSION_DENIED) VBoxManage: error: Details: code
NS_ERROR_FAILURE (0x80004005), component Console, interface IConsole,
callee
System: Linux localhost.localdomain 3.2.0-4-amd64 #1 SMP Debian 3.2.54-2 x86_64 GNU/Linux
Virtual Box Version: 4.1.18_Debianr78361
The VM starts with a NAT NIC config.
The weirdest thing is if I export this VM and import it to another user, it works. The other user I tested with was the user I usually use for running auto started virtual machines. But I cant remember doing anything special setting this user up. It is only in its own group and no others. I tried to create a new user and import the VM, but I get the same error as above. I've tried purging virtual box, and completely deleting my conf but it does not work. I just cant figure out what the diff is.
Any help appreciated.
The solution for me was to install virtualbox-4.0 from linux mint. I believe that is actually a downgrade from what in debians repos. Probably packaged different too. Still don't know how the heck I was getting the error I was getting...
sudo apt-get install -f virtualbox-4.0
sudo /etc/init.d/vboxdrv setup