While many considered Hyper-V R2 to be a vast improvement over Microsoft’s original hypervisor release, critics speculated that the technology still had plenty of room for improvement -- particularly in regards to memory management. With the release of Windows Server 2008 R2 Service Pack 1 (SP1), Microsoft responded with Dynamic Memory, an automated virtual memory allocation feature that’s often compared to VMware’s memory overcommit functionality.
But will Dynamic Memory really help Microsoft further close the virtualization gap? These five links will help you pinpoint how the feature works and whether it truly measures up to similar features from VMware and Citrix.
For more information on Hyper-V Dynamic Memory visit our Microsoft server virtualization topic page.
1. Working with Hyper-V Dynamic Memory
In the past, admins had to guesstimate how much memory to allocate to a Hyper-V virtual machine, but Dynamic Memory takes a more hands-off approach. So how does it work?
2. Best practices for Hyper-V Dynamic Memory
Dynamic Memory may do the brunt of the work when it comes to virtual memory management, but best practices still play a key role in its functionality. Expert Eric Beehler breaks down what they are and how they work.
3. Virtual memory monitoring with Hyper-V
Once Dynamic Memory is up and running, it’s important to monitor virtual memory levels with Hyper-V’s Manager Console to avoid challenging memory shortages.
4. Making sense of virtual memory settings with Dynamic Memory
Dynamic Memory’s virtual memory settings are designed to keep virtual hosts from behaving badly. Windows expert Greg Shields outlines the Memory Buffer and Priority settings in Hyper-V R2 SP1.
5. Microsoft virtual memory debate eyes Citrix over VMware
Hyper-V Dynamic Memory is often weighed against VMware memory overcommit, but memory management features from Citrix XenServer may present the better comparison.
You can follow SearchWindowsServer.com on Twitter @WindowsTT.