I lost about a day trying to figure out why my Vagrant file wasn’t working. It would hang at the point where it was waiting for the Hyper-V VM IP address.
Lots of debugging later …
Then I noticed the VM was getting the same IP address as my host. That explained all the weird networking problems I was having too!
Note that most WiFi adapters CANNOT host multiple IP’s on them (there’s more detail here, but that’s the TLDR). What that means is that if you connect your new VM to any switch that’s bridged to a WiFi adapter, the VM will get the IP address of your host. That causes a lot of problems.
Ironically, I believe it was working fine for me at another location, but I had Ubiquity WiFi access points there; maybe they have more capabilities than an eero WiFi extender?
Also, I had an internal network that ALSO did not work. I had to use the “Default Network” for the bridge name to get Vagrant to function and for an internal IP to work.
No doubt if I was using some host pass throughs, it would have worked, but I was trying to essentially do a local version of running an AWS or Azure VM, so I didn’t want any host port mapping going on as that wouldn’t usually work with a cloud VM.
Just wanted to post this in case someone else had a problem getting Vagrant to create VMs with HyperV bridged to a WiFi connect.