I have a large number of VMs created using Vagrant. Everything worked fine on Big Sur 11.5, but after the upgrade to 11.6, I can no longer access the VM with the IP of the secondary host-only network adapter (created using the 'private_network' type in Vagrant, with a static IP address) in any way: it won't respond to pings, and no network services (e.g. nginx) respond from that IP.
I can still SSH to the running VM through 127.0.0.1 and the SSH port mapping (host 2222 -> guest 22) created by Vagrant.
Here's the output of ip addr inside the VM:
Code: Select all
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 08:00:27:73:60:cf brd ff:ff:ff:ff:ff:ff
inet 10.0.2.15/24 brd 10.0.2.255 scope global dynamic eth0
valid_lft 81203sec preferred_lft 81203sec
inet6 fe80::a00:27ff:fe73:60cf/64 scope link
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 08:00:27:92:3a:ce brd ff:ff:ff:ff:ff:ff
inet 192.168.201.20/24 brd 192.168.201.255 scope global eth1
valid_lft forever preferred_lft forever
inet6 fe80::a00:27ff:fe92:3ace/64 scope link
valid_lft forever preferred_lft forever
* eth1 is Adapter 2, a Host-only Adapter on vboxnet25. The IP address 192.168.201.20 is set in the Vagrantfile.
* Both have Cable Connected checked.
Nothing about the VirtualBox or Vagrant configuration has changed after the 11.6 upgrade. I tried uninstalling and reinstalling VirtualBox and the Extension pack, rebooting multiple times, as well as destroying and recreating the VM.
Here's the output of kextstat, showing that the VirtualBox kexts seem to be loaded just fine:
Code: Select all
Index Refs Address Size Wired Name (Version) UUID <Linked Against>
199 3 0xffffff7f9cc6d000 0xb3000 0xb3000 org.virtualbox.kext.VBoxDrv (6.1.28) 2322A451-8E64-3434-9126-8297421A36D4 <8 6 5 3 1>
201 0 0xffffff7f9cd4c000 0x5000 0x5000 org.virtualbox.kext.VBoxUSB (6.1.28) F38BE5D7-048C-3EC2-82FD-0C02F9E9CCF5 <200 199 62 8 6 5 3 1>
202 0 0xffffff7f9cd47000 0x4000 0x4000 org.virtualbox.kext.VBoxNetFlt (6.1.28) 5D62FC0B-F37D-3D34-BF4A-C564FFFFD27D <199 8 6 5 3 1>
203 0 0xffffff7f9cd41000 0x2000 0x2000 org.virtualbox.kext.VBoxNetAdp (6.1.28) 090DCE04-5E98-34F0-A2C0-06669D0E498C <199 6 5 1>
Nothing in the output of the vagrant command has changed. It's not indicating any kind of problem conditions, and both interfaces do receive their IP addresses, so I'm believing this is some kind of issue between VirtualBox and Big Sur 11.6.
If I can provide some other types of logs or debugging information, please advise how to get them, and I'll post them.