2011
06.16

I’ve just published a new document or guide that is subtitled as “Understanding, enabling, and configuring Windows Server 2008 R2 Hyper-V Dynamic Memory for virtualised workloads”.

This whitepaper will walk you through:

  • The mechanics of Windows Server 2008 R2 SP1 Hyper-V Dynamic Memory
  • The scenarios that you’ll employ it in
  • The pre-requisites for Dynamic Memory
  • Configuring Dynamic Memory
  • Some of the application workload scenarios

“We normally don’t like it when a service pack includes new features. New features mean changes that need to be tested, possible compatibility issues, and more headaches in between the usual operating system deployment cycles. Windows Server 2008 R2 Service Pack 1 came with a number of new features but we did not complain; in fact, we virtualisation engineers had a mini celebration. This is because those new features were mostly targeted at server and desktop/session virtualisation, and aimed to give us a better return on hardware investment.

Dynamic Memory was one of those new features. Put very simply, this VM memory allocation feature allows us to get more virtual machines on to a Hyper-V host without sacrificing performance.

You can use Dynamic Memory in a few scenarios. The one that gets the most publicity is virtual desktop infrastructure (VDI) where economic PCs are replaced by expensive virtual machines running in the data centre. It’s critical to get as many of them on a host as possible to reduce the cost of ownership. Server virtualisation is the scenario that we techies are most concerned with. We’ve typically found that we tend to run out of memory before we get near to the processor or storage I/O limits of our hardware. And the final scenario is where we use Hyper-V to build an Infrastructure-as-a-Service cloud, where elasticity and greater virtual machine density are required.

The approach that Microsoft took with this new memory optimisation technique ensures that concepts such as over commitment are not possible; that’s because over commitment potentially does cause performance issues. Dynamic Memory does require that you understand how it works, how to troubleshoot it, and how applications may be affected, before you log into your hosts and start enabling it. It will require some planning.

The aim of this document is to teach you how Dynamic Memory works, show you how to configure it, how to monitor it, and how to use it in various application scenarios”.

The document continues …

Credit:

Big shout out to the Hyper-V PMs and my fellow MVPs for the many conversations over the past year that allowed us to learn a lot.

18 comments so far

Add Your Comment
  1. great work…love it

    • Thanks!

  2. Absolute fantastic, Aidan!

  3. Sounds good, but I cannot download the PDF :-(

    • Raymond,

      I’ve tested the download from 2 different locations/PCs, and lots of others have downloaded. Give it another go, then check any proxies/firewalls.

      Aidan.

  4. Thanks Aidan. Another very informative whitepaper and one of the clearest guides to Dynamic Memory that I’ve read yet.

    Niall

    • Thanks Niall.

  5. Fantastic work again Aidan…Thanks

    • Thanks Konstantinos

  6. Can I share it on PaperShare ?

    • No.

  7. Excellent, just when I needed a clear explanation… got here via Ben Armstrong’s blog. Lovin the Hyper-V deployment book btw.

    • Thanks! I hope it proves useful.

  8. Thanks a lot!
    The reading is excellent even for non English speaking users!

    We waiting for smth else in the same way :)

  9. Thanks. Very clear explanation!

  10. Thank you for your share is.

  11. Very good article. Thanks.
    Is there a way to verify that my host (R2 sp1) and VMs are configured properly to use Dynamic memory model? I’ve problem verifying whether dmvsc.sys driver get loaded or not. Boot log, ntbtlog.txt (genreated with “bcdedit /set bootlog yes”) doesn’t list the driver. DriverViewer.exe (from NirSoft) also doesn’t list it. Am I missing something here?

Get Adobe Flash player