Hyper V - Minasi Forum 2009

1,183 views

Published on

I spoke about:

- The need for machine virtualisation
- Hyper-V architecture and components
- Failover Clustering
- Licensing
- Management- W2008 R2: Cluster Shared Volume and Live Migration
- The possible future

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,183
On SlideShare
0
From Embeds
0
Number of Embeds
14
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Hyper V - Minasi Forum 2009

  1. 1. VM 1 VM 1 VM 3 VM 2 (“Admin”) (“Parent”) VM 2 VM 3 (“Child”) (“Child”) Drivers Drivers Hypervisor Drivers Drivers Drivers Drivers Hypervisor Hardware Hardware Traditional Approach Hyper-V Approach Microkernelised Hypervisor has an inherently secure architecture with minimal attack surface
  2. 2. OS Parent Partition Child Partitions Hyper-V VM Worker Processes ISV / IHV / OEM Applications Applications Applications MS/ XenSource WMI Provider VM Service User Mode Windows Server Xen-Enabled Linux Non- Windows Server Windows Server 2008, x64 2008, x64 Kernel 2008, 2003 Hypervisor Windows Linux Aware OS VSP Drivers VSC Windows VSC Windows Kernel Kernel Windows Hypercall Windows Drivers Kernel Adapter VMBus VMBus Emulation VMBus Kernel Mode Hyper-V “Designed for Windows” Server Hardware
  3. 3. 1. Copy memory pages from the source to the target via Ethernet 2. Final state transfer 3. Pause virtual machine a) Move storage connectivity from source host to target host via Ethernet b) Run new VM on target; Delete VM on source 4. Host 1 Host 2 Blue = Storage Purple = Networking Shared Storage
  4. 4. Configuration State

×