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??
- Još 1 odgovor
Novi razgovor -
-
-
Never been able to get it to work. Must be me.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Virtualbox instead?
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
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.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
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.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.