How to setup RAM sensitive software on a Hyper-V VM with Dynamic Memory

When you create a new Hyper-V virtual machine, configured with Dynamic Memory, the advantage is to boot a virtual server with minimal RAM allocated (e.g. 512 MB), but the catch is some setups check that the computer it's being installed on has enough memory.  I recently was disappointed to see that this same issue / inconvenience exists as I was running through the VMM setup for 2012 SP1 (CTP2). I tried Aidan's tip of using Paint, but I could not get paint to use enough memory, so that the setup prerequisites would let me get by.

Fortunately, I found a post from 2008 on the Windows SDK blog that mentioned tcpanalyzer.exe and consume.exe as "hidden gems" in the SDK. Consume.exe sounded promising, so I went to fetch the latest Windows SDK. Fortunately, consume.exe is still there.

Consume.exe is all of 21KB, so I copied into my newly minted Hyper-V VM (for more on my favorite way to load up a new Windows Server 2012 VM, see … ) and ran consume.exe -physical-memory -time 60.

The 'Assigned Memory' value in my Hyper-V Manager window climbed up above the 2GB (2242 MB) I needed to proceed, and I was able to finish my setup.

PrintView Printer Friendly Version

EmailEmail Article to Friend

« I miss @Gist already | Main | Gartner MQ - APM Review of Microsoft System Center 2012 »

References (3)

References allow you to track sources for this article, as well as articles that were written in response to this article.
  • Source
    Consume.exe This command line tool can consume system resources for a specified amount of time and is useful for reproducing errors that might be caused by resource starvation. The resources it can consume include physical memory, page file space, disk space, kernel pool, and CPU time.
  • Related
    Please check if this help you Mohamed Fawzi |
  • Related
    You can cause the VM to reach a high water mark that exceeds the memory requirements of the application that you want to install. It is a bit crude but it will work. I picked up a handy trick from one of the Hyper-V product group members for my Dynamic Memory testing/demonstrations. I use MS Paint, and expand the canvas size to the maximum number of pixels. That EATS up memory and drives up the highwater mark.

Reader Comments

There are no comments for this journal entry. To create a new comment, use the form below.

PostPost a New Comment

Enter your information below to add a new comment.

My response is on my own website »
Author Email (optional):
Author URL (optional):
Some HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>