vagrant: Use memory size setting
authorMartin Schwenke <martin@meltin.net>
Wed, 4 Dec 2019 23:52:13 +0000 (10:52 +1100)
committerMartin Schwenke <martin@meltin.net>
Wed, 4 Dec 2019 23:52:13 +0000 (10:52 +1100)
This doesn't look to have been a vagrant-libvirt bug.  It looks to
have been the use of "mem" instead of "memory" as the configuration
key.

Signed-off-by: Martin Schwenke <martin@meltin.net>
defaults.yml
vagrant/Vagrantfile

index 7b061df75eefd460e885f1b21d1e2cb423e03eea..fb05a86bf2947dd32d090c5aa0a2364ee0596821 100644 (file)
@@ -25,8 +25,7 @@ vagrant_provider: libvirt
 node_list: [nas, nas, nas, nas, base]
 
 cpus: 2
-# mem is currently ignored due to a libvirt provider bug
-mem: 1024
+memory: 2048
 
 # Block devices shared between nodes, used for cluster filesystem
 shared_disks:
index 7ae6a6522b74f1152e32103782c984f729fa3c51..120b054b44caa0bf3a6efef6bc00bc73603d40ad 100644 (file)
@@ -86,7 +86,7 @@ Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
 
         libvirt.default_prefix = 'autocluster'
         libvirt.cpus = settings['cpus']
-        #FIXME: causes an error ### libvirt.memory = settings['memory']
+        libvirt.memory = settings['memory']
 
         if node['has_shared_storage']
           for i in 1..settings['shared_disks']['count']