Re: [Xen-users] xe CLI: Error code: MEMORY_CONSTRAINT_VIOLATION - trial XenServer 6.0.2 image has a bug

[Mark Schneider <ms@xxxxxxxxxxxxxxxxxxxxxx>]

Thank you Joseph

Am 20.04.2012 16:40, schrieb Joseph Hom:

That command has always been funny for me. I always needed to specify all 4 fields usually in order of static-min, dynamic-min, dynamic-max, static-max.

Am 20.04.2012 15:04, schrieb James Bulpin:

For this specific question this is not a bug. As the error message states the VM has a constraint that dynamic_min, dynamic_max and static_max must all be equal. Your command is trying to change one of these values in isolation which would break this constraint. I suggest using the CLI command vm-memory-limits-set, e.g.: “xe vm-memory-limits-set uuid=e4f2d301-77d0-6c3f-055a-412f74b3920d dynamic-min=2GiB dynamic-max=2GiB static-max=2GiB static-min=2GiB”.

Due to Citrix there is *not* a bug (thank you very much for the hint James). The free XenServer Version differs from the commercial one (and I guess from XCP 1.5. as it works there a bit different).

I had to use there the following order with the "xe vm-param-set ..." CLI command on XCP 1.5:
memory-static-max
memory-dynamic-max
memory-dynamic-min
memory-static-min

I mean to remember, that other orders gave me error messages (with XCP).

 As an aside it’s worth pointing out that the memory constraints differ between the XenServer Free edition (which don’t have dynamic memory control enabled) “static_min <= dynamic_min = dynamic_max = static_max” and the XenServer paid editions (which do) “static_min <= dynamic_min <= dynamic_max <= static_max”.

The statement above is quite *essential*. For full functionality the commercial (payed) version is required.

regards, Mark

 

From: xen-users-bounces@xxxxxxxxxxxxx [mailto:xen-users-bounces@xxxxxxxxxxxxx] On Behalf Of Mark Schneider
Sent: Thursday, April 19, 2012 7:20 PM
To: xen-users@xxxxxxxxxxxxx; ms@xxxxxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] xe CLI: Error code: MEMORY_CONSTRAINT_VIOLATION - trial XenServer 6.0.2 image has a bug

 

Hello

it looks like the trial XenServer 6.0.2 image has a bug (see below).

# ---
XenServer-6.0.2-free-trial-error.txt
                 memory-actual ( RO): 0
                 memory-target ( RO): <expensive field>
               memory-overhead ( RO): 6291456
             memory-static-max ( RW): 268435456
            memory-dynamic-max ( RW): 268435456
            memory-dynamic-min ( RW): 268435456
             memory-static-min ( RW): 268435456

# ---
[root@dev70 ~]# xe vm-param-set memory-static-max=2GiB name-label=mx70 uuid=e4f2d301-77d0-6c3f-055a-412f74b3920d
Error code: MEMORY_CONSTRAINT_VIOLATION
Error parameters: Memory limits must satisfy: static_min ≤ dynamic_min = dynamic_max = static_max

[root@dev70 ~]# xe vm-param-set memory-static-min=2GiB name-label=mx70 uuid=e4f2d301-77d0-6c3f-055a-412f74b3920d
Error code: MEMORY_CONSTRAINT_VIOLATION
Error parameters: Memory limits must satisfy: static_min ≤ dynamic_min = dynamic_max = static_max

[root@dev70 ~]# xe vm-param-set memory-dynamic-max=2GiB name-label=mx70 uuid=e4f2d301-77d0-6c3f-055a-412f74b3920d
Error code: MEMORY_CONSTRAINT_VIOLATION
Error parameters: Memory limits must satisfy: static_min ≤ dynamic_min = dynamic_max = static_max

[root@dev70 ~]# xe vm-param-set memory-dynamic-min=2GiB name-label=mx70 uuid=e4f2d301-77d0-6c3f-055a-412f74b3920d
Error code: MEMORY_CONSTRAINT_VIOLATION
Error parameters: Memory limits must satisfy: static_min ≤ dynamic_min = dynamic_max = static_max


[root@dev70 ~]# uname -a
Linux dev70 2.6.32.12-0.7.1.xs6.0.2.542.170665xen #1 SMP Tue Jan 17 15:14:24 EST 2012 i686 athlon i386 GNU/Linux
# ---

Does Citrix know already about this issue? Not just the best quality of software ...

regards, Mark

-- 

ms@xxxxxxxxxxxxxxxxxxxxxx

http://rsync.it-infrastrukturen.org

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users