Dear oVirt,

I need help clarifying how internal memory filter is used, at which values it looks at.

The log message below is clear, but I am failing to see from where are the memory values calculated, is it based on Guarenteed, Allocated or MaxAvailable memory a VM can get/have? Or something else.

We have a shared cluster, with hosts having different memory amount:

Tried to create 17VMs, and following errors were observed:

2019-09-20 11:46:10,496Z WARN  [org.ovirt.engine.core.bll.RunVmCommand] (EE-ManagedThreadFactory-engine-Thread-967) [2d316914-84dc-4410-856f-f8576e411574] Validation of action 'RunVm' failed for user mvrgotic@ictv.com@ictv.com-authz. Reasons: VAR__ACTION__RUN,VAR__TYPE__VM,SCHEDULING_ALL_HOSTS_FILTERED_OUT,VAR__FILTERTYPE__INTERNAL,$hostName ovirt-hv-08.avinity.tv,$filterName Memory,$availableMem 3513,VAR__DETAIL__NOT_ENOUGH_MEMORY,SCHEDULING_HOST_FILTERED_REASON_WITH_DETAIL,VAR__FILTERTYPE__INTERNAL,$hostName ovirt-hv-02.avinity.tv,$filterName Memory,$availableMem 1605,VAR__DETAIL__NOT_ENOUGH_MEMORY,SCHEDULING_HOST_FILTERED_REASON_WITH_DETAIL,VAR__FILTERTYPE__INTERNAL,$hostName ovirt-hv-05.avinity.tv,$filterName Memory,$availableMem 1265,VAR__DETAIL__NOT_ENOUGH_MEMORY,SCHEDULING_HOST_FILTERED_REASON_WITH_DETAIL,VAR__FILTERTYPE__INTERNAL,$hostName ovirt-hv-20.avinity.tv,$filterName Memory,$availableMem 195,VAR__DETAIL__NOT_ENOUGH_MEMORY,SCHEDULING_HOST_FILTERED_REASON_WITH_DETAIL,VAR__FILTERTYPE__INTERNAL,$hostName ovirt-hv-01.avinity.tv,$filterName Memory,$availableMem 177,VAR__DETAIL__NOT_ENOUGH_MEMORY,SCHEDULING_HOST_FILTERED_REASON_WITH_DETAIL,VAR__FILTERTYPE__INTERNAL,$hostName ovirt-hv-06.avinity.tv,$filterName Memory,$availableMem 2845,VAR__DETAIL__NOT_ENOUGH_MEMORY,SCHEDULING_HOST_FILTERED_REASON_WITH_DETAIL,VAR__FILTERTYPE__INTERNAL,$hostName ovirt-hv-09.avinity.tv,$filterName Memory,$availableMem 480,VAR__DETAIL__NOT_ENOUGH_MEMORY,SCHEDULING_HOST_FILTERED_REASON_WITH_DETAIL,VAR__FILTERTYPE__INTERNAL,$hostName ovirt-hv-03.avinity.tv,$filterName Memory,$availableMem 3116,VAR__DETAIL__NOT_ENOUGH_MEMORY,SCHEDULING_HOST_FILTERED_REASON_WITH_DETAIL,VAR__FILTERTYPE__INTERNAL,$hostName ovirt-hv-21.avinity.tv,$filterName Memory,$availableMem 1342,VAR__DETAIL__NOT_ENOUGH_MEMORY,SCHEDULING_HOST_FILTERED_REASON_WITH_DETAIL

2019-09-20 11:46:10,577Z INFO  [org.ovirt.engine.core.bll.scheduling.SchedulingManager] (EE-ManagedThreadFactory-engine-Thread-851) [2d316914-84dc-4410-856f-f8576e411574] Candidate host 'ovirt-hv-08.avinity.tv' ('adebaa4f-5402-47c7-8634-5779a4b3f10f') was filtered out by 'VAR__FILTERTYPE__INTERNAL' filter 'Memory' (correlation id: null)

To provide you with bit more detail on our Cluster setup:

oVirt SHE 4.3.4.3-1

Cluster Settings and Hosts actual memory usage

And here is the VM information”

Name: testvmmvr-th11stitcher

Defined Memory: 4096 MB

Origin: oVirt

Description:

Physical Memory Guaranteed: 1024 MB

Run On: Any Host in Cluster

Template: av-centos-75-baseimage (Thin/Dependent)

Guest OS Memory Free/Cached/Buffered: 3453 / 2 / 156 MB

Custom Properties: Not Configured

Operating System: Red Hat Enterprise Linux 7.x x64

Number of CPU Cores: 4 (1:4:1)

Cluster Compatibility Version: 4.3

BIOS Type: Default

Guest CPU Count: 4

VM ID: testvmmvr

Graphics protocol: VNC

Guest CPU Type: SandyBridge,+pcid,+spec-ctrl,+ssbd

Video Type: QXL

Highly Available: No

Priority: Low

Number of Monitors: 1

FQDN: testvmmvr-th11stitcher

Optimized for: Server

USB Policy: Disabled

Hardware Clock Time Offset: Etc/GMT

Created By: Deployment User

Kindly awaiting your reply.

If any data is missing, please let me know.

— — —
Met vriendelijke groet / Kind regards,

Marko Vrgotic