Clock is ticking and the launch of Windows 8 Client OS is around the corner. Well, i’m not going to covered everything except Client Hyper-V which is going to replaced XP mode & Virtual PC. Yes, right you will have Enterprise class hypervisor running in your desktop/laptop.
Some information that you should take note when you want to use Client Hyper-V.
Requirement to enable Client Hyper-V
- Second Level Address Translation (SLAT) must exist
- 64 bit of Windows 8 Pro
- Hardware assisted Virtualization
How to enable Client Hyper-V features
- Go to Program & Features on the Control Panel, Click Turn Windows Features on or off and select Hyper-V Platform
Features NOT Available on Client Hyper-V
By using Client Hyper-V, you will have almost the features of Server Hyper-V EXCEPT the following features:
- RemoteFX GPU Hardware acceleration which require RDV in Windows Server)
- Live Migration.
- Hyper-V Replica
- Virtual Fibre Channel
- NIC Teaming
- Custom Event Viewer for Hyper-V
- Hyper-V Network Virtualization
- Failover Clustering (only available in Windows Server)
- Shared Nothing Live Migration
For those who has installed Windows 8 Enterprise, you will see “Virtual SAN Manager” on Hyper-V Manager. This does not mean that you will have “Virtual Fibre Channel”. The Hyper-V Manager in Client Hyper-V can be used to manage Windows Server 2012, in which case all the capabilities show up in the UI.
Another example:- Client Hyper-V only support Storage Migration and not Live Migration – in the UI when Hyper-V Manager is connected to Client Hyper-V, you’ll only see the option to move VM’s storage. If you use the same Hyper-V Manager to connect to WS2012 Hyper-V, you’ll see all 3 options
Commonalities between Client Hyper-V and Server Hyper-V
The commonalities between Windows 8 Hyper-V & Windows Server 2012 Hyper-V:
- Virtual Machines created with Client Hyper-V are 100% compatible with Server Hyper-V
- Client Hyper-V offers the same VM scale as Server
- Up to 64 virtual processes per VM
- Up to 64TB per virtual disk
- New file format VHDX
- Up to 1 TB of memory per VM.
- Live Storage Migration is included
- Support VHD Storage on SMB3 file shares
- 100% PowerShell/WMI compatibility in management from Client to Server.
- Client Hyper-V offers the full rich, open and extensible Hyper-V virtual switch.
- QoS, bandwidth management and other advanced virtual switch capabilities are in there
Q1. Can i use SCVMM to manage Client Hyper-V?
- No. It is not supported. SCVMM is use to manage Server Hyper-V.
Information above was shared by MVP peer :- Didier Van, Patrick Lownds, Romeo Minar, Carsten Rachfahl and Brian Elbert. Thank guy!
It may NOT contain the entire features which is NOT available on Client Hyper-V. So if the different is not listed above, kindly leave a comment to share with everyone. Thank you for your input.