lx07 said:
You can always run an emulator. You mean hypervisor. You may think this is a trivial point put there is a major difference between an emulator and a hypervisor. An emulator converts CPU instructions in the guest into the structure the underlying CPU understands. Virtualisation is not the same - it uses the hardware directly. Virtualisation is much faster than emulation. Apart from hobby projects emulation really isn't used these days although you can emulate a Nintendo DS on Windows if you want - see here Windows Emulators Software - SourceForge.net

After that there is also a difference between a type 1 and type 2 hypervisor. This is in fact why VirtualBox will work in 32bit mode but not 64 when another is running. With a Type 1 (like Hyper-V or ESXi) there isn't an underlying OS running. When you enable Hyper-V role your Windows is a VM. Type 1 and Type 2 Hypervisors Explained -- Virtualization Review. This is in fact why your networking speed can reduce when turning enabling Hyper-V role as the hypervisor assumes you want to share.

To what? In what sense? Are you saying Hyper-V is better for Enterprise than ESXi or ZEN? It isn't the most popular for sure. Or are you saying it is better for a home user (even though VMWare works better for Linux as you admit).

It has a few advantages for a home user (mainly auto suspend restart) but superior it is not. It isn't faster than VMWare and isn't as generic as VBox. Perhaps you mean "free if you have Pro".
Yeah - terms were a bit slack. It is a bit more subtle as you can install android emulators which will not run if the hyper-v hypervisor is running.

Really I was just comparing hyper-v with vmware/vbox for average domestic user. IMO Hyper-V is superior in enhanced mode but can be inferior in basic mode due to sound issue.

I have done performance tests with Vmware and hyper-v and hyper-v easily out performed vmware. Maybe that was a function of my device, but imo it was no contest.

Of course, if a Home user it is irrelevant as it cannot run hyper-v.

I also personally prefer hyper-v as it uses vhdx files which can be attached as a host boot or hyper-v guest boot. I like to use a vhdx for testing Insider versions but prefer to run on host pc as faster than in a vm. Only annoying thing is you cannot do build upgrades in a vhdx on host, so I attach vhdx as a vm, do build upgrade, and then reattach vhdx as a host boot. It is not that easy to do same with vmware (I know yiu can mess around with macrium images etc to same end but more hassle).

I do use vmware now and then, but as a rule, I find hyper-v slicker but to be fair, it is less intuitive for beginners but @Kari's guides are how I got off the ground.