Certain tests like testAP spawn two IWD process in separate
namespaces. When --valrind is used this eats up quite a bit
of RAM and causes the VM to run out of memory and start
killing off processes.
---
tools/test-runner | 12 ++++++++++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/tools/test-runner b/tools/test-runner
index b890b3e7..dd4cbf82 100755
--- a/tools/test-runner
+++ b/tools/test-runner
@@ -1570,7 +1570,15 @@ class Main:
else:
smp = int(nproc / 2)
- print("Using %d cores for VM" % smp)
+ #
+ # Increase RAM if valgrind is being used
+ #
+ if self.args.valgrind:
+ ram = 512
+ else:
+ ram = 256
+
+ print("Using %d cores, %d RAM for VM" % (smp, ram))
#
# This passes through most of the command line options to
@@ -1593,7 +1601,7 @@ class Main:
qemu_binary,
'-machine', 'type=q35,accel=kvm:tcg',
'-nodefaults', '-no-user-config', '-monitor', 'none',
- '-display', 'none', '-m', '256M',
'-nographic', '-vga',
+ '-display', 'none', '-m', '%dM' % ram,
'-nographic', '-vga',
'none', '-no-acpi', '-no-hpet',
'-no-reboot', '-fsdev',
'local,id=fsdev-root,path=/,readonly,security_model=none,multidevs=remap',
--
2.26.2
Show replies by date
Hi James,
On 5/3/21 4:30 PM, James Prestwood wrote:
Certain tests like testAP spawn two IWD process in separate
namespaces. When --valrind is used this eats up quite a bit
of RAM and causes the VM to run out of memory and start
killing off processes.
---
tools/test-runner | 12 ++++++++++--
1 file changed, 10 insertions(+), 2 deletions(-)
Applied, thanks.
Regards,
-Denis