Dear oVirt,
We are running 4.3.3 oVirt with SHE on three CentOS nodes for HA – with NFS storage.
We also have two Local Storage DCs managed by same SHE.
The issue we are reporting was present on 4.3.2 as well.
The memory usage on both hosts (third one is in maintenance mode) does not go above 45%:
I have also attached the UI Dashboard screenshot.
However, when trying to start one VM:
Engine reports that there is not enough memory and writes the following in the engine.log:
2019-05-14 11:23:10,809Z INFO
[org.ovirt.engine.core.bll.RunVmCommand] (default task-14) [63aa9817-80fd-4b18-8c86-26c910a2954a] Lock Acquired to object 'EngineLock:{exclusiveLocks='[13b2299f-b4b4-48e4-b2f9-09450eff235d=VM]', sharedLocks=''}'
2019-05-14 11:23:10,819Z INFO
[org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand] (default task-14) [63aa9817-80fd-4b18-8c86-26c910a2954a] START, IsVmDuringInitiatingVDSCommand( IsVmDuringInitiatingVDSCommandParameters:{vmId='13b2299f-b4b4-48e4-b2f9-09450eff235d'}),
log id: 5f80129f
2019-05-14 11:23:10,819Z INFO
[org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand] (default task-14) [63aa9817-80fd-4b18-8c86-26c910a2954a] FINISH, IsVmDuringInitiatingVDSCommand, return: false, log id: 5f80129f
2019-05-14 11:23:10,833Z INFO
[org.ovirt.engine.core.bll.scheduling.SchedulingManager] (default task-14) [63aa9817-80fd-4b18-8c86-26c910a2954a] Candidate host 'ovirt-staging-hv-01' ('d81b296a-f3b2-49ea-9b4d-04c90f3508e9') was filtered
out by 'VAR__FILTERTYPE__INTERNAL' filter 'Memory' (correlation id: null)
2019-05-14 11:23:10,833Z INFO
[org.ovirt.engine.core.bll.scheduling.SchedulingManager] (default task-14) [63aa9817-80fd-4b18-8c86-26c910a2954a] Candidate host 'ovirt-staging-hv-02' ('f4fdeccd-4cf4-4ed7-9eb1-d98ac65c4ce6') was filtered
out by 'VAR__FILTERTYPE__INTERNAL' filter 'Memory' (correlation id: null)
2019-05-14 11:23:10,838Z ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-14) [63aa9817-80fd-4b18-8c86-26c910a2954a] EVENT_ID: USER_FAILED_RUN_VM(54), Failed to
run VM csm2-216-d due to a failed validation: [Cannot run VM. There is no host that satisfies current scheduling constraints. See below for details:, The host ovirt-staging-hv-01 did not satisfy internal filter Memory because its available memory is too low
(0 MB) to run the VM., The host ovirt-staging-hv-01 did not satisfy internal filter Memory because its available memory is too low (0 MB) to run the VM.] (User: admin@internal-authz).
2019-05-14 11:23:10,838Z WARN
[org.ovirt.engine.core.bll.RunVmCommand] (default task-14) [63aa9817-80fd-4b18-8c86-26c910a2954a] Validation of action 'RunVm' failed for user admin@internal-authz. Reasons: VAR__ACTION__RUN,VAR__TYPE__VM,SCHEDULING_ALL_HOSTS_FILTERED_OUT,VAR__FILTERTYPE__INTERNAL,$hostName
ovirt-staging-hv-01,$filterName Memory,$availableMem 0,VAR__DETAIL__NOT_ENOUGH_MEMORY,SCHEDULING_HOST_FILTERED_REASON_WITH_DETAIL,VAR__FILTERTYPE__INTERNAL,$hostName ovirt-staging-hv-02,$filterName Memory,$availableMem 0,VAR__DETAIL__NOT_ENOUGH_MEMORY,SCHEDULING_HOST_FILTERED_REASON_WITH_DETAIL
2019-05-14 11:23:10,838Z INFO
[org.ovirt.engine.core.bll.RunVmCommand] (default task-14) [63aa9817-80fd-4b18-8c86-26c910a2954a] Lock freed to object 'EngineLock:{exclusiveLocks='[13b2299f-b4b4-48e4-b2f9-09450eff235d=VM]', sharedLocks=''}'
Current memory optimization is set to “None”
Please let me know if you need additional log files.
Kindly awaiting your reply.
Marko Vrgotic
Sr. System Engineer