[ovirt-users] [SLA] can't start vm due to "host did not satisfy internal filter Memory."

[Roy Golan]

On 02/10/2015 04:13 PM, Artyom Lukianov wrote:
> I checked a little in code, and we have some complicate formula for memory: memory_that_vm_need = host.mem_commited + host.pending_vmem_size + host.guest_overhead + host.reserved_mem + vm.guaranteed_memory
> you can check all parameters for host under vds_dynamic table in database, you can also enable debug logging under engine log t get more details(http://www.ovirt.org/OVirt_Engine_Development_Environment#Enable_DEBUG_log).
> I hope it will help you.
> Thanks
>
> ----- Original Message -----
> From: "Sven Kieske" <s.kieske at mittwald.de>
> To: "Artyom Lukianov" <alukiano at redhat.com>
> Cc: "users at ovirt.org List" <Users at ovirt.org>
> Sent: Tuesday, February 10, 2015 3:29:13 PM
> Subject: Re: [ovirt-users] [SLA] can't start vm due to "host did not satisfy internal filter Memory."
>
>
>
> On 10/02/15 14:03, Artyom Lukianov wrote:
>> Can you also provide value for "Max free Memory for scheduling new VMs" parameter, under REST max_scheduling_memory.
> sure:
>
> with the vm being launched with 28 GB max ram it is:
> Max free Memory for scheduling new VMs:
> 	35617 MB
>
> Before it was way beyond that (I can't shutdown the vm now), obviously
> because of the 200% overcommitment on the cluster.
>
> So imho it should be fine running a vm with 32768 MB RAM defined.
>
> Thanks!
>

Sven is that solved?