Yes, that needs to be something we can tune to help avoid this problem. Or a
way to have it release memory allocated to cache for new VMs.
--
Charlie.
http://msmvps.com/blogs/xperts64 http://mvp.support.microsoft.com/profile/charlie.russel
"Bill Grant" <not.available@xxxxxx> wrote in message
news:uAVZD4tlJHA.1288@xxxxxx
Quote:
>
>
> "Clyde" <none@xxxxxx> wrote in message
> news:99d7edc6-2875-441e-a5a7-7927020cedf9@xxxxxx Quote:
>> Quote:
>>> I have 10 VMs running on my server, using a total of about 25 GB memory.
>>> The system has 32 GB of physical memory.
>>>
>>> When I try to start another VM, I get this:
>>>
>>> CALMACIL failed to initialize.
>>>
>>> Unable to allocate 2048 MB of RAM. Insufficient system resources exist
>>> to
>>> complete the requested service.
>>>
>>> CALMACIL is unable to allocate 2048 MB or RAM. The available memory is
>>> 10728. Insufficient system resources exist to complete the requested
>>> service.
>>>
>>> I use the task manager and I see the following:
>>>
>>> Physical memory:
>>> Total 32765
>>> Cached 9616
>>> Free 1317
>>>
>>> I keep having this problem. I have enough memory to start this VM, but
>>> it
>>> won't start. Has anyone seen this before? Is there a resolution?
>>>
>>> Blake
>>>
>>
>> Just a guess, but, your machine says that it has 1317 MB free, and you're
>> telling VPC to allocate 2048 MB for this additional VM.
>>
>> Not enough memory left?
>>
>> Posted via http://www.VirtualServerFaq.com - Brought to you by Business
>> Information Technology Shop - http://www.bitshop.com >
> That is indeed the problem. Ben Armstrong has discussed this in the past
> in his blog. Hyper-V is fairly aggressive in trying to acquire memory but
> if it can't get enough it will not start a vm. Hyper-V will not
> over-commit memory.
>
> The real problem is that, if you have a lot of free memory, the
> system will use it for caching to speed up access. (Load from memory beats
> load from disk by a big margin). Note the size of the cache figure.