Bug #7166

Vagrant always looks at host memory for RAM building

Added by anonym 2014-05-06 16:06:03 . Updated 2014-07-22 23:06:54 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Build system
Target version:
Tails_1.1
Start date:
2014-05-06
Due date:
% Done:

0%

Feature Branch:
bugfix/7166-vagrant-memory-checks
Type of work:
Code
Blueprint:

Starter:
0
Affected tool:
Deliverable for:

Description

When the Vagrant builder VM is up, our Rakefile checks if enough memory for RAM building is available on the host, which effectively means “can we start another Vagrant VM”. In other words, the current check only makes sense when the VM is off.

When the VM is up we should instead look if the running VM has enough free memory.

Subtasks

History

#1 Updated by anonym 2014-05-06 16:43:54

  • Assignee set to kytv
  • QA Check set to Ready for QA
  • Feature Branch set to bugfix/7166-vagrant-memory-checks

Optimistically assigning kytv for testing, since s/he did the previous Vagrant related test (as no other Tails developer seem to use it).

#2 Updated by kytv 2014-05-08 21:33:17

  • Assignee changed from kytv to anonym
  • % Done changed from 0 to 100
  • QA Check changed from Ready for QA to Pass

It worked for me. As per the post on the mailing list, I started the build with more than 8GB of RAM free then started the VM.

After the VM was started I fired up `memtester` to fill up the RAM on my host. I then started a build. Once live-build kicked in:

vagrant@squeeze:~$ df -h -t tmpfs
Filesystem            Size  Used Avail Use% Mounted on
tmpfs                 3.5G     0  3.5G   0% /lib/init/rw
udev                  3.5G  112K  3.5G   1% /dev
tmpfs                 3.5G     0  3.5G   0% /dev/shm
tmpfs                 6.5G   60M  6.5G   1% /tmp/tmpfs.Cpwm4zQT
vagrant@squeeze:~$ mount -t tmpfs
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /tmp/tmpfs.Cpwm4zQT type tmpfs (rw,noatime,size=6979321856,mode=0770,uid=0,gid=1000)

#3 Updated by anonym 2014-05-08 21:44:15

  • Assignee changed from anonym to intrigeri
  • % Done changed from 100 to 0
  • QA Check changed from Pass to Ready for QA

kytv’s results are expected ones. Thanks a lot, kytv!

intrigeri, re-assigning to you for code review and the final merge into devel.

#4 Updated by intrigeri 2014-05-10 12:40:28

  • Status changed from Confirmed to Fix committed
  • Assignee deleted (intrigeri)
  • QA Check changed from Ready for QA to Pass

Tested and reviewed by kytv, merged.

#5 Updated by BitingBird 2014-06-21 15:49:01

  • Target version set to Tails_1.1

#6 Updated by BitingBird 2014-07-22 23:06:54

  • Status changed from Fix committed to Resolved