Twitter | Pretraživanje | |
Will Dormann
I'll move to Hyper-V for virtualization on my home computer... Smaller attack surface, and enables the ability to use extra exploit mitigations. 1) Broadcom network driver causes BSODs when Hyper-V bridges a VM to that network. 2) Hyper-V NAT doesn't even provide DHCP. Sigh...
Reply Retweet Označi sa "sviđa mi se" More
Jonathan 26. sij
Odgovor korisniku/ci @wdormann
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.
Reply Retweet Označi sa "sviđa mi se"
Will Dormann 26. sij
Odgovor korisniku/ci @jdgregson
"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??
Reply Retweet Označi sa "sviđa mi se"
Thierry Zoller 🌐 26. sij
Odgovor korisniku/ci @wdormann
Never been able to get it to work. Must be me.
Reply Retweet Označi sa "sviđa mi se"
stuart smiles 26. sij
Odgovor korisniku/ci @wdormann
Virtualbox instead?
Reply Retweet Označi sa "sviđa mi se"
Kyle Erickson 26. sij
Odgovor korisniku/ci @wdormann
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.
Reply Retweet Označi sa "sviđa mi se"
Twirrim 26. sij
Odgovor korisniku/ci @wdormann
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.
Reply Retweet Označi sa "sviđa mi se"