VirtualBox failed to initialize after an upgrade to OSX Big Sur 11.4
Failed to open a session for the virtual machine xxx.
The virtual machine 'xxx' has terminated unexpectedly during startup with exit code 1 (0x1).
Result Code: NS_ERROR_FAILURE
The following step resolved the problem:
sudo csrutil clear
followed by a reboot
The reboot took a long time.
Note that I did not need to uninstall or reinstall VirtualBox, like this related problem
Related
After installing openSUSE-2022-10067 Security update for virtualbox, I got the following error when trying to start a guest vitural machine: Failed to open a session for the virtual machine. Result Code NS_ERROR_FAILURE (0x80004005) Component: SessionMachine Interface: ISession{c0447716-ff5a-4795-b57a-ecd5fffa18a4}
Details: The VM Session was aborted.
I had above errors with MS Win-10 and Opensuse Leap 15.4 Guest VM's on a Open Suse Leap 15.4 VM-Host-System.
Anybody experiances the same issue?
My temporary solution was to rollback the snapshot to pre-installation of the security update for virtualbox. Then it was possible to start the VM's without any errors again.
I think I've seen a similar crash when trying to start a VM with the combination of VirtualBox 6.1.35 and 6.1.36 in combination with the VirtualBox Extension Pack (EP) 6.1.34. Did you also upgrade the EP? ;)
This solves my problem in VirtualBox 6.1.36
With 6.1.35 I could not even update the EP without running in the same error.
Hope this helps.
BR Markus
I am trying to launch two VMs using docker machine:
docker-machine create --driver virtualbox myvm1
docker-machine create --driver virtualbox myvm2
I see the following error in the output:
(myvm2) Progress state: NS_ERROR_FAILURE
(myvm2) VBoxManage: error: Failed to create the host-only adapter
(myvm2) VBoxManage: error: VBoxNetAdpCtl: Error while adding new interface: failed to open /dev/vboxnetctl: No such file or directory
(myvm2) VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
(myvm2) VBoxManage: error: Context: "RTEXITCODE handleCreate(HandlerArg *)" at line 94 of file VBoxManageHostonly.cpp
(myvm2)
(myvm2) This is a known VirtualBox bug. Let's try to recover anyway...
Error creating machine: Error in driver during machine creation: Error setting up host only network on machine start: The host-only adapter we just created is not visible. This is a well known VirtualBox bug. You might want to uninstall it and reinstall at least version 5.0.12 that is is supposed to fix this issue
I installed the latest version of VirtualBox (6.0.0) from there. When I open VirtualBox window and click on the VMs in the left panel I get the following error popup:
UPDATE
I tried to re-install VirtualBox 6.0.0 and in the end of the VirtualBox installation process I saw the following screen:
Maybe it is a reason of the failures described above? My mac is running on 10.14.1 macOS Mojave
How can I fix these errors?
You probably need to approve the VirtualBox kernel extension in System Preferences under Security & Privacy:
After you allow the kernel extension, the installer should be able to run successfully.
The (rc=-1908) usually happens when the secure boot is enable, try to disable and run your vm again
Secure Boot settings are available in Startup Security Utility:
Turn on your Mac, then press and hold Command (⌘)-R immediately after you see the Apple logo to start up from macOS Recovery.
When you see the macOS Utilities window, choose Utilities > Startup Security Utility from the menu bar.
When you're asked to authenticate, click Enter macOS Password, then choose an administrator account and enter its password.
Select "No security" option
I got this exact error after upgrading my Mac to Monterey. Remove Virtualbox and reinstall solves the problem.
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
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.
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