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.ģ) Network configuration for Hyper-V is much more complicated, now I don't want to dis Hyper-V here solely for this requirement. 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. 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.

Am I correct or did I just miss something about installation options in Hyper-V?Ģ) Getting local VM sessions displayed in native monitor resolutions was not apparent to me for Hyper-V. Conclusion - Hyper-V didn't automatically install with GUI enabled for Linux variants. 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. My main complaints were the following:ġ) Setting up VM's in Hyper-V was more cumbersome and involved more steps to get Linux GUI environments enabled. 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. I thought I would give Hyper-V another go when I upgraded my work system to Windows 10 at the end of last year. I have a lot more experience over the years using VMWare Workstation (ESX too) as well as VirtualBox. 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.

Vmware workstation pro vs player