Virtualbox (Headless) No Longer Work Running macOS 12.0.1 Monterey

Anyone figured out a work around for running Homestead via Vagrant using Virtualbox on Monterey?

It's crazy how this was missed when it was released. I can't tell if it's a Virtualbox issue or Apple issue.

Either way, I was only able to get the virtualbox to run as a GUI, not headless.

MacBook Pro 16″, macOS 12.0

Posted on Nov 4, 2021 1:06 PM

Similar questions

Unable to run Virtualbox after updating to macOS Mojave I had a problem with my location service in my macOS Mojave, so I decided to reset and successfully reset my macbook, but here is where problems begin. I was unable to install Oracle Virtualbox. I also tried entering into security and privacy and to allow the system extension, but it does not show any options to allow them. I have reset my mac several times, but no use. The location service issue is also not solved yet, that is a different discussion but. I tried reseting my mac to older version of OS X (El Captian), virtualbox worked flawlessly, now I am in macOS Mojave. It is not working. Kindly help me out.
3760 15
Virtualbox What is people's experience with Virtualbox? i had problems with Parallels. Too bad Bootcamp is not available on the M1 MacBook Pro.... Thank you so much, Anita
417 2
how to run amd based virtual machine in m2? I am trying to create 5/6 amdX64-based VM on my Mac chip using Vagrant, but it is not working. govinda at Govindas-MacBook-Pro-2 in ~/Documents/programming/kubernetes/kubernetes-hardway/kubernetes-the-hard-way/vagrant (master) $ vagrant up Bringing machine 'master-1' up with 'virtualbox' provider... Bringing machine 'master-2' up with 'virtualbox' provider... Bringing machine 'loadbalancer' up with 'virtualbox' provider... Bringing machine 'worker-1' up with 'virtualbox' provider... Bringing machine 'worker-2' up with 'virtualbox' provider... ==> master-1: Box 'ubuntu/jammy64' could not be found. Attempting to find and install... master-1: Box Provider: virtualbox master-1: Box Version: >= 0 ==> master-1: Loading metadata for box 'ubuntu/jammy64' master-1: URL: https://vagrantcloud.com/ubuntu/jammy64 ==> master-1: Adding box 'ubuntu/jammy64' (v20230712.0.0) for provider: virtualbox master-1: Downloading: https://vagrantcloud.com/ubuntu/boxes/jammy64/versions/20230712.0.0/providers/virtualbox.box Download redirected to host: cloud-images.ubuntu.com ==> master-1: Successfully added box 'ubuntu/jammy64' (v20230712.0.0) for 'virtualbox'! ==> master-1: Importing base box 'ubuntu/jammy64'... ==> master-1: Matching MAC address for NAT networking... ==> master-1: Setting the name of the VM: kubernetes-ha-master-1 Vagrant is currently configured to create VirtualBox synced folders with the `SharedFoldersEnableSymlinksCreate` option enabled. If the Vagrant guest is not trusted, you may want to disable this option. For more information on this option, please refer to the VirtualBox manual: https://www.virtualbox.org/manual/ch04.html#sharedfolders This option can be disabled globally with an environment variable: VAGRANT_DISABLE_VBOXSYMLINKCREATE=1 or on a per folder basis within the Vagrantfile: config.vm.synced_folder '/host/path', '/guest/path', SharedFoldersEnableSymlinksCreate: false ==> master-1: Clearing any previously set network interfaces... ==> master-1: Preparing network interfaces based on configuration... master-1: Adapter 1: nat master-1: Adapter 2: hostonly ==> master-1: Forwarding ports... master-1: 22 (guest) => 2711 (host) (adapter 1) master-1: 22 (guest) => 2222 (host) (adapter 1) ==> master-1: Running 'pre-boot' VM customizations... ==> master-1: Booting VM... ==> master-1: Waiting for machine to boot. This may take a few minutes... master-1: SSH address: 127.0.0.1:2222 master-1: SSH username: vagrant master-1: SSH auth method: private key master-1: Warning: Connection reset. Retrying... The guest machine entered an invalid state while waiting for it to boot. Valid states are 'starting, running'. The machine is in the 'aborted' state. Please verify everything is configured properly and try again. If the provider you're using has a GUI that comes with it, it is often helpful to open that and watch the machine, since the GUI often has more helpful error messages than Vagrant can retrieve. For example, if you're using VirtualBox, run `vagrant up` while the VirtualBox GUI is open. The primary issue for this error is that the provider you're using is not properly configured. This is very rarely a Vagrant issue.
1854 7

3 replies

VikingOSX

Level 10

123,290 points

Nov 4, 2021 1:10 PM in response to iTimC21

First of all, Virtualbox does not support any macOS host after Catalina per their documentation. They only support Intel hardware for macOS. If you got it working on Monterey as a GUI, it is not supported by Oracle for this operating system.

VikingOSX

Level 10

123,290 points

Nov 4, 2021 1:19 PM in response to iTimC21

At a minimum, you need the latest release of Parallels 17.* for Monterey.

iTimC21 Author

Level 2

193 points

Nov 4, 2021 1:14 PM in response to VikingOSX

Fair enough, I also wasn't able to get Parallels to work with Homestead either. Those are the only two apps that Laravel recommends to use Homestead. I guess I can't use this anymore.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Virtualbox (Headless) No Longer Work Running macOS 12.0.1 Monterey