Clarification of "VM Limits" in XO
-
The documentation I found on the VM Limits section of the Advanced tab is a bit thin, so I'm just looking to ensure I understand how these options work. I did search the forums and found this old post, which provides a link that is now dead.
-
Are these settings for XCPng/XO to automatically adjust these values based on the load on the host? Or is it just a range that will allow me to manually change while the VM is running?
-
For memory, we are offered both static and dynamic ranges. Can someone explain how these work in detail?
-
-
- Yes and no. Yes only to make more room if it's needed, within the dynamic range given.
- Static is the global range that can be modified only when the VM is halted. Dynamic is the range when the the VM memory can be changed while the VM is running. Obviously, dynamic range is included inside the static one.
Most of the time, except if you have a very good reason for it, do not use dynamic memory.
-
Thanks @olivierlambert, very helpful. It looks like I should learn more about load balancing for managing peak/idle loads more efficiently.
-
O olivierlambert marked this topic as a question on
-
O olivierlambert has marked this topic as solved on
-
@olivierlambert Thanks! Just read this and after experimenting with dynamic memory I see what you mean!
-
@olivierlambert said in Clarification of "VM Limits" in XO:
- Static is the global range that can be modified only when the VM is halted. Dynamic is the range when the the VM memory can be changed while the VM is running. Obviously, dynamic range is included inside the static one.
Most of the time, except if you have a very good reason for it, do not use dynamic memory.
ok.. but if i set memory limit static 1gb-16gb
and dynamic 16gb-16gb XCP assign 16 gb to vm?
the static limit is only a "barrier" for dynamic? -
That's correct
