Citrix XenServer resource modification bugs

When managing a Citrix XenServer 5.6 host, Cloudmin 4.7 will correctly increase the size of a virtual drive but not expand the filesystem, and it will not set the specified amount of memory at all - this has to be done with XenCenter.

For example, I created a VM from one of your templates and set the memory to 1GB, instead it was created with 256MB. I shut down the VM and tried to increase the limit with Cloudmin which failed with the following error, so I increased the limit with XenCenter. I started the VM and it had 1GB memory. I then shut down the VM and used Cloudmin to try and lower the memory limit back to 512MB and the original 256MB and received the exact same error I did before for each:

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

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 maximum memory allocation to 256 MB ..
.. failed : Error code: MEMORY_CONSTRAINT_VIOLATION Error parameters: Memory limits must satisfy: static_min ≤ dynamic_min = dynamic_max = static_max
Status: 
Active

Comments

Looks like XenServer 5.6 added a restriction on the way those memory limits to be set that wasn't present in 5.5.. I will update Cloudmin to set all those limits at once, to avoid this error.

Regarding the issue with expanding the virtual drive, did you get any error message during the creation process?

Ok, I see the problem here - the disk and partition do get expanded, but the filesystem does not.

The work-around until Cloudmin 4.8 comes out is to login to the new virtual system and run :

resize2fs /dev/xvda1