3 ms·

Hyper-V user here. It's fine - I run 12-15 VMs (4 of which are Linux) at a time (full production environment with virtual networking) on a 4 year old Dell T3500

by bananas 13y ago

Hyper-V user here. It's fine - I run 12-15 VMs (4 of which are Linux) at a time (full production environment with virtual networking) on a 4 year old Dell T3500 Quad Xeon with 32Gb of RAM. Sounds like your hardware is broken/crap.

tanzam75 13y ago
Hardware problem often means driver problem. When you have Hyper-V installed, you have to be exceptionally careful about what drivers you have installed. I've even seen a Bluetooth driver bluescreen the management OS when Hyper-V was enabled. This is just the nature of hypervisors. Most drivers are only tested on an OS that's running directly against the hardware. Run them through a hypervisor, and their behavior becomes unpredictable. Ultimately, Hyper-V is a hypervisor, and it competes against ESX -- not VMWare Workstation. That's why it's best run on workstation-class or server-class hardware. Basically, situations where the hardware vendor might actually keep the drivers up-to-date. On consumer-level hardware, it's a crapshoot.
- bananas 13y ago
  Yeah which is why if you're doing serious shit with Windows you buy either: 1. Thinkpad T or W series 2. Dell Precision 3. HP Z-series. Nothing else is worth throwing any money at all unless it's for facebook or pr0n usage (consumer).
vetinari 13y ago
On server, it is fine. On notebook? Trying to combine Hyper-V (for WP dev) and Intel HAXM (for Android dev) is BSOD nightmare. It stopped after I got rid of Hyper-V...
- yuhong 13y ago
  I think there is a BCD option to disable Hyper-V. You could have two boot menu options.
- bananas 13y ago
  It's fine on a notebook too. More than one hypervisor per machine is not a good idea. You'll get the same problem with Intel HAXM and VMware as well. To be fair the problem with this is that the whole Intel virtualization architecture is hacked on the side (as is every other damn feature since the 80186).

by bananas 13y ago

tanzam75 13y ago

Hardware problem often means driver problem. When you have Hyper-V installed, you have to be exceptionally careful about what drivers you have installed. I've even seen a Bluetooth driver bluescreen the management OS when Hyper-V was enabled. This is just the nature of hypervisors. Most drivers are only tested on an OS that's running directly against the hardware. Run them through a hypervisor, and their behavior becomes unpredictable. Ultimately, Hyper-V is a hypervisor, and it competes against ESX -- not VMWare Workstation. That's why it's best run on workstation-class or server-class hardware. Basically, situations where the hardware vendor might actually keep the drivers up-to-date. On consumer-level hardware, it's a crapshoot.

bananas 13y ago
Yeah which is why if you're doing serious shit with Windows you buy either: 1. Thinkpad T or W series 2. Dell Precision 3. HP Z-series. Nothing else is worth throwing any money at all unless it's for facebook or pr0n usage (consumer).

vetinari 13y ago

On server, it is fine. On notebook? Trying to combine Hyper-V (for WP dev) and Intel HAXM (for Android dev) is BSOD nightmare. It stopped after I got rid of Hyper-V...

yuhong 13y ago
I think there is a BCD option to disable Hyper-V. You could have two boot menu options.
bananas 13y ago
It's fine on a notebook too. More than one hypervisor per machine is not a good idea. You'll get the same problem with Intel HAXM and VMware as well. To be fair the problem with this is that the whole Intel virtualization architecture is hacked on the side (as is every other damn feature since the 80186).