1. Module 4: Hyper-V for VDI

2. Agenda Introduction to Hyper-V Hyper-V for VDI components
Technical requirements and architecture
Hyper-V for VDI components
VDI over SMB, SAN, DAS
Storage tiers for pooled desktops
Clustering and storage spaces

3. Hyper-V Architecture Child Partitions User Mode Kernel Mode Ring -1
Parent Partition
Child Partitions
Applications
Applications
Applications
VM Worker Processes
Applications
User Mode
WMI Provider
VM Service
Windows Server 2012
Windows Server 2008, 2012
Windows Kernel
VSC
Non-Hypervisor Aware OS
Linux Kernel
Linux VSC
Hypercall Adapter
Windows Kernel
VSP
IHV Drivers
VMBus
Kernel Mode
Architecture
VMBus
VMBus
Emulation
Windows hypervisor
Ring -1
“Designed for Windows” Server Hardware

4. Hypervisor: Monolithic vs. Microkernelized
Monolithic hypervisor
Microkernelized hypervisor
Simpler than a modern kernel, but still complex
Contains its own drivers model
Used by competitors
Simple partitioning functionality
Increase reliability and minimize TCB
No third-party code in HV
Drivers run within guests
Hyper-V
VM 1
(Admin)
VM 2
VM 3
VM 2
(“Child”)
VM 3
(“Child”)
VM 1 (“Parent”)
Virtualization
Stack
Hypervisor
Drivers
Drivers
Drivers
Drivers
Hypervisor
Hardware
Hardware

5. Before Windows Server 2012 Hyper-V
Windows Server Management Marketing
5/5/2018
Before Windows Server 2012 Hyper-V
Windows Server 2008 R2 Hyper-V & Hyper-V Server 2008 R2 launched
SP1 for Windows Server 2008 R2 & Hyper-V Server 2008 R2 launched
Hyper-V introduced in Windows Server 2008
Hyper-V Server 2008 launched
Live Migration
Cluster Shared Volumes
Processor Compatibility
Hot-Add Storage
Performance & Scalability Improvements
June 2008
October 2008
October 2009
February 2011
Dynamic Memory
RemoteFX
Before Windows Server 2012
Let’s first review the Hyper V improvements that the earlier versions of Windows Server provide. Beginning with Windows Server 2008, server virtualization via Hyper V technology has been an integral part of the operating system. A new version of Hyper V is included as a part of Windows Server 2008 R2, and this was further enhanced with Service Pack 1 (SP1).
There are two manifestations of the Hyper V technology:
Hyper V is the hypervisor-based virtualization feature of Windows Server 2008 R2.
Microsoft Hyper V Server is the hypervisor-based server virtualization product that allows customers to consolidate workloads onto a single physical server. This is available as a free download.
Windows Server 2008 R2 Hyper V enhancements
With the launch of Windows Server 2008 R2 Hyper-V, Microsoft introduced a number of compelling capabilities to help organizations reduce costs, whilst increasing agility and flexibility. Key features introduced included:
Live Migration – Enabling the movement of virtual machines (VMs) with no interruption or downtime
Cluster Shared Volumes – Highly scalable and flexible use of shared storage (SAN) for VMs
Processor Compatibility – Increase the Flexibility for Live Migration across hosts with differing CPU architectures
Hot Add Storage – Flexibly add or remove storage to and from VMs
Improved Virtual Networking Performance – Support for Jumbo Frames and Virtual Machine Queue (VMq)
With the addition of Service Pack 1 (SP1) for Hyper-V, Microsoft introduced 2 new, key capabilities to help organizations realize even greater value from the platform:
Dynamic Memory – More efficient use of memory while maintaining consistent workload performance and scalability.
RemoteFX – Provides the richest virtualized Windows 7 experience for Virtual Desktop Infrastructure (VDI) deployments.
Windows Server 2008 R2 Hyper V Benefits
Hyper V is an integral part of Windows Server and provides a foundational virtualization platform that lets customers transition to the cloud. With Windows Server 2008 R2, customers get a compelling solution for core virtualization scenarios; production server consolidation, dynamic data center, business continuity, Virtual Desktop Infrastructure (VDI), and test and development. Hyper V provides customers with better flexibility with features like live migration and cluster shared volumes for storage flexibility. In Windows Server 2008 R2, Hyper V also delivers greater scalability with support for up to 64 logical processors and improved performance with support for dynamic memory and enhanced networking support.
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

6. Hyper-V Scalability Improvements
System
Resource
Windows Server 2008 R2 Hyper-V
Windows Server 2012 Hyper-V
Improvement Factor
Host
Logical Processors 64
320 5×
Physical Memory
1TB
4TB 4×
Virtual CPUs per Host
512
2,048 VM
Virtual CPUs per VM 4
16×
Memory per VM
64GB
Active VMs per Host
384
1,024
2.7×
Guest NUMA No
Yes -
Cluster
Maximum Nodes 16
Maximum VMs
1,000
8,000 8×

