February 24, 201412 yr Hi, I am running Arch VM on v6 beta 3. Following ironicbadgers guide installing arch was simple and quick. I currently have 12gb of memory installed and 2 are given to dom0 I am however having trouble utilizing all my ram. I understand that dom0 has a max limit set in the syslinux.cfg. I would like to assign the rest of my available memory to the archVM. When I attempt to assign any more than 1024mb to arch via the arch.cfg or terminal I receive errors as: libxl: error: libxl.c:3717:libxl_set_memory_target: memory_dynamic_max must be less than or equal to memory_static_max xentop - 00:08:20 Xen 4.3.1 2 domains: 1 running, 1 blocked, 0 paused, 0 crashed, 0 dying, 0 shutdown Mem: 12581364k total, 3289836k used, 9291528k free CPUs: 8 @ 2698MHz NAME STATE CPU(sec) CPU(%) MEM(k) MEM(%) MAXMEM(k) MAXMEM(%) VCPUS NETS NETTX(k) NETRX(k) VBDS VBD_OO VBD_RD VBD_WR VBD_RSECT VBD_WSECT SS ID archVM --b--- 2814 0.7 1048576 8.3 2098176 16.7 8 1 7539537 145658 0 0 0 0 0 0 0 Domain-0 -----r 487 0.8 2097152 16.7 no limit n/a 8 0 0 0 0 0 0 0 0 0 0 Sorry if this is a simple resolution.... my linux skills are only so so. Thanks so much for your help syslog.txt
February 24, 201412 yr Author Here is my .cfg file. This is the one that is currently working. If i raise the memory to anything larger, lets say something like 2048, then I receive errors similar to the ones in the first post, claiming that there is not enough memory. name = "archVM" bootloader = "pygrub" memory = 1024 vcpus = '8' disk = [ 'phy:/mnt/cache/ArchVM/arch.img,xvda,w', 'phy:/mnt/cache/ArchVM/data.img,xvdb,w' ] vif = [ 'mac=00:16:3e:a1:b2:c3,bridge=br0' ]
February 24, 201412 yr It is correctly picking up the 1gb assignment in the file as you have it set. Also xentop is showing your 12gb. So just replace 1024 with 4096. Can't see why that wouldn't work.
February 25, 201412 yr Author I don't understand why that wasn't working yesterday but after re-editing the .cfg file I am no longer receiving errors. Perhaps my text editor was inserting some invisible characters causing the issues. Anyway, the issue seems to be resolved now. Thank you so much.
Archived
This topic is now archived and is closed to further replies.