Bug 579658

Summary:	check-reqs.eclass CHECKREQS_MEMORY doesn't consider memory ballooning used by HyperV
Product:	Gentoo Linux	Reporter:	Ian Guerit <ian.guerit>
Component:	Eclasses	Assignee:	Gentoo Quality Assurance Team <qa>
Status:	RESOLVED NEEDINFO
Severity:	minor	CC:	ian.guerit
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
See Also:	https://bugs.gentoo.org/show_bug.cgi?id=569966
Whiteboard:
Package list:		Runtime testing required:	---

Description Ian Guerit 2016-04-11 19:38:48 UTC

When attempting to emerge an ebuild with CHECKREQS_MEMORY="1024M" in HyperV hosted Gentoo VM, only physical memory size is checked.
On HyperV with memory ballooning enabled, this doesn't reflect memory which could be available.

Would be useful to have method to disable this check, otherwise only other solution is to stop using memory ballooning.

Similar to bug #569966 


Issue as tested:

# emerge mongodb
 * Checking for at least 1024 MiB RAM... 
 * There is NOT at least 1024 MiB RAM

Environment tested:

VM running on HyperV with hv_balloon kernel module enabled and VM configuration as follows:
Startup RAM: 1024MB
Dynamic Memory Minimum: 512MB
Dynamic Memory Maximum: 4096MB

# free -m
              total        used        free      shared  buff/cache   available
Mem:            994         362          10          20         621         573
Swap:           511          61         450

# cat /proc/meminfo
MemTotal:        1018736 kB
MemFree:           10528 kB
MemAvailable:     586864 kB
Buffers:          193580 kB
Cached:           213480 kB
SwapCached:         3236 kB
...
VmallocTotal:   34359738367 kB
VmallocUsed:       36316 kB
VmallocChunk:   34359671776 kB

...
DirectMap4k:       20416 kB
DirectMap2M:     4304896 kB


Source:

/usr/portage/eclass/check-reqs.eclass
# Internal function that checks size of RAM
check-reqs_memory()

Checks only `/proc/meminfo` for MemTotal or `sysctl hw.physmem`

Comment 1 Ian Guerit 2016-04-12 06:07:31 UTC

Cloning the ebuild (and associated files) to a custom overlay and simply removing the line with CHECKREQS_MEMORY, allowed me to work around the issue (for dev-db/mongodb).

Comment 2 Ulrich Müller gentoo-dev

2019-08-20 07:30:24 UTC

Is this still an issue, after bug 569966 has been fixed?

Comment 3 Ulrich Müller gentoo-dev

2021-03-14 17:11:32 UTC

No reply. Closing.