windows 8 hyper-v: availability
DESCRIPTION
More info on http://www.techdays.be.TRANSCRIPT
• Statements about capabilities or benefits are subject to change
• Packaging and licensing have not yet been determined
• Any concepts shown are for illustration purposes only
Disclaimer:
This presentation contains preliminary information that may be changed substantially prior to final commercial release of the software described herein.
The information contained in this presentation represents the current view of Microsoft Corporation on the issues discussed as of the date of the presentation. Because Microsoft must respond to changing market conditions, it should not interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of the information presented after the date of the presentation. This presentation is for informational purposes only.
MICROSOFT MAKES NO WARRANTIES, EXPRESSED, IMPLIED ,OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
Microsoft may have patents, patent applications, trademarks, copyrights or other intellectual property rights , covering subject matter in this presentation. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this information does not give you any license to these patents , trademarks, copyrights or other intellectual property rights.
MISSION CRITICAL WORKLOADS
Windows Server 8 – Developer Preview
MEMORYSTORAGE NETWORKPROCESSOR
FLEXIBLE
Windows Server 8 – Developer Preview
High Medium Low
• VM Health Monitoring detection inside virtual machine
• Clustering in the host identifies app failures and takes recovery action
1. Host level HA recovery
• Failover Clustering fails over VM to another node
2. Guest level HA recovery
• Failover Clustering Reboots VM
3. Application level recovery
• Service Control Manager (SCM) or event triggered
• Generic health monitoring for any application
– Monitor services through Service Control Manager
– Generation of specific Event ID’s• ISV opportunity to leverage GuestSetCriticalState() with to integrate 3rd party
application monitoring solutions in the VM
APP
Windows Server 8 – Developer Preview
Windows Server 8 – Developer Preview
According to Gartner about 1/3 companies use outside
companies to dispose of PCs & Servers
ENCRYPTED CLUSTER VOLUMES
Windows Server 8 – Developer Preview
Windows Server 8 – Developer Preview
Hyper-V Replica
Affordable
Simple to configure
Works with your current hardware
Comes in the box in Windows 8
Single wizard setup
All you need is two connected servers
No Guest dependencies
Windows Server 8 – Developer Preview
Demo
DISASTER RECOVERY FOR EVERYONE
Windows Server 8 – Developer Preview
• Yes! NIC Teaming is supported with the
Hyper-V Extensible Switch
Windows Server 8 – Developer Preview
Root Partition
Extensible Switch
Extension Protocol
Extension Miniport
Capture Extensions
WFP Extensions
Filtering Extensions
Forwarding Extensions
Team NIC
Physical NICPhysical NIC Physical NIC
Host NICVM NIC
VM1
VM NIC
VM2
Windows Server 8 – Developer Preview
Host 1
Extensible Switch
Extension Protocol
Extension Miniport
Extension A
Host 2
Extensible Switch
Extension Protocol
Extension Miniport
Extension A
VMConfiguration
Runtime State
Windows Server 8 – Developer Preview
Virtual Machine
Network Stack
Software NIC
• Enable IOV (VM NIC Property)
• Virtual Function is “Assigned”
• “NIC” automatically created
• Traffic flows through VF
Turn On IOV• Switch back to Software path • Reassign Virtual Function
• Assuming resources are available
• Migrate as normal
Live Migration Post Migration
• Remove VF from VM
VM has connectivity even if
• Switch not in IOV mode
• IOV physical NIC not present
• Different NIC vendor
• Different NIC firmware
SR-IOV Physical NICPhysical NIC
Software Switch
(IOV Mode)
SR-IOV Physical NIC
• Software path is not used
Virtual Function
“NIC”
Software NIC
Virtual Function
Software Switch
(IOV Mode)
“NIC”
Fibre Channel from the guest
• Guest Clustering• Cluster service runs inside a VM
• Apps and services inside the VM are managed by the cluster
• Apps move between clustered VMs
• Historically required iSCSI shared storage
• New virtual “Fiber Channel Adapter”• Up to four virtual HBAs assigned to each guest
• WWNs assigned to each virtual HBA
Fiber Channel
Cluster
STORAGE
DSM Host MPIO
DSM Guest MPIO
Demo
ARCHITECTURE
Green = Storage
Blue = Networking
Shared Storage: SAS, iSCSI, FC or SMB
Cluster
Node 1 Node 2
ARCHITECTURE
Windows Server 8 – Developer Preview
Host 1 Host 2
SMB File Server
ARCHITECTURE
Windows Server 8 – Developer Preview
Storage 1 Storage 2
Hyper-V Server
Destination Device
Hyper-V Server
Virtual Machine
VHD VHD
VHD Stack
1
23
45
Source Device
1. Reads and writes go to
VHD on Source device
2. VHD is copied from
Source to Destination
device
3. After copying, mirror
writes to Source and
Destination
4. After Source and
Destination storage are
synchronized, transfer
access to the VHD to the
Destination device
5. VHD from Source device
is deleted
Windows Server 8 – Developer Preview
ARCHITECTURE
Windows Server 8 – Developer Preview
Blue = Networking
Host 1 Host 2
No Shared Storage
Demo
MOBILITY WITHOUT LIMITS
Windows Server 8 – Developer Preview
Windows Server 2008 Windows Server 2008 R2Windows Server 8
Developer Preview
Live MigrationNo, Quick Migration one at
a timeYes, one at a time
Yes, with no limits. As
many as hardware will
allow
Live Migration Storage
RequirementsSAN required SAN required Any Storage Solution
Live Migration Shared
StorageiSCSI, Fiber Channel or SAS iSCSI, Fiber Channel or SAS
iSCSI, Fiber Channel, SAS
or SMB
Live Storage MigrationNo. Quick Storage Migration
via SCVMM
No. Quick Storage Migration
via SCVMM
Yes, with no limits. As
many as hardware will
allow
Live Migration Between
ClustersNo No Yes
Disaster Recovery• Hyper-V Replica for Asynchronous Replication
• Integration with Storage Arrays for Synchronous Replication
Application/Service Failover
• Non-Cluster Aware Apps: Application Health detection
• VM Guest Cluster: iSCSI, Fiber Channel, FCoE
• VM Guest Teaming of SR-IOV NICs
I/O Redundancy
• Network Load Balancing & Failover via Windows NIC Teaming
• Storage Multi-Path IO (MPIO)
• Multi-Channel SMB
Node Redundancy• Live Migration for Planned Downtime
• Failover Cluster for Unplanned Downtime
Hardware Fault • Windows Hardware Error Architecture (WHEA)/RAS