Skip to main content

Hyper-V R2 SP1 Dynamic Memory

Until now, you were not able to over allocate RAM to virtual machines running Hyper-V.  You could allocate enough static RAM to a set of VMs that would exceed the total amount of RAM on the server, but you would not be able to start all your virtual machines.

Part of server consolidation is the ability to take servers that are underutilized and move their operations to a single server.  This has worked well however, even when a virtual machine was not taxed to its maximum memory load, it still consumed the same amount of memory and therefor was a hindrance to further consolidation.

Dynamic memory allows you to safely increase the VM density on a server.  This feature requires Windows Server 2008 R2 SP1 and is available on the following guest partitions:
  • Windows Server 2003 Enterprise and Datacenter with SP2 (32 and 64-bit versions)
  • Windows Server 2003 R2 Enterprise and Datacenter with SP2 (32 and 64-bit versions)
  • Windows Server 2008 Enterprise and Datacenter (32 and 64-bit versions)
  • Windows Server 2008 R2 Enterprise and Datacenter (32 and 64-bit versions)
  • Windows Vista Ultimate and Enterprise with SP1 (32 and 64-bit versions)
  • Windows 7 Ultimate and Enterprise  (32 and 64-bit versions)

After installing Windows Server 2008 R2 SP1, I ran a test of the dynamic memory option.  Dynamic memory is not enabled by default.  The screen shot below shows the memory page of a VM on the upgraded server.
image
Two new areas have been added, Dynamic and the Memory weight.

In the Dynamic Memory area, you must first decide on the minimal amount of RAM that is required to start the VM.  The Maximum RAM setting is the upper limit of RAM that you will allocate to this VM.  You cannot use this option to assign more RAM than is physically on the server.  64GB is still the upper limit for a virtual machine. 

The Memory Buffer allows you to specify additional RAM above the current workload requirements.  If it is available, your VM will have additional RAM to work with

The Memory Weight option allows you to establish a pecking order among your VMs to decide who gets additional RAM when the free pool of RAM is depleted.

The Memory Weight and Memory Buffer are the only two memory settings that can be adjusted while a VM is running.  Changing between static and dynamic or adjusting dynamic memory requires the VM to be shut down.

The Hyper-V Manager also has some new columns added to it:
image
The Assigned Memory always starts at the Startup RAM value.  The Memory Demand lets you know how much RAM is actually being used. The VM that is not reporting Memory Demand is configured for static memory.

You also need to install SP1 on your VMs to take fully advantage of Dynamic memory.  Re-installing the integration services will also provide this functionality, but Microsoft recommends that you upgrade all VMs to SP1.

More information can be found by following this link to Microsoft.

Comments

Popular posts from this blog

Sticky Key problem between Windows Server 2012 and LogMeIn

This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this.  First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .

With the AD Recycle Bin Turned on, What Happens when you Create a User Account with a Password that does not meet the Password Policy?

This was an interesting observation from one of my Windows Server 2012 classes.  While working with the AD Recycle bin in a lab, one of my students discovered some interesting accounts that were created. When he created user accounts that did not meet password complexity requirements, an account is temporarily made and then deleted.  When a new password is provided that meets the password requirements, then a new account is made. We discovered this in two places.  First off in the Active Directory Administrative Center.  This is what caused the initial confusion.  Take a look.  This is in the Deleted Objects OU. You can see multiple deleted accounts for Test2 and one for Test3.  Test3 is a valid, functioning user account.  Using the PowerShell command Get-ADObject –IncludeDeletedObjects –Filter * –Properties ObjectSID we can see that indeed, two accounts were created, with one of them deleted. Notice the RID portion of the SID is different. ...

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...