locked
Dynamic Memory Not Working for me RRS feed

  • Question

  • I have installed SP1 on Server 2008 R2 Enterprise.  Using Hyper-V Manager, I've set dynamic allocation to 512 min and 2048 max.  The VM, when booted, will not pass the 512 MB RAM and it's memory is almost topped, but the OS keeps paging and never passes the 512.


    Am I missing a step?

    Thanks.

    Thursday, July 22, 2010 1:42 AM

Answers

  • The most common causes I have seen for this are:

    1. The new R2 SP1 Integration Services are not installed in the VM (you can tell if this is installed if you see the memory available column populated for the VM in Hyper-V Manager)

    2. The Guest OS is not a compatible operating system

     

    Here is a list of compatible guest operating systems for Dynamic memory

    Windows Server 2008 R2 Enterprise Edition
    Windows Server 2008 R2 Datacenter Edition
    Windows 7 Ultimate Edition (32-bit and 64-bit)
    Windows 7 Enterprise Edition (32-bit and 64-bit)
    Windows Server 2008 Enterprise Edition (32-bit and 64-bit)
    Windows Server 2008 Datacenter Edition (32-bit and 64-bit)
    Windows Vista Ultimate Edition with Service Pack 1 (SP1) (32-bit and 64-bit)
    Windows Vista Enterprise Edition with Service Pack 1 (SP1) (32-bit and 64-bit)
    Windows Server 2003 R2 Enterprise Edition with Service Pack 2 (SP2) (32-bit and 64-bit)
    Windows Server 2003 R2 Datacenter Edition with Service Pack 2 (SP2) (32-bit and 64-bit)
    Windows Server 2003 Enterprise Edition with Service Pack 2 (SP2) (32-bit and 64-bit)
    Windows Server 2003 Datacenter Edition with Service Pack 2 (SP2) (32-bit and 64-bit)

    Thursday, July 22, 2010 6:00 AM
  • Brent has it right on - you must upgrade the ICs in ths OS of the VM. for Dynamic memory to work, and your OS must be on the Beta support list.

    There are two lists for VM OS support - one is for hte final release of the SP1 and the other is for the Beta release of SP1.

    http://blogs.msdn.com/b/virtual_pc_guy/archive/2010/07/12/dynamic-memory-beta-supported-guest-operating-systems.aspx


    Brian Ehlert (hopefully you have found this useful)
    • Marked as answer by BrianEhMVP Thursday, July 22, 2010 3:04 PM
    Thursday, July 22, 2010 3:04 PM

All replies

  • The most common causes I have seen for this are:

    1. The new R2 SP1 Integration Services are not installed in the VM (you can tell if this is installed if you see the memory available column populated for the VM in Hyper-V Manager)

    2. The Guest OS is not a compatible operating system

     

    Here is a list of compatible guest operating systems for Dynamic memory

    Windows Server 2008 R2 Enterprise Edition
    Windows Server 2008 R2 Datacenter Edition
    Windows 7 Ultimate Edition (32-bit and 64-bit)
    Windows 7 Enterprise Edition (32-bit and 64-bit)
    Windows Server 2008 Enterprise Edition (32-bit and 64-bit)
    Windows Server 2008 Datacenter Edition (32-bit and 64-bit)
    Windows Vista Ultimate Edition with Service Pack 1 (SP1) (32-bit and 64-bit)
    Windows Vista Enterprise Edition with Service Pack 1 (SP1) (32-bit and 64-bit)
    Windows Server 2003 R2 Enterprise Edition with Service Pack 2 (SP2) (32-bit and 64-bit)
    Windows Server 2003 R2 Datacenter Edition with Service Pack 2 (SP2) (32-bit and 64-bit)
    Windows Server 2003 Enterprise Edition with Service Pack 2 (SP2) (32-bit and 64-bit)
    Windows Server 2003 Datacenter Edition with Service Pack 2 (SP2) (32-bit and 64-bit)

    Thursday, July 22, 2010 6:00 AM
  • Brent has it right on - you must upgrade the ICs in ths OS of the VM. for Dynamic memory to work, and your OS must be on the Beta support list.

    There are two lists for VM OS support - one is for hte final release of the SP1 and the other is for the Beta release of SP1.

    http://blogs.msdn.com/b/virtual_pc_guy/archive/2010/07/12/dynamic-memory-beta-supported-guest-operating-systems.aspx


    Brian Ehlert (hopefully you have found this useful)
    • Marked as answer by BrianEhMVP Thursday, July 22, 2010 3:04 PM
    Thursday, July 22, 2010 3:04 PM
  • That was exactly it, thanks both for your answer.  My OS was supported, the problem was due to the Integration Services.

    Thursday, July 22, 2010 5:13 PM