Mac : There was an error while executing `VBoxManage`, a CLI used by Vagrant

▲
8
▼

I am working with aerospike and installing it using vagrant virtual box.

After installation, when i am trying to start the virtual machine, it is giving the following error:

. There was an error while executing VBoxManage, a CLI used by Vagrant for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "dff6693e-52c8-4c9e-922a-243d18c7f666", "--type", "headless"]

Stderr: VBoxManage: error: The VM session was closed before any attempt to power it on VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component SessionMachine, interface ISession

i am using mac machine for this setup.

Any suggestion?

macos
caching
vagrant
virtual-machine
aerospike
asked on Stack Overflow Jan 21, 2019 by KayV

6 Answers

▲
10
▼

Proceeding with the following steps helped me out:

  1. restart the virtual box using:

    sudo "/Library/Application Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh" restart

  2. Stop vagrant as follows:

    vagrant halt

  3. start vagrant as follows:

    vagrant up
answered on Stack Overflow Jan 21, 2019 by KayV
▲
6
▼

Go to settings => security & privacy => general

and allow permission.

answered on Stack Overflow Apr 4, 2020 by Jux Salley • edited Apr 4, 2020 by Basel Issmail
▲
2
▼

Just had the same issue after latest OS update (Big Sur). Steps I had to get through in order to get it working again:

  • Uninstall VirtulBox and reinstall it (it shouldn't delete your VMs)
  • run homestead box update in Homestead directory
  • run sudo "/Library/Application Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh" restart
  • Weirdly enough, followed @Alperen Tahta 's link and restarted laptop after I changed permissions.
  • Vagrant up and tada!

It took me a few steps to get there but I now have my VMs up and ruinning as before.

Hope it helps 👍🏼

answered on Stack Overflow Nov 25, 2020 by daneczech
▲
0
▼

I had the same problem. You can simply restart your system and then restart Vagrant as well. The error majorly occurs when the virtual box was stopped abruptly. Good luck!

answered on Stack Overflow Nov 27, 2019 by Michael Imatitikua • edited Nov 27, 2019 by Shlomo Koppel
▲
0
▼
  1. Open up the VirtualBox GUI and look at "older" items in the VirtualBox Manager.
  2. Remove all the boxes that are written 'inaccessible'
  3. sudo "/Library/Application Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh" restart
  4. vagrant halt
  5. vagrant up
answered on Stack Overflow Sep 21, 2020 by Sboniso Marcus Nzimande
▲
0
▼

For macos you can update privaciy and security permissions.

here is a link: https://medium.com/@Aenon/mac-virtualbox-kernel-driver-error-df39e7e10cd8

answered on Stack Overflow Oct 21, 2020 by Alperen Tahta

User contributions licensed under CC BY-SA 3.0