Vista Tutorial - Hyper-V memory allocation error

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

"Clyde" <none@xxxxxx> wrote in message
news:99d7edc6-2875-441e-a5a7-7927020cedf9@xxxxxxThat 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.

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

Blake - take a look at http://support.microsoft.com/kb/953585. There's a hot
fix, but you'll have to call for it. Not sure that's it, but it sounds
possible.

--
Charlie.
http://msmvps.com/blogs/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel

"Blake" <blake.duffey@xxxxxx> wrote in message
news:%23hgLvGrlJHA.2384@xxxxxx

I realize what Task Manager says - but in reality I should have nearly 10 GB
left

Hyper-V sees 10 GB, per the message about available memory. Why is the
system caching 9.5 GB? And why does a cache make that completely
unavailable??

Blake

"Clyde" <none@xxxxxx> wrote in message
news:99d7edc6-2875-441e-a5a7-7927020cedf9@xxxxxx

It just seems odd to me that the cache would be 'locked' so to speak and
disallow further VM allocation. I would expect the cache to be used as
needed, but if another VM is allocated the cache would lose out. (cache is
a luxury, in that instance)

I hadn't seen that on Armstrong's blog. Do you have a date or URL?

Thanks
Blake


"Bill Grant" <not.available@xxxxxx> wrote in message
news:uAVZD4tlJHA.1288@xxxxxx

Thanks Charlie.

I'll look into that.

Blake

"Charlie Russel - MVP" <charlie@xxxxxx> wrote in message
news:uOdcol6lJHA.3644@xxxxxx

I think that's it.

I can download the link for the Vista fix, but not the 2k8..

grrr...

now have to waste all day on phone..

Thanks again,
Blake

"Charlie Russel - MVP" <charlie@xxxxxx> wrote in message
news:uOdcol6lJHA.3644@xxxxxx

Shouldn't be that bad to get it. Most hotfix calls are pretty quick. Let us
know if it solves it, please.

--
Charlie.
http://msmvps.com/blogs/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel

"Blake" <blake.duffey@xxxxxx> wrote in message
news:uehjiREmJHA.4540@xxxxxx

After much time on the phone they told me to run the Vista patch on Windows
Server

It installed on one machine without problem - I need some downtime to
install on the machine where I was actually seeing the
problem

B

"Bruce Sanderson" <bsanders@xxxxxx> wrote in message
news:Oms9JarmJHA.4520@xxxxxx