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 NS_ERROR_FAILURE (0x80004005)
- VirtualBox start error NS_ ERROR_ FAILURE (0x80004005)
- Error ns when starting VirtualBox virtual machine after upgrading kernel_ ERROR_ FAILURE
- Record of solving the failure of installing ie11 (9c59) under 64 bit Windows 7 system
- VirtualBox problem solving set -[drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send host log message
- Spring boot problem solving record (1)
- Failed to load resource: net::ERR_ INSECURE_ Response problem solving record
- To solve the problem of “failed to load vmmr0. R0” (Verr) of VirtualBox under Mac OS X_ SUPLIB_ WORLD_ Writable) “error
- Error lnk1123: failure during conversion to coff: problem solving
- Failed to connect to 127.0.0.1 port 43571: problem solving record
- Under win864 bit, install python, PyQt4 and sip. (final failure, only record)
- OSD deployment failure code (0x00000001) 0x80004005
- A problem occurred configuring project ‘:x x x‘. ＞ java.lang.NullPointerException (no error message)
- Virtualbox failed to attach usb, VERR_PDM_NO_USB_PORTS problem solved
- Error in installing RVM on MacOS raw.githubusercontent.com:443 Connection failure resolution
- Commandinvocationfailure: failed to build APK problem record
- Solving failure executing javac, but could not parse the error
- How to Solve MacOS Big Sur MySQL workbench flashback problem
- [DRC nstd-1] problem solving of vivado error problem
- VirtualBox Failed to start LSB:Bring up/down Networking problem