VBoxManage.exe: error: Unknown option: --host-only-net9=HostOnly

[chan15]

Versions

• Vagrant: 2.3.4
• Provider: Virtualbox 7.0.4

Homestead.yaml

---
ip: "192.168.10.10"
memory: 2048
cpus: 2
provider: virtualbox

authorize: ~/.ssh/id_rsa.pub

keys:
    - ~/.ssh/id_rsa

folders:
    - map: d:/projects
      to: /home/vagrant/code
    - map: d:/www/php
      to: /home/vagrant/php

features:
    - mysql: true
    - mariadb: false
    - postgresql: false
    - ohmyzsh: false
    - webdriver: false

services:
    - enabled:
          - "mysql"

Vagrant destroy & up output

https://gist.github.com/chan15/496a4bf39985381aac77652eda395d52

My homestead branch is on release, I run git pull for the update, when it was done, run init.bat, then run vagrant up --provision, and I got:

VBoxManage.exe: error: Unknown option: --host-only-net9=HostOnly

Before updating the script everything is fine

[svpernova09]

Yeah, there's a lot going on with Virtualbox, see #1815, and #1807.

I pushed a new Homestead version to the release branch, but you should be getting box version issues. I would check out your Homestead branch to 2dad0ce ~ git checkout 2dad0ce3964657d6255235f450e254f4f0e9ea81 Will get you back to the previous release. If that doesn't solve your issues and nothing else matches the above Issues add another post to either one.

[stormtr]

how did you solve this?
VBoxManage.exe: error: Unknown option: --host-only-net9=HostOnly

[chan15]

how did you solve this? VBoxManage.exe: error: Unknown option: --host-only-net9=HostOnly

I comment this part, and it works XD

[tminich]

This was introduced in commit 4b258ed, which breaks completely on windows. It causes op's error and the vm is no longer accessible via the configured IP. Undoing both changes fixes that (Windows 11, VirtualBox 7.0.4).

[chan15]

2dad0ce

It's hard to believe the team released the new version without checking that, it's easy to find out.

[svpernova09]

2dad0ce

It's hard to believe the team released the new version without checking that, it's easy to find out.

It's been incredibly frustrating to deal with VirtualBox :/

[alexhackney]

We appreciate the effort though @svpernova09