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. I tried reinstalling both Vagrant and Virtualbox but no luck. VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MachineWrap, interface IMachine

Stderr: VBoxManage: error: The virtual machine 'vm_default_1635193007482_74329' has terminated unexpectedly during startup because of signal 10 The command and stderr is shown below.Ĭommand: There was an error while executing `VBoxManage`, a CLI used by Vagrantįor controlling VirtualBox. => default: Running 'pre-boot' VM customizations. => default: Preparing network interfaces based on configuration.ĭefault: 80 (guest) => 3000 (host) (adapter 1)ĭefault: 22 (guest) => 2222 (host) (adapter 1) => default: Clearing any previously set network interfaces. => default: Clearing any previously set forwarded ports. => default: Checking if box 'tynesolutions/ruby-node-redis-mysql-ubuntu' version '2.0.0' is up to date. I upgraded my Mac to Monterey today, and now I get the following error when I run vagrant up Bringing machine 'default' up with 'virtualbox' provider.

Macos 12 virtualbox