util: Update GitHub Runners Vagrant to overcommit memory

SE mode tests were failing in some cases where the VM did not have
enough memory to satisfy the constraints of the simulated system. This
change ensures the VM allows overcommitting of memory.

Change-Id: I1800288e16146bdae612a401c2ff282d8664892d
Reviewed-on: https://gem5-review.googlesource.com/c/public/gem5/+/71498
Reviewed-by: Jason Lowe-Power <power.jg@gmail.com>
Tested-by: kokoro <noreply+kokoro@google.com>
Maintainer: Jason Lowe-Power <power.jg@gmail.com>

util/github-runners-vagrant/Vagrantfile-builder

@@ -22,6 +22,11 @@ Vagrant.configure("2") do |config|
   config.vm.provision :shell, privileged: false, path: "provision_nonroot.sh"
   # The provision_root.sh adds the vagrant user to the docker group, so we need to reload the VM.
   config.vm.provision :reload
+  config.vm.provision :shell, run: 'always', inline: <<-SHELL
+    # When running gem5 in SE mode we must overcommit memory.
+    # This is run on every startup of the VM.
+    /sbin/sysctl vm.overcommit_memory=1
+  SHELL
   config.vm.provision :shell, privileged: false, run: 'always', inline: <<-SHELL
     if [ -d ~/actions-runner ]; then
         # This will be run everytime the VM is run (once created).

util/github-runners-vagrant/Vagrantfile-runner

@@ -22,6 +22,11 @@ Vagrant.configure("2") do |config|
   config.vm.provision :shell, privileged: false, path: "provision_nonroot.sh"
   # The provision_root.sh adds the vagrant user to the docker group, so we need to reload the VM.
   config.vm.provision :reload
+  config.vm.provision :shell, run: 'always', inline: <<-SHELL
+    # When running gem5 in SE mode we must overcommit memory.
+    # This is run on every startup of the VM.
+    /sbin/sysctl vm.overcommit_memory=1
+  SHELL
   config.vm.provision :shell, privileged: false, run: 'always', inline: <<-SHELL
     if [ -d ~/actions-runner ]; then
         # This will be run everytime the VM is run (once created).