none
Big host allows only little vms

    Question

  • I have a Dell T410 with 2 - quad cores and 16GB DRAM.  Host system runs Server2008 R2 and has one active client VM running Server2008 32-bit.  (Required for particular app.)  Initially I was able to run the vm with 4GB DRAM allocated, but after a reboot, the vm would not run and threw error 0x800705AA.  Experimentation revealed that I could run this vm, and any other vm I had created (server 2008 R2, Win7 32-bit, Win7 64-bit) ONLY if I reduce the allocation of DRAM to 1GB.  Logs don;t seem to help and management screens show the host using only about 5GB of the 16GB installed.  Any suggestions for resolving this?  I do need to use 4GB in the 2008 32-bit vm.
    Monday, May 09, 2011 6:57 PM

Answers

  • I would try using Process Explorer from Sysinternals site and sort by Working Set.  Do you see a culprit consuming a lot of RAM?  Also, try using msconfig.exe -> Services -> Check the Hide all Microsoft Services check box and disable all services, reboot.  I saw one or two cases where a 3rd party application was asking the memory manager to reserve excessive RAM at startup when it should not.

    Dave Guenthner [MSFT]

    This posting is provided "AS IS" with no warranties, and confers no rights.
    http://blogs.technet.com/b/davguents_blog/

    Monday, May 09, 2011 9:00 PM

All replies

  • Rich,

    Interesting issue, I have not see this myself but looking at the error:

    0x800705AA = ERROR_NO_SYSTEM_RESOURCES

    I found a KB Article which states that 2008 R2 RTM in some cases exhibits a race condition where task manager shows free RAM but it cannot be allocated.  Can you apply this update to your system and see if helps?

    It is scheduled to be included with SP1.

    The "ZwAllocateVirtualMemory" function fails together with a STATUS_INSUFFICIENT_RESOURCES error randomly when you have sufficient memory in Windows 7 or in Windows Server 2008 R2
    http://support.microsoft.com/kb/983289

    Dave Guenthner [MSFT]
     
    This posting is provided "AS IS" with no warranties, and confers no rights.
     http://blogs.technet.com/b/davguents_blog/

     

    Monday, May 09, 2011 7:26 PM
  • Dave,

     

    I have just attempted to apply this to the server.  Received a "Does not apply to this operating system" sort of message.  I believe that it is because I am already at SP1 on this box, so the fix you recommend has already been applied.  Are there any other thoughts?


    Richard Ploss
    Monday, May 09, 2011 8:32 PM
  • I would try using Process Explorer from Sysinternals site and sort by Working Set.  Do you see a culprit consuming a lot of RAM?  Also, try using msconfig.exe -> Services -> Check the Hide all Microsoft Services check box and disable all services, reboot.  I saw one or two cases where a 3rd party application was asking the memory manager to reserve excessive RAM at startup when it should not.

    Dave Guenthner [MSFT]

    This posting is provided "AS IS" with no warranties, and confers no rights.
    http://blogs.technet.com/b/davguents_blog/

    Monday, May 09, 2011 9:00 PM
  • Hi Richard,

    how much free space has your disc where the VM configuration resists? Maybe the problem is, that Hyper-V creates a memory file for the configured memory and you havent the place for a 4 GB file left? 


    Grüße/Regards Carsten Rachfahl MCT, MCITP, MCSA, CCA, Husband and Papa, www.hyper-v-server.de First German Gold Virtualisation Kompetenz Partner
    Monday, May 09, 2011 9:01 PM