I use Hyper-V for desktop virtualization as well. I've never had any BSODs, but virtual networks and default switches not providing DHCP is an occasional and very annoying problem. If you do continue down this road I can share my usual troubleshooting steps which sometimes help.
-
-
-
"Occasional"? Best I could find is that NAT is something that you can manually add to Hyper-V via PowerShell. And even then that it doesn't provide DHCP. I'm currently running my VM with a static IP on the NAT network that I manually created. There's an easier way??
- 1 more reply
New conversation -
-
-
Never been able to get it to work. Must be me.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Virtualbox instead?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Do you happen to have Internet Connection Sharing disabled via group policy? Last I tried the default switch with Win10v1809 it did do DHCP, NAT, etc., but I had to allow ICS for it to function. Regardless the experience is poor and I typically just bridge the VMs.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Broadcom SR-IOV can be a big pain. Paravirtualized is more stable, in my experience. (haven't experimented with Hyper-V). I do hear that it's important to be fully up to date with Broadcom NICs for virtualisation.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.