Installation of El Capitan within VM is very slow - virtualbox

I created a bootable ISO image by following guide of osx-vm-templates. And then I create a new VM and configured it to boot from the ISO image in VirtualBox, I get a workable OSX VM at the end.
But the installation process takes about 2 hours to complete, why?

The box I'm using for creating VM runs Server.app, the installation process now cause about 40 minutes after I removed Server.app.

Related

Can not find NVIDIA driver after stop and start a deep learning VM

[TL;DR] First, wait for a couple of minutes and check if the Nvidia driver starts to work properly. If not, stop and start the VM instance again.
I created a Deep Learning VM (Google Click to Deploy) with an A100 GPU. After stopping and starting the instance, when I run nvidia-smi, I got the following error message:
NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running.
But if I type which nvidia-smi, I got
/usr/bin/nvidia-smi
It seems the driver is there but can not be used. Can someone suggest how to enable NVIDIA driver after stopping and starting a deep learning VM? The first time I created and opened the instance, the driver is automatically installed.
The system information is (using uname -m && cat /etc/*release):
x86_64
PRETTY_NAME="Debian GNU/Linux 10 (buster)"
NAME="Debian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
I tried the installation scripts from GCP. First run
curl https://raw.githubusercontent.com/GoogleCloudPlatform/compute-gpu-installation/main/linux/install_gpu_driver.py --output install_gpu_driver.py
And then run
sudo python3 install_gpu_driver.py
which gives the following message:
Executing: which nvidia-smi
/usr/bin/nvidia-smi
Already installed.
After posting the question, the Nvidia driver starts to work properly after waiting for a couple of minutes.
In the following days, I tried stopping/starting the VM instance multiple times. Sometimes nvidia-smi directly works, sometimes does not after >20 min waiting. My current best answer to this question is first waiting for several minutes. If nvidia-smi still does not work, stop and start the instance again.
What worked for me (not sure if it will go well to next starts) was to remove all drivers: sudo apt remove --purge '*nvidia*', and then force the installation with sudo python3 install_gpu_driver.py.
In the install_gpu_driver.py, change line 230 to return False inside of the check_driver_installed function. Then, run the script.
Who uses docker may face this error docker: Error response from daemon: could not select device driver "" with capabilities: [[gpu]] and have to reinstall the docker too. This thread helped me.

How can I get Raspbian running in VirtualBox?

I'm trying to set up a Raspbian image in VirtualBox 6.1.14 for development. I downloaded the latest .iso from the RPi website, and set up a VirtualBox machine with the OS set to Debian (32-bit). When I mount the .iso and start the machine, I'm able to get through all the installation steps until it gets to the point of configuring the package manager--at that point it freezes in both the text installer and the GUI installer.
I've tried doing this with the network adapter enabled and disabled, which made no difference. Is there a specific configuration to the VM that will get the installation to work?
I am a dum dum. I needed to up the memory on the VM. Below are the pertinent stats for it to work.
OS: Debian (32-bit)
Base Memory: 1024mb
Video Memory: 128mb
Graphics Controller: VMSVGA
Storage: 8gb

VMWare player does not detect GParted live CD iso file

I have a VMWare Player virtual machine where I am trying to change partitions of my Windows 7 VM hardrive using GParted. I downloaded a GParted live CD from here. I tried this with both *-i686 and *-amd64 versions.
The problem is that VMWare Player VM does not detect the bootable ISO at all. I added the ISO file like this. When I run the VM and check its setting then CD/DVD (SATA) has a checkmark next to it so I presume it is connected. But the ISO is nowhere to be found when I try to change boot order in PhoenixBIOS. So I cannot run GParted to change partitions.
I´ve already checked that both *-i686 and *-amd64 ISO files are bootable with MagicISO.
Has anyone dealt with this? I´ve tried both my Windows 7 VM and Ubuntu VM. In both I went into PhoenixBIOS and results were the same.

Openstack dashboard gives error "Error: Unable to retrieve usage information"

I installed OpenStack on an ec2 instance running Ubuntu 14.04 LTS via devstack. When I login into the dashboard I get an error "Error: Unable to retrieve usage information"
When I installed it and logged in for the first time, everything was working fine. But after I stopped my ec2 instance and restarted, I am facing this problem.
What might be causing this error?
I used the stable juno version of devstack.
And the AMI for my ec2 instance is Ubuntu Server 14.04 LTS (HVM), SSD Volume Type.
Does restarting the instance might have caused some problem?
cd to devstack and execute ./rejoin-stack
That solved it. I was trying to reboot nova and other services individually.
But since the installation was done using devstack, you need to run the ./rejoin-stack script.
In addition to [akshay1188] answer, you can re-stack your system. Sometimes, rejoin-stack does not work as expected. In that case, you can unstack (unstack.sh) it and stack (stack.sh) again. *This may take much time.
Another observation of mine says this can be an issue with IP address of the system. Try to keep IP address same after reboot.

Can't start VM in Virtualbox after update

I just updated virtualbox to the latest 4.1.16 r78094 and realized that I can no longer start my virtual machines.
If I start a VM, the error displayed is:
Failed to open a session for the virtual machine Historical Image.
Failed to load VMMR0.r0 (VERR_NO_MEMORY).
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: Console
Interface: IConsole {1968b7d3-e3bf-4ceb-99e0-cb7c913317bb}
I have 8GB RAM in my VM host which is running OSX 10.6 of which I have over 4GBs free. Does anyone know how I can get my VMs working again?
It is a well known issue and at the moment you have two options:
install new version from http://download.virtualbox.org/virtualbox/4.1.18/VirtualBox-4.1.18-78361-OSX.dmg
downgrade your version to previous one: https://www.virtualbox.org/wiki/Download_Old_Builds_4_1