System environment
macOS catalina(10.15)virtualbox version: 6.0.14 r133895
Problem description
After upgrading the old version of VirtualBox 5 to VirtualBox 6.0, the following error is found in docker-machine start
➜ ~ docker-machine start
Starting "default"...
(default) Check network to re-create if needed...
Unable to start the VM: /usr/local/bin/VBoxManage startvm default --type headless failed:
VBoxManage: error: The virtual machine 'default' has terminated unexpectedly during startup with exit code 1 (0x1)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MachineWrap, interface IMachine
Details: 00:29:32.593106 Console: Machine state changed to 'PoweredOff'
found that all Vbox virtual machines could not start, the reason should be the same
. Then I remembered that I once had the permission to change some system directory (or users), whether I changed the installation path of VirtualBox
solution
- because I’m not sure the original
/Application/VirtualBox. App what permissions, so the uninstall tools perform VirtualBox installation image will be installed version completely uninstall, and then reassembled, found after heavy users and user groups is root: admin , but start still have the same error for help online, watch some, not installed corresponding enhanced version of the tools expansion pack, So I went to the official website to download the enhancement package and install it. When installing the package, an error was reported: 
then found that although The error type was The same, this time it was reported for a different reason: VBoxExtPackHelperApp: error: The owner is not root: /Applications. Now I remember that I once changed The /Application directory to a normal user in order to test a certain program and forgot to change it back... Really dug a pit pit themselves so /Applications by users and groups in the root: wheel , to perform the installation of the expansion pack, installation is not an error, guess is probably because when the user is not the root cause in the installation directory belong to unable to perform a specific system commands (such as virtual machine driver installation ) expansion pack, after the success of the installation, open the virtual machine again, found that already can start, The problem has been fixed here. summary
- do not eat too full to have nothing to modify the system directory permissions (including the users) encounter problems can be Internet help, and then for each possible useful scheme to try one by one
Read More:
- VirtualBox failed to start, prompt failed to open a session for the virtual machine windoze 7
- virtualbox Failed to load VMMR0.r0 (VERR_SUPLIB_OWNER_NOT_ROOT)
- Modify the VDI path of VirtualBox on MacOSX, and transfer the virtual machine
- System and host port mapping under virtualbox
- VBoxManage.exe: error: Failed to create the host-only adapter
- An error is displayed when virtualbox uses modifyhd command to expand capacity: Resize medium operation for this format is not implemented yet
- VBoxManage.exe: error: Resize hard disk operation for this format is not implemented yet!
- Failed to create VirtualBox client com
- Error of oracel VM installing Windows Server 2012
- Virtualbox failed to attach usb, VERR_PDM_NO_USB_PORTS problem solved
- [solved] genymotion, “unable to load VirtualBox engine”
- VirtualBox problem solving set -[drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send host log message
- Error ns when starting VirtualBox virtual machine after upgrading kernel_ ERROR_ FAILURE
- Vacuum box installation CentOS encountered the pit
- Shortcut to exit zoom mode in VirtualBox [off]
- The seahorse play simulator failed to start, start machine failed! error code = 3 and error code = 21
- VirtualBox start error NS_ ERROR_ FAILURE (0x80004005)
- Open virtuakbox and failed to acquire the VirtualBox com appears object.The application will now terminate.
- VirtualBox + CentOS 7 virtual machine setting static IP address of host only NIC
- Record of solutions to internal error when VMware starts virtual machine