Submitted by jasongayson on Thu, 02/07/2013 - 21:09
Let's say I create a virtual machine with 512mb of memory.
Checking the Xen .cfg file, I see "maxmem=4096" as well.
Needs control over that parameter. It's what allows domUs to balloon out of control if they want more than the memory allocated to them.
We created Swap for a reason, and maxmem shouldn't be able to override all of that work.
Status:
Active
Comments
Submitted by JamieCameron on Fri, 02/08/2013 - 00:05 Comment #1
You can control what this gets set to for new VMs at Cloudmin Settings -> Cloudmin Configuration -> Open Source Xen settings -> Maximum memory for Xen instances.
Submitted by jasongayson on Fri, 02/08/2013 - 00:16 Comment #2
Oh. Doesn't that make sense to show as a second value in the Create dialog?
Memory: 1024 - 2048
Submitted by JamieCameron on Fri, 02/08/2013 - 16:55 Comment #3
I don't see how that would be useful, although I may be missing something about how Xen memory allocations work.
Why not set the max memory really high (like 8 GB) when the VM is first created, and then move the actual memory around within that range?
Submitted by aitte on Sat, 02/09/2013 - 19:22 Comment #4
Seems the maxmem is used by the "xm balloon" command which a VM can use to request more than the min-mem it has already been allocated:
http://xen.1045712.n5.nabble.com/confusion-over-memory-maxmem-balloon-et...
Would make sense to configure that per-Vm
Submitted by JamieCameron on Sat, 02/09/2013 - 19:42 Comment #5
Thanks .. it may actually make sense to allow Cloudmin to control the max memory separately. I will look into this further.