Win 8 CP - HyperV Limited to 3 GB of RAM

Unanswered Win 8 CP - HyperV Limited to 3 GB of RAM

  • Monday, May 21, 2012 8:40 AM
     
     

    I use Hyper-V to run a VM Windows 7 Pro to connect to my firm. (1,5 GB Ram)

    I use other VM to create labs to prepare the 70-640 exams. (1 to 2 GB Ram)

    When the total amount of Virtual memory excceed 3GB of RAM on my host, the Hyper-V manager tells me that he can not allocate memory to the virtual machine.

    When I look to my taskmanager, I can see that I have More than 4 GB free !!!

    If I use Dynamic memory, when I have more than 3 GB of Virtual memory allocated VM and Host freeze or crash.

All Replies

  • Monday, May 21, 2012 2:09 PM
     
     

    Hi,

    Please help us to collect the following information so that we can perform the further research.

    1. What’s the amount of the memory on the physical machine?
    2. How many virtual machines did you run on the Hyper-V host machine concurrently?
    3. What’s the amount of the memory assigned to the above virtual machines?

  • Monday, May 21, 2012 2:52 PM
     
     

    My physical computer is a Toshiba Potege Z830 11J

    8 GB Ram and a Core I7 2677M

    OS Windows 8 CP

    I can run more VM if I reduce the amount of RAM of each running VM. The Amount of Ram does not have to exceed 3 GB.

    If I try to launch another VM  and that the amount of RAM exceed 3GB, I recieve this message:

    Unable to allocate 1024 MB of RAM: Ressources système insuffisantes pour terminer le service demandé. (0x800705AA)


    Oncletum

  • Monday, May 21, 2012 3:05 PM
     
     

    The 'management' operating system - the OS you see when you logon to the physical console - requires RAM as well.

    In fact, if you use this as a desktop, it requires more RAM than it would if you were running Hyper-V Server.  Over time, if you do not logoff, there are user processes that slowly consume additional RAM and will result in false reports of not being able to start additional VMs.

    It is these user applications that are not giving up RAM as they should.

    Dynamic Memory being turned on for the VMs should not result in a crash - but you need to make sure that you install the Integration Components into each VM.

    This is why Vincent needs your details.


    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.
    Disclaimer: Attempting change is of your own free will.

  • Monday, May 21, 2012 3:26 PM
     
     

    Even if there is an overhead when the hypervisor allocate the amount of RAM, 1024 MB is less than 3.3 GB (look at the print screen)

    Moreover, it seems that there is a "physical" limit. I tried different configurations with and without Dynamic Memory and there is an error when I need to allocate more than 3 GB of RAM. For the moment, memory is not set to Dynamic, because of the problem.

    I can reproduce the problem on demand, so it does not depend on my host usage. With a standard usage (Office applications and a navigator), there is no need to have more than 2 GB of RAM for a computer. So, even if I have less than 6 GB because of the overhead allocation, I must be able to allocate at least 5 GB. It is not the reality.


    Oncletum

  • Monday, May 21, 2012 3:30 PM
     
     

    Is this Hyper-V on Windows 8 Client?  Or Hyper-V with Server 2012?


    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.
    Disclaimer: Attempting change is of your own free will.

  • Monday, May 21, 2012 4:13 PM
     
     
    I don't know of any limit on the client but I can test it pretty
    quick.
     
    One quick question -- you don't have googlecrashhandler.exe running do
    you?
     
     
     

    Bob Comer - Microsoft MVP Virtual Machine
  • Monday, May 21, 2012 4:26 PM
     
     
    I just started 2 VM's in the consumer Preview that have a total RAM of
    5G, so I don't think you're hitting any kind of hard limit.
     
    check for that googlecrashhandler, I almost bet that's what is messing
    up the memory allocation.
     
     
    It worries me that you crash with dynamic memory set, I'd turn that in
    as a bug for sure of you figure out the other problem.
     
     

    Bob Comer - Microsoft MVP Virtual Machine
  • Monday, May 21, 2012 4:55 PM
     
     

    Hi,

    Yes CP is for Consumer Preview. So it is the client Windows 8, not the server.

    I will check for googlecrashhandler. Thank you.

    If I use Dynamic Memory and if HyperV needs more than 3 GB I have no message, but the system freeze with no warning message.

    I had to make an hard reeboot to restart.


    Oncletum

  • Monday, May 21, 2012 5:38 PM
     
     
    Have you done a physical RAM diagnostic to verify that your RAM is OK? Virtualization tends to stress more of the system than other things and can often bring out hidden faults in the system.
  • Tuesday, May 22, 2012 9:05 AM
     
     

    Hi,

    I tried some configuration.

    Uninstall all google tools and remove directory + reboot => No luck :(

    Uninstall Nero Tools and reboot => It works !!!!

    Install Google Chrome + reboot => It is still working :)

    Thank you Bob Comer you give the solution in another of your post ;) (bad memory allocation by Nero)


    Oncletum

    • Marked As Answer by Oncletum Tuesday, May 22, 2012 9:06 AM
    • Unmarked As Answer by Oncletum Thursday, May 24, 2012 8:14 AM
    •  
  • Tuesday, May 22, 2012 11:27 AM
     
     
    You're welcome.
     
    The nero problem is almost identical to the googlecrashhandler problem
    in the error they made.  Maybe google finally fixed theirs though, and
    that's good news.
     

    Bob Comer - Microsoft MVP Virtual Machine
  • Wednesday, May 23, 2012 9:10 PM
     
     

    Well, I've hit a similar problem, though no Google, no Nero, and no Dynamic memory.  I have one 2GB VM running and I can't start a second 3GB VM.  I have 8GB total, 3.4GB used.

    The VM won't launch until I lower the memory to 1GB.

    Messed around some more and I can't start a single VM with 4GB.  This is a AMD Athlon II X4 CPU (so my understanding is that NUMA is automatically enabled)...is this a revist of the NUMA bug from 2008?
    • Edited by Steve JainMVP Wednesday, May 23, 2012 9:56 PM updated numa
    •  
  • Thursday, May 24, 2012 8:14 AM
     
     

    My problem is still there... :(

    But I have found that if I start my VMs just after the boot, it works.

    If I wait, 5 minutes for exemple, to start my VM the limit is here.

    I have not tried to reinstall my computer yet.

    Perhaps there is a prroblem because the Windows 8 CP on my computer is an upgrade of the Windows 7...

    It is the case for Metro App.

    So can you try to start your VM immediatly after boot and tell us if you have the same behaviour.


    Oncletum

  • Friday, May 25, 2012 7:23 PM
     
     

    Well, I seem to have found the culprit for my issue, Stardock's Start8 utility.

    I uninstalled that and disabled my Teamviewer service and was able to use more than 4GB.  I reenabled Teamviewer and I am still able to use 4GB+.

  • Friday, May 25, 2012 7:32 PM
     
     

    I think that was the point all along.

    It had to be some client applicaiton of some sort that was causing the problem and eating the RAM and thus not allowing the hypervisor to use it. 

    Possibly an application that cannot handle a dynamic memory type of change.


    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.
    Disclaimer: Attempting change is of your own free will.

  • Monday, June 18, 2012 6:06 PM
     
     

    I use C and C++ and most stuff is on the stack where it belongs. Some objects are allocated from the pool with new/delete etc.

    Never seem to have problems with my code anyway.


    Windows MVP 2011-12, XP, Vista, 7 and 8.

    Hardcore Games, Legendary is the only Way to Play

    Developer | Windows IT | Chess | Economics | Vegan Advocate | PC Reviews