Oct 26, 2021

Level 23

Any luck running laravel homestead on MacOS Monterey?

When I try to vagrant up I get

Bringing machine 'homestead' up with 'virtualbox' provider... ==> homestead: Checking if box 'laravel/homestead' version '11.5.0' is up to date... ==> homestead: Clearing any previously set forwarded ports... ==> homestead: Clearing any previously set network interfaces... ==> homestead: Preparing network interfaces based on configuration... homestead: Adapter 1: nat homestead: Adapter 2: hostonly ==> homestead: Forwarding ports... homestead: 80 (guest) => 8000 (host) (adapter 1) homestead: 443 (guest) => 44300 (host) (adapter 1) homestead: 22 (guest) => 2222 (host) (adapter 1) ==> homestead: Running 'pre-boot' VM customizations... ==> homestead: Booting VM... There was an error while executing VBoxManage, a CLI used by Vagrant for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "5c2cc9a7-cfba-4b5f-b273-fb8fcf183100", "--type", "headless"]

Stderr: VBoxManage: error: The virtual machine 'homestead' has terminated unexpectedly during startup because of signal 10 VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MachineWrap, interface IMachine

➜ Homestead git:(release)

martinbean

4 years ago

Level 80

@zoransa Nope. I was getting the same error yesterday. I just gave up and installed Sail in my projects.

zoransa

4 years ago

Level 23

OK here is a temporary fix.

In ~/Homestead/Vagrantfile

I added

    config.vm.provider "virtualbox" do |v|
        v.gui = true
    end

before the line:

 Homestead.configure(config, settings)

This results in a visible window of the virtual box that is kind of annoying but it works. Also, there is another bug so use Virtualbox 6.1.26 (not 28) and fix the above homestead server. Those slackers from Vagrant promised to fix it soon.

1 like

zoransa

4 years ago

Level 23

I just realized before you are able to load VirtualBox you need to run extensions:

sudo kextload -b org.virtualbox.kext.VBoxDrv;
sudo kextload -b org.virtualbox.kext.VBoxNetFlt;
sudo kextload -b org.virtualbox.kext.VBoxNetAdp;
sudo kextload -b org.virtualbox.kext.VBoxUSB;

so Vagrantfile turn on GUI, load extensions, and then you should be able to load homestead.

1 like

alejandrozepeda

4 years ago

Best Answer

Level 4

@zoran the following works for me

In Homestead.yaml add gui and update IP:

ip: "192.168.56.10" <----- this
memory: 2048
cpus: 2
provider: virtualbox
gui: true <----- this

Run extensions

sudo kextload -b org.virtualbox.kext.VBoxDrv;
sudo kextload -b org.virtualbox.kext.VBoxNetFlt;
sudo kextload -b org.virtualbox.kext.VBoxNetAdp;
sudo kextload -b org.virtualbox.kext.VBoxUSB;

2 likes

zoransa

4 years ago

Level 23

@alejandrozepeda Precisely thanks for updating. Extensions are not necessary if somehow your installation goes OK and you click Allow to Oracle in Security Preferences. I have no idea why sometimes that thing does not show up. It was uninstalled/installed rebooted several times till I managed to install a virtual box with kernel extensions. IP "quoted" is new. I used Virtualbox 6.1.26 that worked without quotes. Thanks for summarising all in one post. Well deserved best answer.

1 like

talavoock

4 years ago

Level 16

VirtualBox bugs are fixed for macOS Monterey in version 6.1.30. in case if you still are using GUI or have a problem.

I upgraded VirtualBox to 6.1.30 and removed gui: true in homestead.yaml reloaded with vagrant provision and works like a charm.

No need to load kexts or extensions after upgrading.

zoransa

4 years ago

Level 23

@talavoock Yes, it worked, but I got another alert the other day informing me that Oracle corporation inc. is using an old kernel API that will not be supported in further OS releases. I don't know what's another situation with VirtualBox and whether they solved it for M1 processors.

talavoock

4 years ago

Level 16

@zoransa I think the patch(bug fixes) are for Mac intel not sure about M1

Please or to participate in this conversation.