The command that is failing is the default headless option for staring VMs via Vagrant. Note the specific error you have posted: There was an error while executing `VBoxManage`, a CLI used by Vagrant The issue seems 100% unrelated to VirtualBox 6.1.28 or even the earlier 6.1.26 since people report the same overall behavior. There is a healthy and detailed thread in the official HashiCorp repo for Vagrant about this: “ Vagrant up issues in Mac OS Monterey #12557” The issue has been solved with the release of VirtualBox version 6.1.30. This is a known issue and seems to be related to VirtualBox version 6.1.28. Uninstalling VirtualBox 6.1.28 and downgrading to VirtualBox 6.1.26.īut no matter what I do, the same error pops up.Made sure to reboot my MacBook Air to get the kernel extensions loaded again.Uninstalling VirtualBox and reinstalling it again.Uninstalling Vagrant and reinstalling it again.

I am using Vagrant 2.2.18 and VirtualBox 6.1.28 and I tried everything I have done in the past for cases like this to no avail. VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MachineWrap, interface IMachine Stderr: VBoxManage: error: The virtual machine 'Sandbox (CentOS 7)' has terminated unexpectedly during startup because of signal 10 The command and stderr is shown below.Ĭommand: I just upgraded my Intel-based MacBook Air (Retina, 13-inch, 2020) to macOS Monterey (12.0.1) - previously was using macOS Big Sur (11.6.1) - and while everything seems fine, I am getting this odd error when attempting to run vagrant up: There was an error while executing `VBoxManage`, a CLI used by Vagrantįor controlling VirtualBox.

Vagrant up provider virtualbox