Error: vmnet_start_interface returned 1001 (VERR_INVALID_PARAMETER)

[JoelProminic]

@feather812002 reported this error when creating a new demo-tasks 0.1.20/22 instance with Super.Human.Installer:

Command: ["startvm", "68235e6c-5deb-4b86-81f0-1b19cba10ea6", "--type", "headless"]

Stderr: VBoxManage: error: Error: vmnet_start_interface returned 1001 (VERR_INVALID_PARAMETER).
VBoxManage: error: Failed to attach the network LUN (VERR_INVALID_PARAMETER)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole
[SHI]: 'vagrant up' stopped with exit code: 1, elapsed time: 00:00:55
[SHI]: Server destroyed

[JoelProminic]

This problem ended up being caused by host-only networks on macOS Ventura. Here is my writeup

I found this error message reported as an issue in the vagrant repository.

It seems like this is an issue with Host-Only Networks. Here is a suggested solution:
hashicorp/vagrant#12959 (comment)
hashicorp/vagrant#12959 (comment)
hashicorp/vagrant#12959 (comment)

The solution was to create new host-only network like this: NOTE: update this to match your network configuration

   VBoxManage hostonlynet add --name=HostOnly --netmask=255.255.255.0 --lower-ip=192.168.56.1 --upper-ip=192.168.56.100 --enable

And then add it to the Vagrantfile like this. However I'm not sure if this will work as-is with the Ansible scripts

   # Hack for MacOS Ventura - HostOnly network should exist under virtualbox
   v.customize ["modifyvm", :id, "--nic2", "hostonlynet", "--host-only-net2=HostOnly"]

This was supposed to be fixed in Vagrant 2.3.3, but @feather812002 is already on 2.4.0.

@feather812002 confirmed that this fix worked with Super.Human.Installer Development v0.9.7. (There were remaining issues that we were already investigating).

To check if you have already created the hostonlynet entry (or do cleanup/changes - see modify and remove subcommands), look for this section in ~/Library/VirtualBox/VirtualBox.xml:

      <HostOnlyNetworks>
        <HostOnlyNetwork name="HostOnly" .../>
      </HostOnlyNetworks>

I created this issue as a reference in case more people have this problem. If it becomes a common issue, we can considering adding logic to support it in Super.Human.Installer.