I somewhat disagree, because sometimes you can have a spike of memory usuage
and if you decide that due to cost swap is the best method for distributing
this spike I would not call that over commiting, just a backup plan that is
cheaper/more realistic than physical RAM. So what I gather from all of this
is that even though microsoft recomends that you do not swap in the guest
Machines, unless you have the luxury of having enough physical RAM to cover
spikes, you are better off placing a swap inside the VM's.
"Paul Adare" <pkadare@xxxxxx> wrote in message
> On Wed, 14 Jan 2009 14:31:55 -0800, news.microsoft.com wrote:
>> Well, coming from a VM world, I had the ability to allocate directly to
>> phsyical RAM or the option to allow some of the RAM for the VM Machines
>> leak into the pagefile. Did I loose this functionality in Hyper-V?
> The feature in VM is over-committing memory and yes, Hyper-V does not
> Paul Adare
> MVP - Identity Lifecycle Manager