Forum Discussion
Hyper-V Default switch IP address range change. Ver 1809 Build 17763.1
It's good to know that it's working out for you, unfortunately I don't much experience with Vagrant myself but I think this is a great feedback that you provided about Hyper-V and Vagrant incompatibility over the default switch, I think Microsoft can fix this with Vagrant just like they cooperate with VMWare to make compatible features, I would definitely up vote it if you post it in the uservoice or Feedback Hub.
Thanks again, have a good one!
I realize that many of us have differing use-cases; some of us are software developers using Vagrant who want internal IP addresses, some of us are systems admins using Windows Server who want external IP addresses, and some of us are adamant about using the Default Switch whereas some of us don't care what switch we use as long as its IP address doesn't change.
For those who share my specific use-case (i.e., using Vagrant and impartial to the Default Switch), I wrote a comprehensive How-To, which you may find helpful:
https://superuser.com/a/1379582/176764
Hopefully, Vagrant and Microsoft can work together to eliminate all the hoop-jumping!
- Good points
I don't have time to list everything I've noticed, but I'll give you a couple of networking examples.
In VMware both the NAT and host-only networks have a virtual DHCP server that's configurable.
Another example is in VMware a bridged virtual adapter can be set to automatically select a physical adapter to bridge...so if you are developing on a laptop it will automatically switch between wifi and ethernet.
- Could you name some of those missing capabilities that you're talking about?
for me the Only capabilities that Hyper-V is missing is tabbed VM session viewing, when working with multiple VMs at the same time. but that's the nature of it because of RDP and there are programs that have tabbed RDP session feature. - In my case, the only reason I'm trying to use Hyper-V now is that it's required if you want to user Windows containers / Docker Desktop on Windows 10. I'd much prefer to still be using VMware Workstation, but unfortunately VMware and Hyper-V can't co-exist (yet). So I've bitten bullet and moved to Hyper-V. I'm honestly really surprised how far behind Hyper-V is in capabilities and flexibility compared to VMware Workstation given how long Hyper-V has been around.
- I'm wondering, The default switch has only been with us for 2 years now, it's fairly new, so what were the Vagrant users using before Default switch was even introduced?
Hyper-V itself is not new and people have been using it for Years, when it didn't have Default switch, but suddenly 2 years ago Microsoft introduced it for users with no networking experience and then all the professionals decides to use it too.
so yeah I'm wondering why not do the same thing that they were before Default switch was even in Hyper-V.
