Yesterday we talked about RemoteFX, one of the two big new features bundled into Windows Server 2008 R2 Service Pack.

Today let's turn our attention to the other one: Dynamic Memory. As you may recall, DM gives Hyper-V a boost by pooling physical memory and dynamically distributing it to virtual machines. Clever stuff. Dynamic, even.

Microsoft's Virtualization Team Blog just posted part 6 (!) of an ongoing series on--you guessed it--Dynamic Memory. This entry looks at the nitty-gritty of the technology--how it works and how you'll actually use it. Here's an excerpt on the subject of Memory Priority:

By default, all virtual machines are created equal in terms of memory prioritization. However, it's very likely you'll want to prioritize memory allocation based on workload. For example, I can see a scenario where one would give domain controllers greater memory priority than a departmental print server. Memory Priority is a per virtual machine setting which indicates the relative priority of the virtual machine's memory needs measured against the needs of other virtual machines. The default is set to 'medium'. If you find that you need to adjust this setting, you can adjust this setting on the fly while the virtual machine is running without downtime.

Sounds great, right? IT staffers will definitely want to give this a read, especially those who just downloaded the Server 2008 R2 beta.

What are your thoughts on Dynamic Memory? Killer addition to Server 2008 R2 and Hyper-V, or something you can better accomplish with other means? Share your thoughts in the comments.