>a VM is powered up and operational. If a VM has 1 CPU and 1G memory
>allocations, but it's powered OFF, no resources are affected. (Well,
>except hard drive space of course; VHDs don't go away.)
>
>Correct?
>Reason for asking -- I'm about to create several VMs of different types
>and want to ensure I'm not parsing out all the memory and CPU cycles of
>the box. :-) It seems to be fairly common sensical that the resources
>would only be tapped when the VM is up, but Microsoft does have a habit
>of doing things a bit oddly sometimes....
>Correct me if I'm wrong -- VS2K5 only takes from the resource pool when
>a VM is powered up and operational. If a VM has 1 CPU and 1G memory
>allocations, but it's powered OFF, no resources are affected. (Well,
>except hard drive space of course; VHDs don't go away.)
>
>Correct?
>
>Reason for asking -- I'm about to create several VMs of different types
>and want to ensure I'm not parsing out all the memory and CPU cycles of
>the box. :-) It seems to be fairly common sensical that the resources
>would only be tapped when the VM is up, but Microsoft does have a habit
>of doing things a bit oddly sometimes....
>
>James

> >Correct me if I'm wrong -- VS2K5 only takes from the resource pool when
>>a VM is powered up and operational. If a VM has 1 CPU and 1G memory
>>allocations, but it's powered OFF, no resources are affected. (Well,
>>except hard drive space of course; VHDs don't go away.)
>>
>>Correct?
>
> Yes. There is a tad of overhead for running the virtual Server
> service, but it's pretty negligible.
>
>>Reason for asking -- I'm about to create several VMs of different types
>>and want to ensure I'm not parsing out all the memory and CPU cycles of
>>the box. :-) It seems to be fairly common sensical that the resources
>>would only be tapped when the VM is up, but Microsoft does have a habit
>>of doing things a bit oddly sometimes....
>
> No problem, if it did that, I'd never be able to boot any of my PC's,
> I have far to may VM's!
>
> --
> Bob Comer <Microsoft MVP Windows - Virtual Machine>
>
>
>
> On Wed, 03 Sep 2008 09:45:17 -0400, Noctaire <(email address - cut out)>
> wrote:
>
>>Correct me if I'm wrong -- VS2K5 only takes from the resource pool when
>>a VM is powered up and operational. If a VM has 1 CPU and 1G memory
>>allocations, but it's powered OFF, no resources are affected. (Well,
>>except hard drive space of course; VHDs don't go away.)
>>
>>Correct?
>>
>>Reason for asking -- I'm about to create several VMs of different types
>>and want to ensure I'm not parsing out all the memory and CPU cycles of
>>the box. :-) It seems to be fairly common sensical that the resources
>>would only be tapped when the VM is up, but Microsoft does have a habit
>>of doing things a bit oddly sometimes....
>>
>>James

> >All that being said - a _paused_ VM still uses RAM, if not CPU.
>
> Good point.
>
>>You have to
>>actually shut down the VM if you want to release RAM back to the host.
>
> Or save state -- it releases the RAM too...
>
> --
> Bob Comer
>
>
> On Thu, 4 Sep 2008 06:29:22 -0700, "Charlie Russel - MVP"
> <(email address - cut out)> wrote:
>
>>Yeah, I'd be in BIG trouble if it didn't release resources back!
>>
>>All that being said - a _paused_ VM still uses RAM, if not CPU. You have
>>to
>>actually shut down the VM if you want to release RAM back to the host.

>You have to
>actually shut down the VM if you want to release RAM back to the host.
>Yeah, I'd be in BIG trouble if it didn't release resources back!
>
>All that being said - a _paused_ VM still uses RAM, if not CPU. You have to
>actually shut down the VM if you want to release RAM back to the host.