A. Client Hyper-V has nearly all of the server Hyper-V capabilities except for features that really don't make sense in a desktop environment such as Live Migration of virtual machines (VMs) between hosts, use of SR-IOV hardware, and fibre channel. Below is the full list of features included in Server Hyper-V but not included in Client Hyper-V:
- RemoteFX capability to virtualize the GPU and pass to VMs (Client Hyper-V does have the software GPU that's part of Windows 8 and RDP).
- Live Migration and Shared Nothing Live Migration of virtual machines (VMs), since moving VMs with no downtime isn't a key scenario for IT professional use. (Also Failover Clustering isn't available in client platforms, which normal Live Migration leverages (but not Shared Nothing Live Migration).)
- Hyper-V Replica, which allows an offsite replica of a VM to be maintained. (It’s highly unlikely a VM running on a desktop machine needs an offsite disaster recovery capability and if it does, it shouldn’t be running on Client Hyper-V.)
- SR-IOV network, which allows VMs to directly access SR-IOV capable network adapters. (No desktop machine would support SR-IOV and the zero latency network capability SR-IOV brings should not be a requirement for desktop workloads.)
- Synthetic fibre channel. (Once again, desktops won't need connectivity to fibre channel.)
- Network Virtualization, which allows networks to be created that are abstracted from the underlying physical network fabric. These are useful for multi-tenancy environments or multi-location infrastructures. (Not useful for desktops.)
Notice that since Live Storage Move isn't on this list, it's offered with both Server and Client Hyper-V, making it easy to move storage of VMs between types of storage and even SMB on Client Hyper-V. What is great with Client Hyper-V is that wireless networks can be used and your machine can still be put to sleep and hibernated!
See FAQs on Windows, virtualization, systems management, and all things Microsoft, at John Savill's FAQs.