7. Hyper-V for VDI components

8. Windows Server 2012 Storage
BEST VALUE FOR VDI
Windows Server 2012 Storage
Use direct-attached storage, network-attached storage, and clustered or SAN storage
Provide configuration options to optimize for tiered storage
Reduce storage cost while maximizing I/O operations per second
With Windows Server 2012, technologies such as RDS and Hyper-V provide the scalability and flexibility that enterprises demand from their virtual desktop platform.
Storage Options:
RDS now supports various lower cost storage, such as SMB-based fileshares, or Direct Attached Storage (DAS), in addition to SAN
Can separately configure storage location for Parent VHD, individuals VMs, and UserVHD. Use different storage tiers for each to optimize
Hence, storing VMs is now cheaper, as customers do not have to rely on expensive SANs anymore.
Powerful Hyper-V platform
RDS can now be configured to have multiple active nodes, thereby enabling the connection broker to scale up, while still ensuring DR.
As always, the RDS platform provides APIs to help partners build on top of the Microsoft platform. Hence, partners such as Citrix can help scale out the Microsoft VDI platform to include largest and most complex of deployments.

9. VDI Storage in Hyper-V New in Windows Server 2012
Storage Spaces
SMB 3.0, Hyper-V over SMB support
Cluster Shared Volume
Scale-Out File Server
VDI Storage Configuration
Direct Attached, Central SMB, or Central CSV / SAN
Storage location of user profile disks, parent VHD, & virtual machines can be configured separately for each collection to enable tiered storage for optimal performance and savings
Optimum use of high IOPS vs. high volume storage
RDVH
File Server
JBOD
SSD
15K
10K
Spaces
SOFS
Cluster
Hyper-V
//CSV1/ Parent
//CSV2/VMs
//CSV3 /UserDsk
Storage is a key part of a VDI deployment. Customer experience indicates that VDI is easily the most challenging workload for storage infrastructure, both in terms of IOPS and storage volume. Thus, it is critical to have a wide range of options with which you can optimize the output from your storage $$.
You have probably heard about all that is new with storage in WS2012: Storage Spaces, SMB Hyper-V support, CSV, new highly scalable deployment models for File Server are some of the key new storage technologies in Server. In our VDI deployment, we support all of these.
We are also offer the ability to configure storage at a granular level, per collection:
You can use direct attached, central SMB, or central CSV SAN storage with a collection.
There are three types of “things” you need to store: The parent VHD, each VM, and the user disks. You can configure a separate storage location for each.
E.g. for your mission critical pooled VM collection, you can use a high-IOPS SSD array over SMB for the parent VHD, and a mirrored spaces disk array for the user VHDs to ensure data resiliency, etc.
Or you can equip your Hyper-V nodes with cheap, locally attached SSD drives along with normal hard disks. Then assign parent VHD to SSD volumes, VM instances to the disks, and host the user disks in a central file server over SMB.
Ultimately, ability to configure these options separately allows you to optimize for your IOPS and volume needs.
Other Notes:
There are some caveats.
If Hyper-V supports the storage option, we support it for VDI. Some things don‘t. REFS not supported for clusters, so we don’t support it.

10. Windows Server 2012 File Server
Not your traditional file server
Enables many new architectures and technologies
SMB 3.0
RDMA
Introduces file server for “server data”
Server data is an extended file lock

11. Server Message Block 3.0
New flexible storage solution for virtual or cloud infrastructure
Virtually no application downtime for planned maintenance and unplanned failures
Data store for Microsoft SQL Server databases and Hyper-V workloads
Highly available scale-out file server
Active/active access
Built-in encryption support
Single namespace for file system
The Server Message Block (SMB) protocol is a network file sharing protocol that allows applications on a computer to read and write to files and to request services from server programs in a computer network. The SMB protocol can be used on top of the TCP/IP protocol or other network protocols. Using the SMB protocol, an application (or the user of an application) can access files or other resources at a remote server. This allows applications to read, create, and update files on the remote server. It can also communicate with any server program that is set up to receive an SMB client request. Windows Server 2012 introduces the new 3.0 version of the SMB protocol.
Windows Server 2012 now offers support for application-based file shares. This application support for SQL and Hyper-V allows you to leverage the high-performance and high availability features now available with Windows Server 2012 for your SQL databases or your Hyper-V guests.
Enables virtual machines and virtual machine storage to reside on SMB network shares, giving you the power to design new flexible storage solutions for your virtual or cloud infrastructure.
Continued on next slide

