Windows 10: Hyper-V vs VMWare Workstation pains

I have used Hyper-V in the past on Server 2008 some years back and typically used rdp from another machine to access the VM's. I have a lot more experience over the years using VMWare Workstation (ESX too) as well as VirtualBox.

I thought I would give Hyper-V another go when I upgraded my work system to Windows 10 at the end of last year. After finally getting around to enabling Hyper-V and setting up a couple of VM's (Win 7, Win XP, CentOS and Ubuntu) I just could not bring myself to want to change to Hyper-V from VMWare Workstation. My main complaints were the following:

1) Setting up VM's in Hyper-V was more cumbersome and involved more steps to get Linux GUI environments enabled. Maybe I missed something but this is pretty automatic in VMWare workstation while it involved a lot of work after initial Linux installation in Hyper-V. Conclusion - Hyper-V didn't automatically install with GUI enabled for Linux variants. Am I correct or did I just miss something about installation options in Hyper-V?

2) Getting local VM sessions displayed in native monitor resolutions was not apparent to me for Hyper-V. I understand you can also connect locally to the VM via rdp vs opening session from the Hyper-V manager but even then things were not so clear on how to get the native resolutions supported. In contrast VMWare Workstation always figures out the native resolution on completion of the VMWare tools installation at the completion of the VM install process and there is never any time spent screwing around with resolution settings just to open the VM at full screen res. Again is there something I am missing about Hyper-V, it seems like it is really only focused on remote VM sessions in terms of resolution flexibility and local sessions are a hassle to configure/change.

3) Network configuration for Hyper-V is much more complicated, now I don't want to dis Hyper-V here solely for this requirement. I believe there are sound reasons for the network topology used and I was able to create the virtual switches fine, but again it seems like if Hyper-V were considering both local AND remote VM management as target audiences the network topology could be simplified like it is for VMWare Workstation which just create a network connection based on individual choices for individual VM's (NAT, Bridged, etc.) and doesn't require an entire VSwitch based network for the hypervisor environment.

Anyway, just my thoughts. I ask because I have no real reason to want to use another hypervisor environment in lieu of Hyper-V but just can't live with all it's additional tasks and limitations when trying to use it as a local desktop hypervisor to manage multiple VM's on a single machine.

TIA,
-Scott

:)

 

VMware is not working in Windows 10 Home edition due to "Hyper-V role".

I use VMware Workstation Player 14 as a Virtual Machine runner. However, when I try to run a virtual machine, VMware tells me:

VMware Player and Hyper-V are not compatible. Remove the Hyper-V role

from the system before running VMware player.

I know that Windows 10 Home does not have Hyper-V but VMware says it does, and I have not been able to run a virtual machine since.

Can anyone help me?

 

Hyper V or VMWare?


I previously used VMWare Workstation 10 on Windows 8.1 x64.
When I uninstalled VMWare Workstation 10 I found the following:

1. Irreversible changes to Windows 8.1 system setup
2. A huge number

of files and folders left on my system that could not be deleted
I had to format my C:\ drive and re-install Windows 8.1 afresh.

My question now is:
If I install Hyper-V in Windows 10 Pro x64, will take control of my system and make irreversible changes like VMWare Workstation did?

 

Uh-oh! Are Hyper-V Windows 10 and VMware Workstation compatible?


I came across this today and I really did not delve to deeply but is the gist of this right? that if I have VMware Workstation already installed that I am going to run in to problems creating a VM using Hyper V? TIA.

are Hyper-V Windows 10 and VMware Workstation compatible