>
>
> <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>> Recently ran into a scenario that a client over committed the
>> available memory in their Hyper-V environment. When a new guest was
>> started-up, the new guest paused (acceptable), however it also paused
>> ALL other guests running on the Hyper-V server (unacceptable). The
>> user wasn't even given a prompt/warning detailing why the server was
>> paused.
>>
>> Is there a way to prevent all servers from being paused when there
>> isn't enough resources.
>>
>> Ideally I would have thought that Hyper-V would be able to detect a
>> lack of resources and wouldn't allow a user to startup a virtual
>> machine without the necessary resources available.
>>
>
> Are you sure that it was a memory problem? Hyper-V does not allow over
> commit of memory. If memory is not available, the vm won't start.
>
> Lack of disk space does cause the vms to pause. There is really no
> alternative if there is nowhere for the OS in the vm(s) to write changes.

> Recently ran into a scenario that a client over committed the
> available memory in their Hyper-V environment. When a new guest was
> started-up, the new guest paused (acceptable), however it also paused
> ALL other guests running on the Hyper-V server (unacceptable). The
> user wasn't even given a prompt/warning detailing why the server was
> paused.
>
> Is there a way to prevent all servers from being paused when there
> isn't enough resources.
>
> Ideally I would have thought that Hyper-V would be able to detect a
> lack of resources and wouldn't allow a user to startup a virtual
> machine without the necessary resources available.
>

> commit of memory. If memory is not available, the vm won't start.
>
> =A0 =A0Lack of disk space does cause the vms to pause. There is really no
> alternative if there is nowhere for the OS in the vm(s) to write changes.