Posted by: Michael Khanin
App-V, Application Virtualization, Hyper-V, Virtual PC, Virtual Server, Virtualization, vmware
Windows Server 2008 R2 will include Hyper-V 2.0, it promises to deliver the final pieces for enterprise level OS virtualization and to really compete with VMware at that level.
The most anticipated is of course Live Migration: moving running VM’s from one host to another without interruption of services running inside the VM’s. To accomplish this technique a new Shared Filesytem is needed and so will also be introduced in Hyper-V 2.0: Clustered Shared Volumes.
The Live migration works best together with System Center Virtual Machine Manager 2008, it can provide additional Live Migration management and orchestration scenarios such as Live Migration via policy.
Cool thing is you only need to update to Hyper-V 2.0, none of the rest of the infrastructure needs updating.
Logical Processor Support
- Support for 32 logical processors on host computer
- Twice the initial supported number of logical processors of Windows Server 2008 Hyper-V
Hot add remove Storage
- Add and remove VHD and pass-through disks to a running VM without requiring a reboot.
- Hot-add/remove disk only applies to VHDs and pass-through disks attached to the SCSI controller (not the IDE controller)
- Hot-add remove of storage controllers is not supported
- Enables storage growth in VMs without downtime
- Enables additional datacenter backup scenarios
Second Level Translation (SLAT)
- Leverage new processor features to improve performance and reduce load on Windows Hypervisor
- AMD: Enhanced Page Tables
- Intel: Nested Page Tables
- Improved memory management performance
- Memory usage of Windows Hypervisor will decrease from approximately 5% to 1% of total physical memory.
- More memory will be available for child partitions enabling higher consolidation ratios
- Pool of memory is dynamically distributed across VMs
- Memory is dynamically allocated/removed based VM usage with no service interruption
- Enables much higher consolidation ratios per host by addressing the greatest limiting factor to consolidation: Memory
- VM memory configuration includes:
- Initial (what VM will boot with)
- Minimum (what VM is guaranteed)
- Maximum (what VM can grow to)
- Memory is added via Hot-Add MEM functionality
- Memory is removed via Balloon driver (supported OSs)
Boot from VHD
Allows any VHD to work on physical hardware, this is very interesting! Boot an OS VHD on your physical hardware.
You can find more information at the WinHEC session descriptions: http://www.microsoft.com/whdc/winhec/2008/sessions.aspx