Cannot adjust memory on Citrix Xen VM

Looks like maybe the xe vm-param-set has changed? see http://forums.citrix.com/thread.jspa?threadID=263740

When I created a test VM on our Citrix XenServer 6.0 host, I selected 512MB of memory. However the VM was created with just 256MB. Trying to adjust this via Cloudmin, I got:

Setting maximum memory allocation to 512 MB .. .. failed : Error code: MEMORY_CONSTRAINT_VIOLATION Error parameters: Memory limits must satisfy: static_min ≤ dynamic_min = dynamic_max = static_max

Setting CPU to Unlimited, and weight to 256 ..

.. already set

Adjusting the memory in XenCenter worked fine.

Status: 
Closed (fixed)

Comments

Thanks for pointing this out - the next Cloudmin release (6.1) will change the order of the parameters to match that posting you linked to.

Looks like 6.1 did not fix this...

Here is how I have been able to set the memory manually:

xe vm-memory-limits-set static-min=256MiB dynamic-min=256MiB dynamic-max=256MiB static-max=256MiB uuid={vm_uuid}

Cloudmin uses a command like :

xe vm-param-set uuid={vm_uuid} memory-static-min=256MiB memory-dynamic-min=256MiB memory-dynamic-max=256MiB memory-static-max=256MiB

does that work for you?

No, it fails:

xe vm-param-set uuid=6e0a4490-f8f3-d55d-252c-b3c0112bb175 memory-static-min=256MiB memory-dynamic-min=256MiB memory-dynamic-max=256MiB memory-static-max=256MiB

Error code: MEMORY_CONSTRAINT_VIOLATION Error parameters: Memory limits must satisfy: static_min ≤ dynamic_min = dynamic_max = static_max

This works though:

xe vm-memory-limits-set static-min=256MiB dynamic-min=256MiB dynamic-max=256MiB static-max=256MiB uuid={vm_uuid}

Thanks for the information - I will update Cloudmin in the next release to use xe vm-memory-limits-set instead. Let me know if you'd like a pre-release or patch for this.

I would be happy to test this out if you want a tester, otherwise I will wait for the next release.

Ok, I have sent you a fix via email..

I can confirm the patch has fixed this, I can now set memory on Citrix Xen VMs correctly! Thanks!

Automatically closed -- issue fixed for 2 weeks with no activity.