How to increase XOA-memory with XOA

KPS

Hi!

Lately, I had to increase the memory of the XOA-VM.
I tried this through XOA "itself" and failed...

After changing the memory-value for the VM, I thought, it would reboot, but it was shut down and I had to start it manually.

Is this "expected" behaviour? Shouldn't there be a "change after next boot"?

Best wishes
KPS

olivierlambert

In theory, we could tell XO to say "shutdown the VM, change the static memory, and start it". But if you are doing on XO itself, it will obviously stop at "shutdown the VM" since the rest cannot be executed.

It's a chicken-egg problem My advice: just do a quick:

xe vm-memory-limits-set vm=XOA static-min=2GiB dynamic-min=4GiB dynamic-max=8GiB static-max=8GiB

jebrown

@olivierlambert

do you need to edit anything else after increasing the memory for the XOA VM?
on the help guides it says ```
In that case, you need to increase the memory allocated to the XOA VM (from 2GB to 4GB or 8GB). Note that simply increasing the RAM for the VM is not enough. You must also edit the service file (/etc/systemd/system/xo-server.service) to increase the memory allocated to the xo-server process itself.

[link text](https://xen-orchestra.com/docs/troubleshooting.html#configuration)

olivierlambert

It's 2 different things. It's not because you add RAM that you might need to raise the Node memory either. First, add memory and see if it's enough