Microsoft goes all in with virtualization
By Sandro Villinger, ITworld.com | Aug 18, 2011
Microsoft seems to be "all in" with its virtualization strategy these days: back in June we heard word of a client-hypervisor (Hyper-V 3.0) built into Windows 8 and in mid-July, Hyper-V for the upcoming Windows Server 8 was publicly unveiled. And I've dug up evidence of a much bigger presence of MinWin in Microsoft's upcoming OS. So how is this fitting together? Is this the ultimate virtualization trio?
My experience with Windows 8 Hyper-V 3.0
In late June, Robert McLaws from Windows Now discovered Hyper-V 3.0 inside a leaked build of Windows 8 client, which marks the first time this virtualization technology has shown up in a non-server Microsoft OS. Quick summary: Hyper-V 3.0 includes a new virtual disk format (VHDX) supporting up to 16 TB and "advanced resiliency features that protect against power failure events". It also sports some performance and scaling enhancements, such as NUMA for both CPU and RAM while also getting rid of the CPU core limit.
I spent two weeks trying out various VMs (from XP to Windows 7) to get a grip on Hyper-V's performance and possible integration with the Windows 8 client. First and foremost: It acts and works like the hypervisor built into Windows Server 2008 R2; there are no major changes except for the enhancements discovered by McLaws and some minor differences I noticed while migrating my VMs:
- Performance: Hyper-V seems to try harder to reduce overall resource usage of idling VMs. There's less resource usage, which was especially noticeable on one of my lower-end Core i3 systems.
- EPT required: the pre-release version of Hyper-V 3.0 requires a CPU with EPT (Extended Page Tables), a virtualization feature unique to Intel's Nehalem processor architecture (Core i3, i5, i7 and Xeon obviously), or known as "Nested Page Tables" in the AMD world.
- New Migration Assistant: A new migration assistant helps move single VHDs or the entire VM (including configuration, snapshot and the second level paging file) to a new on- or offsite location without taking it offline.
Add comment
Recent popular content
Most Read
Recent popular content
Most Read

0 comments
Digg
Print









