Bug 1495213

Summary: Code for dynamic allocation sums memory of VMs without hugepages
Product: [oVirt] vdsm Reporter: Artyom <alukiano>
Component: CoreAssignee: Dan Kenigsberg <danken>
Status: CLOSED CURRENTRELEASE QA Contact: Artyom <alukiano>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.20.4CC: bugs, michal.skrivanek, tjelinek
Target Milestone: ovirt-4.2.0Keywords: Triaged
Target Release: ---Flags: rule-engine: ovirt-4.2+
rule-engine: blocker+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-20 11:35:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
vdsm log none

Description Artyom 2017-09-25 14:03:45 UTC
Created attachment 1330585 [details]
vdsm log

Description of problem:
Code for dynamic allocation sums memory of VMs without hugepages

Version-Release number of selected component (if applicable):
vdsm-4.20.3-88.git6102334.el7.centos.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Configure hugepages on host via "echo 1024 > /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages"
HugePages_Total:    1024
HugePages_Free:     1024
2. Configure two VM's with 1 GB each and with hugepages custom parameters 2048
3. Start VM's

Actual results:
The VDSM allocate additional hugepages
HugePages_Total:    2048
HugePages_Free:     1024

Expected results:
The VDSm use already ready hugepages

Additional info:

Comment 1 Dan Kenigsberg 2017-11-29 15:17:03 UTC
Asking for blocker as Francesco would like this fixed for 4.2.0.

Comment 2 Artyom 2017-12-11 13:21:01 UTC
Verified on vdsm-4.20.9-1.el7ev.x86_64

Comment 3 Sandro Bonazzola 2017-12-20 11:35:26 UTC
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.