Re: Hyper-V and memory consumption

Reboot and check the RAM - I haven't seen any issues on memory usage not
being what you'd expect. Look for processes that are using more than they
should be.

--
Charlie.
"Roma" <Roma@discussions.microsoft.com> wrote in message
news:131B2408-A2BF-435D-9A28-A9D78272D8B5@microsoft.com...
> Charlie,
>
> I understand why Mike asked this question... With Hyper-V or maybe the way
> Windows Server 2008 works memory gauge is not quite accurate in Task
> Manager.
> I have 32GB RAM on my server and loaded a few VMs for the total of 16GB of
> RAM, so 16GB minus overhead must be still available. Today I tried to add
> another VM and it said I'm out of memory. I open Task Manager on Hyper-V
> server and see that all 32GB are in use, but I know for sure there must be
> about half of the server available.
>
> Any ideas?
>
> --
> Roma
>
>
> "Charlie Russel - MVP" wrote:
>
>> That method is still quite sufficient. Just as with Virtual Server,
>> there's
>> no "shared" memory or thin provisioning of memory for VMs. When a VM is
>> running, it's assigned whatever memory it's going to get, and that's
>> pretty
>> much the end of it.
>>
>> Give yourself somewhere in the range of 384-512 Mb for the parent (more
>> if
>> GUI, less if Core). And assume an overhead on the order of 60-75 Mb per
>> active child partition.
>>
>> --
>> Charlie.
>> http://msmvps.com/blogs/xperts64
>> http://mvp.support.microsoft.com/profile/charlie.russel
>>
>>
>> "Mike" <mhowells@gmail.com> wrote in message
>> news:8e4ffb37-aa25-4dca-88bf-5d483401f01d@m45g2000hsb.googlegroups.com...
>> > What is the best way to determine if Hyper-V is near its physical
>> > memory consumption limit?
>> >
>> > With Virtual Server 2005 running on top of Windows Server 2003 it was
>> > an easy determination. All you had to do was open Task Manager and,
>> > click on the Performance tab and view the available memory in the
>> > Physical Memory section.
>> >
>> > It looks like this method does not work for Hyper-V.
>>
>>