Skip to content

Disable VM dynamic memory globally #4661

Open
@Ultra2D

Description

@Ultra2D

Could you enhance XOA to set the XOA instance (or each pool) to use static memory assignment by default, and optionally enforce this?

From xcp-ng/xcp#268 :
I would want a setting that applies to all pools/hosts/whatever managed by XOA. Just set it once in XOA and forget. If it's easier to set it per pool on the settings/servers page, I wouldn't mind.
It would change the default behaviour when creating a VM to use static memory: when changing the RAM field you change Dynamic memory min, Dynamic memory max, Static memory max .

Next, you indeed might or might not want some or all users to be able to override this (later) per VM. In my case it is not needed at all, so block all changes in advanced settings when creating and editing a VM. If someone changes it another way [i.e. outside of XOA], so be it I guess, but other people might think differently about that.

So two settings: default to static memory (yes/no), and allow exceptions (yes/no). These could be conflated into one setting with three options (no/default only/always).
But I realize my use case is quite limited. I'm not sure if others want to actually enforce it (so revert changes made outside of XOA), and have fine-grained permissions.

From #2481:
When adding more RAM on the general tab of a VM, it will switch from static to dynamic. For instance, if a VM previously had 4GB static RAM, then changing it to 8 GB on the general tab, it will have dynamic memory with a minimum of 4 and a maximum of 8 GB. IMHO it should get 8 GB static RAM. Some people might like the current behavior, so possibly it should be a preference you can set somewhere.

According to @julien-f:

The value exposed on the General tab is the dynamic max, not the static max.

Perhaps some people (like me) expect this to be the static max. It is counter-intuitive that a virtual machine that has no dynamic memory will get dynamic memory by adjusting one number, without any indication of that happening. This will cause problems down the line when migrating the VM!
XenCenter exposes this differently. When you change static RAM, you change one number:
"Set a fixed memory of"

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions