Upload
others
View
17
Download
0
Embed Size (px)
Citation preview
GM16What‘s new in Hyper-V 2016
Thomas Maurer
Cloud Architect & Microsoft MVP
itnetX
www.thomasmaurer.ch
@ThomasMaurer
Q&A
10 cool items to review
x86 Server Virtualization
Share For The Past 5+ Years
We are winning virtualization share
Q1 CY2008
Windows Server 2008Released
Q3 CY2009
Windows Server 2008 R2Released
Q3 CY2012
Windows Server 2012Released
Q3 CY2014
CURRENT
Change
Since Hyper-V Released
MicrosoftHyper-V
Server0.0% 11.8% 25.9% 30.6% +30.6 Pts
ESX40.0% 46.6% 51.4% 46.2% +6.2 Pts
Switch now!
From September 1, 2016, through June 30,
2017, customers who switch workloads from
VMware to Hyper-V can get free Windows
Server Datacenter licenses when buying
Windows Server Datacenter + Software
Assurance.
http://www.thomasmaurer.ch/2016/08/microsofts-new-
vmware-migration-offer-for-windows-server-2016/
Windows Server 2012 / 2012 R2 Hyper-V
High performance live migration (compression/RDMA)
Zero downtime upgrades
Automatic VM Activation
Live VM export
Guest backup improvements
Enhanced VMConnect
Dynamic memory host balancing
First class Linux support – Dynamic memory, file system consistent host based backup
RemoteFX over WAN
Generation 2 Virtual Machines
Secure boot in a VM
User defined meta data for VHDX
PowerShell for all Hyper-V operations
Hyper-V Metrics
Shared nothing live migration
High performance auto tiered storage spaces
Write back cache with spaces
Storage QoS
Shared VHDX for guest clustering
VHDX online resize
Storage deduplication with live VMs for VDI
Hyper-V Recovery Manager (Microsoft Azure Site recovery)
Azure Backup
Inbox multi-tenant site-to-site VPN gateway for physical & virtual networks
Protected VM Networks/Virtual RSS
Enhanced LBFO performance with NIC teaming
Hyper-V Extensible Switch
4K Sector support
Hyper-V over SMB
Hyper-V over Spaces & ReFS
64 VP, 1 TB VMs
SR-IOV for 10+GB networking
64TB VHDX
Hyper-V Replica
Network Virtualization
USB redirection over RemoteFX vGPU
Hot add/remove of storage
VHDX resiliency
Dynamic & differencing VHDX performance improvements
384 LP, 4TB physical system
2+ Million IOPS to a single VM
Resource Pools
NUMA in a VM
1024 running VMs on a host
Windows Server 2012 R2 Hyper-VWindows Server 2016 Hyper-VHigh performance live migration (compression/RDMA)Zero downtime upgradesAutomatic VM ActivationLive VM exportGuest backup improvementsEnhanced VMConnectDynamic memory host balancingFirst class Linux support – Dynamic memory, file system consistent host based backupRemoteFX over WANGeneration 2 Virtual MachinesSecure boot in a VMUser defined meta data for VHDXPowerShell for all Hyper-V operationsHyper-V MetricsShared nothing live migration
High performance auto tiered storage spacesWrite back cache with spacesStorage QoSShared VHDX for guest clusteringVHDX online resizeStorage deduplication with live VMs for VDIHyper-V Recovery Manager (Microsoft Azure Site recovery)Azure BackupInbox multi-tenant site-to-site VPN gateway for physical & virtual networksProtected VM Networks/Virtual RSSEnhanced LBFO performance with NIC teamingHyper-V Extensible Switch4K Sector support
Hyper-V over SMBHyper-V over Spaces & ReFS64 VP, 1 TB VMsSR-IOV for 10+GB networking64TB VHDXHyper-V ReplicaNetwork VirtualizationUSB redirection over RemoteFX vGPUHot add/remove of storageVHDX resiliencyDynamic & differencing VHDX performance improvements384 LP, 4TB physical system2+ Million IOPS to a single VMResource PoolsNUMA in a VM1024 running VMs on a host
Shielded VM supportvTPMKey Storage Drive for Gen 1 VMGuest VSM (enable Device Guard & Credential Guard in a VM)VM IsolationLinux Secure Boot
Distributed Storage QoSREFS Block REFS Fast Fixed Disk Creation
RemoteFX improvementsDiscrete Device Assignment of GPUHeadless mode support
Resilient Change Tracking (RCT)Backup improvementsBackup of Shared VHDX
Nested virtualizationVMCX configuration file Nano Server Host SupportMulti-host management (WMI)Hypervisor Power Management (connected standby works)Virtual machine groupingIC Upgrade via Windows UpdateHvSocket (Guest-Host)TimeSync improvements240 VP, 16TB VMsSupport for Containers
VM configuration version & upgradeRuntime Memory ResizeHot / add remove of NICsProduction CheckpointsStorage Resiliency - All Paths DownOnline Resize for Shared VHDXHot add / remove of replicated VHDRolling Cluster Upgrade Cluster Compute ResiliencyCluster Node QuarantineDevice Naming of NIC512LP, 24TB HostDirect Device Assignment
Windows Server 2016 Hyper-V scale limits
CapabilityWindows Server 2012/2012 R2
Standard and Datacenter
Windows Server 2016
Standard and Datacenter
VMware vSphere 6
Enterprise Plus
Physical (Host)
Memory Support
Up to 4 TB per
physical server
Up to 24 TB per
physical server (6x)
Up to 6 TB per physical server (12 TB for specific OEM certified platform)
Physical (Host) Logical
Processor SupportUp to 320 LPs Up to 512 LPs Up to 480 LPs
Virtual Machine
Memory Support
Up to 1 TB
per VM
Up to 16 TB
per VM (16x)
Up to 4TB
per VM
Virtual Machine Virtual
Processor Support
Up to 64
VPs per VM
Up to 240 VPs
per VM (3.75x)
Up to 128
VPs per VM
Source: http://www.vmware.com/pdf/vsphere6/r60/vsphere-60-configuration-maximums.pdf
#1Nano Server
Nano Server installation optionJust enough OS
Containers and modern applications
Full GUI
Specialized workloads
Third-party applications
RDS experience
Server Core
Lower maintenance server environment
Existing VM workloads
Nano Server
Just Enough OS
Provides higher density, reduced attack surface and servicing requirements
Ideal for cloud inspired infrastructure
• Smaller image size, smaller attack surface, faster boot time
Ideal for next generation app development
• Built for containers and cloud-native apps
• Full developer experience with Windows SDK and Visual Studio
The next step in the journey…
Nano Server: A new headless, 64-bit only, deployment option for Windows Server
Deep refactoring with cloud emphasis• Cloud fabric & infrastructure (clustering, storage, networking)
• Born-in-the-cloud applications (PaaS v2, ASP.NET v5)
• VMs & Containers (Hyper-V & Docker)
Extend the Server Core pattern• Roles & features live outside of Nano Server
• No binaries or metadata in OS image
• Standalone packages install like apps
• Full driver support
• Antimalware
#2Shielded VMs & Security
Challenges in protecting high-value assets
Solution – Windows Server 2016 Hyper-V
Shielded Virtual Machines
Confidently protect sensitive customer data:
Designed for ‘zero-trust’ environments
Who is Shielded VMs for?
As a hoster,I can protect my tenants’ VMs and their data from datacenter admins
As a tenant,I can run my workloads in the cloud while meeting regulatory/compliance requirements
As an enterprise,I can enforce a strong separation between Hyper-V administrators and sensitive workloads
Linux Secure Boot
Providing kernel code integrity protections for
Linux guest operating systems
Works with:Ubuntu 14.04 and later
SUSE Linux Enterprise Server 12
PowerShell to enable:Set-VMFirmware “Ubuntu”-SecureBootTemplateMicrosoftUEFICertificateAuthority
Host Resource Protection
• Dynamically identify virtual machines that are not
“playing well” and reduce their resource allocation
• Pioneered in Azure and enabled by default
• Designed to help prevent a VM consuming excessive hardware resources
• Looks for patterns of activity that shouldn’t occur within a non-malicious VM
GM16Demo Shielded VMs
www.thomasmaurer.ch
#3Networking & Storage Enhancements
Networking & Storage Enhancements
• Distributed Storage QoS (one or more virtual disks on
SOFS)
• Deduplication optimization for virtualized backup workloads
• VHDX improvements on ReFS
Storage Spaces Direct
Reliability, scalability, flexibility •
•
•
Use cases•
•
•
•
Cloud design points and management•
•
•
Storage Spaces Direct Scenarios
Hyper-converged Converged (Disaggregated)
Storage Replica
• Volume based block-level storage replication
• synchronous or asynchronous
• HW agnostic (any type of source / destination volume)
• SMB3 as transport protocol
• Leverages RDMA / SMB3 Encryption Multichanneling
• I/Os pre-aggregated prior to transfer
• Managed via Powershell, cluadmin, ASR
Storage Replica at a glance
ReFS Accelerated VHDX Operations
Resilient File System
It maximizes data availability, despite errors that
would historically cause data loss or downtime.
Taking advantage of an intelligent file system for:Rapid fixed disk creation
Rapid disk merge operations
GM16Demo ReFS
www.thomasmaurer.ch
#4PowerShell
PowerShell direct
• No network, no firewall requirements no nothing…
• Enter-PSSession –VMName VMName
• Invoke-Command –VMName VMName –ScriptBlock { Commands }
• connected to a W10 or WS 2016 TP host with VM that run W10 or WS 2016 TP
as the guest OS
• You need to be logged in with Hyper-V administrator credentials on the host.
• You need user credentials for the virtual machine.
• The virtual machine that you want to connect to must run locally on the host
and be booted.
#5Virtual Machines
VM Configuration & format
• Current at 8.0
• Might need to get manually updated
Update-VmVersion vmname (or vmobject)
• VM needs to be off
• Format is now binary
• .VMCX
Hot Add/Remove
• Add vNICs to a running VM
• Change memory of a running VM (add only if memory is available)
GM16Demo Hyper-V Operations & PowerShell
Direct
www.thomasmaurer.ch
#6Clustering
Rolling Cluster upgrade
• Stay in mixed mode during an upgrade of your cluster
• No more downtime
• Stays at 2012 R2 functional level until: Update-ClusterFunctionalLevel
• Works for Scale-Out File server failover cluster also
Cluster OS Rolling Upgrade Mixed OS mode is a new transition state for Failover
Clusters Optimizations don’t run
New features are not available
Do not plan on running your cluster in Mixed OS Mode for longer than one month
Cluster OS Rolling Upgrade Process
Start with a Windows Server 2012 R2 cluster
All nodes running Windows Server 2012 R2
The workload supports Cluster OS Rolling Upgrade process
Windows Server 2012 R2
Cluster Functional Level = Windows Server 2012 R2
Windows Server 2012 R2
Windows Server 2012 R2
Windows Server 2012 R2
Windows Server 2012 R2
Cluster OS Rolling Upgrade Process
Migrate Workloads Off Cluster Node
Pause | Drain the node
Windows Server 2012 R2
Cluster Functional Level = Windows Server 2012 R2
Windows Server 2012 R2
Windows Server 2012 R2
Windows Server 2012 R2
Windows Server 2012 R2
Failover Cluster
Cluster OS Rolling Upgrade Process
Evict Idle Cluster Node
Windows Server 2012 R2
Cluster Functional Level = Windows Server 2012 R2
Windows Server 2012 R2
Windows Server 2012 R2
Windows Server 2012 R2
Windows Server 2012 R2
Failover Cluster
Cluster OS Rolling Upgrade Process
Re-Provision Node
Install New OS
Install and Configure any Workload Requirements
Windows Server 2012 R2
Cluster Functional Level = Windows Server 2012 R2
Windows Server 2012 R2
Windows Server 2012 R2
Windows Server 2012 R2
Windows Server 2016
Failover Cluster
Cluster OS Rolling Upgrade Process
Re-Add Node To Cluster
Using Cluster UI or PowerShell
Cluster Functional Level Remains Windows Server 2012 R2
Windows Server 2012 R2
Cluster Functional Level = Windows Server 2012 R2
Windows Server 2012 R2
Windows Server 2012 R2
Windows Server 2012 R2
Windows Server 2016
Cluster OS Rolling Upgrade Process
Ready To Migrate Workloads Back
Migrate workloads to Windows Server 2016 Node
Validate functionality
Windows Server 2012 R2
Cluster Functional Level = Windows Server 2012 R2
Windows Server 2012 R2
Windows Server 2012 R2
Windows Server 2012 R2
Windows Server 2016
Cluster OS Rolling Upgrade Process
Repeat For Remaining Nodes
Cluster Functional Level = Windows Server 2012 R2
Windows Server 2016
Windows Server 2016
Windows Server 2016
Windows Server 2016
Windows Server 2012 R2
Cluster OS Rolling Upgrade Process
All Nodes Are Upgraded
Cluster Functional Level remains Windows Server 2012 R2
Functionality is limited to Windows Server 2012 R2 levels
Windows Server 2016
Cluster Functional Level = Windows Server 2012 R2
Windows Server 2016
Windows Server 2016
Windows Server 2016
Windows Server 2016
Cluster OS Rolling Upgrade Process Upgrade Functional Level
Cluster Functional Level upgraded To Windows Server 2016:
Update-ClusterFunctionalLevel cmdlet
New functionality added in Windows Server 2016 enabled
Windows Server 2016
Cluster Functional Level = Windows Server 2016
Windows Server 2016
Windows Server 2016
Windows Server 2016
Windows Server 2016
Cluster OS Rolling Upgrade Process
Upgrade is completed
Windows Server 2016
Cluster Functional Level = Windows Server 2016
Windows Server 2016
Windows Server 2016
Windows Server 2016
Windows Server 2016
Failover Cluster
v8
Virtual machine upgradesNew virtual machine upgrade and servicing processes
Compatibility mode: When a VM is migrated to a Windows Server 2016 host, it will remain in Windows Server 2012 R2 compatibility mode.
Upgrading a VM is separate from upgrading host.
VMs can be moved back to earlier versions until they have been manually upgraded.
Update-VMVersion vmname
Once upgraded, VMs can take advantage of new features of the underlying Hyper-V host.
Servicing model: VM drivers (integration services) updated as necessary.
Updated VM drivers will be pushed directly to guest operating system via Windows Update.
Windows Server2012 R2Hyper-V
Windows Server2016
Hyper-V
Windows Server Technical Previewsupports previous version VMs
in compatibility mode
By running Update-VMVersion,VM will be upgraded to newest hardware version
and can use the new Hyper-V features
v8 v8 v8
VM Servicing
Windows 8.1 / Windows Server 2012 R2:VM drivers (integration services) updated with each new host release
Required that VM driver version matches the host
Drivers shipped with host operating system
Windows 10 / Windows Server 2016:VM drivers (integration services) updated when needed
Require latest available VM drivers for that guest operating system
Drivers delivered directly to the guest operating system via Windows Update
Clustering
• Storage Replica
• Cloud Witness
• Virtual Machine Resiliency
• Site-aware Failover Clusters
• Workgroup & Multi-domain clusters
#7Hyper-V Manager
Hyper-V manager
• Updated Icons
• Alternate Credentials Support
• Managing earlier versions
• Updated Management Protocol
#8Production Checkpoints
Production Checkpoints
• Allows you to create “point-in-time” images of a VM
• Full support for application workloads
• VSS on windows (application-consistent)
• File system buffer flush on Linux (file-consistent)
• Still can switch to the standard method
• New VMs use production checkpoints as default
• Fixes the “wrong usage of checkpoints”
• NOT a backup solution
• Native CBT will be implemented for backup vendors
#9Nested Virtualization
Nested Virtualization
• Possible in Windows 10 build 10565 (with restrictions)
• Possible in TP5
• Dynamic Memory needs to be off
• http://www.thomasmaurer.ch/2015/11/nested-virtualization-in-windows-
server-2016-and-windows-10/
#10Much more
Much more
• Containers
• Software-Defined Networking
• Windows-as-a-Service
• …
GM16Servicing Model
LTSB servicing model
This is the traditional servicing model Windows Server has always used
5 + 5 years of servicing
Security and quality fixes only
No new features or functionality
Two Windows Server 2016 installation options use this model
Server with Desktop Experience
Server Core
Current Branch for Business (CBB)
Nano Server will be CBB only
What does this change?
Nano Server will not have an LTSB with Windows Server 2016 and therefore not have 5+5 years of servicing
Nano Server installations will have to move forward to future CBB releases of Nano Server to continue to be serviced
Licensing Nano Server will require Software Assurance (SA)
What doesn’t this change?
The quality, features, and functionality of Nano Server
Installation of new CBBs are always controlled by administrators, no forced upgrades
Windows Server Servicing
CBB4
WS 2012
WS 2012R2
WS 2016
CBB2
CBB3
Server with Desktop Experience and Server Core
LTSB
LTSB
Nano Server CBB1
Time
Feat
ure
s
Servicing for a CBB ends after the release of the 2nd future CBB
GM16Licensing
Core Based Licensing
Windows Server 2016 Licensing
• License all the physical cores in the server
• Minimum of 8 core licenses required for each proc
• Minimum of 16 core licenses required for each server
• Core licenses will be sold in packs of two.
• 8 two-core packs will be the minimum required to license each physical server.
• The two-core pack for each edition is 1/8th the price of a two proc license for
corresponding 2012 R2 editions.
http://www.thomasmaurer.ch/2015/12/windows-server-2016-licensing-and-pricing/
GM16What‘s new in Hyper-V 2016
Thomas Maurer
Cloud Architect & Microsoft MVP
itnetX
www.thomasmaurer.ch
@ThomasMaurer