12. Improved performance optimizations
New in SMB 3.0
SMB Transparent Failover
SMB Scale Out
SMB Multichannel
SMB Direct
SMB Directory Leasing
SMB Encryption
SMB-Specific PowerShell cmdlets
Performance Counters for server applications
Improved performance optimizations
New features of SMB 3.0
SMB Transparent Failover
SMB Scale Out
SMB Multichannel
SMB Direct
SMB Directory Leasing
SMB Encryption
SMB-Specific PowerShell cmdlets
Performance Counters for server applications
Improved performance optimizations
Server Message Block overview:
Server Message Block overview:

13. Hyper-V over SMB
Can store virtual machine files (configuration, VHD, snapshots) in files shares over the SMB 3.0 protocol
Is supported for both stand-alone and clustered servers that use Hyper-V with shared file storage for the cluster
Can support scale-out file shares and clusters
Can leverage SMB Multichannel
Hyper-V in Windows Server 2012 introduces a new storage option—support for Server Message Block 3.0 – for remote file storage. This capability provides increased flexibility, easier storage provisioning, and reduced system costs when compared to the storage options in Windows Server 2008 R2.
Hyper-V can store virtual machine files, such as configuration, virtual hard disk (VHD) files, and snapshots, in file shares over the SMB 3.0 protocol. This can be used for both stand-alone file servers and clustered file servers that use Hyper-V together with shared file storage for the cluster.

14. Why Should I Care? Ease of storage provisioning and management
You can manage file shares instead of storage fabric and logical unit numbers (LUNs)
Previously all Hyper-V clusters required shared storage using Fibre Channel, Fibre Channel over Ethernet, iSCSI, or Serial-Attached SCSI
Increased flexibility
You can dynamically migrate virtual machines or databases in the data center
Ability to take advantage of existing investment in a converged network
You can use your existing converged network with no specialized storage networking hardware
Reduced capital expenditures
Capital expenses (acquisition costs) are reduced
Reduced operating expenditures
You can reduce operating costs because there is no need for specialized storage expertise
With new Hyper-V support for SMB file storage, administrators have more storage options for virtualized environments. The feature makes it easier to provision and manage Hyper-V storage, takes advantage of existing network investments, and helps reduce acquisition and management costs for Hyper-V.
Hyper-V gains flexibility, adaptability, and cost efficiency through the use of SMB remote file storage.
Ease of provisioning and management.
You can manage file shares instead of storage fabric and logical unit numbers (LUNs).
Increased flexibility.
You can dynamically migrate virtual machines or databases in the data center.
Ability to take advantage of existing investment in a converged network.
You can use your existing converged network with no specialized storage networking hardware.
Reduced capital expenditures.
Capital expenses (acquisition costs) are reduced.
Reduced operating expenditures.
You can reduce operating costs because there is no need for specialized storage expertise.

15. Requirements
One or more computers running Windows Server 2012 with the File Services role installed
One or more computers running Windows Server 2012 with the Hyper-V role installed (separate from the file server)
A common Active Directory infrastructure
The servers running Active Directory Domain Services (AD DS) do not need to run Windows Server 2012
Constrained delegation
Supported configurations
Standalone Hyper-V servers (not a high-availability solution)
Hyper-V servers configured in a failover cluster
The requirements for implementing Hyper-V over SMB 3.0 include:
One or more computers running Windows Server 2012 with the File Services role installed
The file server must have Windows Server 2012 installed, so the new SMB 3.0 protocol is available. You can also use non-Microsoft file servers that implement the SMB 3.0 protocol. Hyper-V does not block older versions of SMB, however, the Hyper-V Best Practice Analyzer issues an alert when an older version of SMB is detected.
One or more computers running Windows Server 2012 with the Hyper-V role installed
Loopback configurations (where the computer that is running Hyper-V is used as the file server for virtual machine storage) are not supported.
A common Active Directory infrastructure. The servers running Active Directory Domain Services (AD DS) do not need to run Windows Server 2012.
An Active Directory infrastructure is required, so you can grant permissions to the computer account of the Hyper-V hosts. Note: Although not required, failover clustering is supported on the Hyper-V side, the File Services side, or both. They must be separate clusters.
Although not required, failover clustering is supported on the Hyper-V side, the File Services side, or both. They must be separate clusters.

16. SMB Hyper-V Cluster Clustered File Server/ Standalone Hyper-V
Standalone File Server/ Clustered Hyper-V
All Clustered
SMB shares are used for VHD storage in all scenarios
Standalone file server/Clustered Hyper-V: Hyper-V VMs are highly available; file server is not continuously available
Clustered file server/Standalone Hyper-V: File system is highly available; Hyper-V VMs are not highly available
All clustered: File system and Hyper-V VMs are both highly available

17. Clustering Hyper-V with SMB
Cluster is a “storageless” cluster.
Configure a file server witness quorum model.

18. CSV Cache Block level read cache for CSV
Takes up to 20% of file server memory
Drastic reductions in IO from reads
Configure SharedVolumeBlockCacheSize cluster property
Set CSVEnableBLockCache to 1 for each CSV Volume

19. INSERT DM SLIDES HERE