This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-API] XCP BETA BUG: memory limits error

To: Jonathan Knowles <jonathan.knowles@xxxxxxxxxxxxx>
Subject: Re: [Xen-API] XCP BETA BUG: memory limits error
From: George Shuklin <george.shuklin@xxxxxxxxx>
Date: Tue, 20 Sep 2011 12:42:16 +0400
Cc: "xen-api@xxxxxxxxxxxxxxxxxxx" <xen-api@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 20 Sep 2011 02:36:09 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:date :message-id:mime-version:x-mailer:content-transfer-encoding; bh=csxjGVbfvwfXBc/aHL3tYFzDYMr23nx/C85ZdM1qvvE=; b=ntO0n6mj5N55fESo6NP72AYa99DHUWevu6cLgOlEkOwrPhHxolxv/iqLv4BHxt9hSo ZNQvxjB5++QJmShMv3wF9OHw+kT9+gtFDck5qkPh5kZTIrLZgJEhXdFWe/dDTjiyLtg2 64CEVndZV2MbVij4K041YL22gWH0+/OS3g43I=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110919131124.GA4870@radon>
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
References: <1316436591.22917.1.camel@X220> <20110919131124.GA4870@radon>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
How can I debug it? 

In xensource.log I see only this:

[20110919T11:36:42.991Z| info|test|18 unix-RPC|host.set_license_params
R:f8586de1a1d3|license] New pool features enabled: VLAN QoS SStorage
NTAP EQL Pool XHA MTC email perf WLB RBAC DMC chpt DVSC Mask Cnx Plat
nonag VMPR

On Пн., 2011-09-19 at 14:11 +0100, Jonathan Knowles wrote:
> On Mon, Sep 19, 2011 at 01:49:51PM +0100, George Shuklin wrote:
> > xe vm-memory-limits-set uuid=any dynamic-min=128MiB dynamic-max=256MiB
> > static-min=128MiB static-max=256MiB
> > Error parameters: Memory limits must satisfy: static_min ≤ dynamic_min =
> > dynamic_max = static_max
> Normally, we would expect Xapi to apply the following constraint:
>       static_min <= dynamic_min <= dynamic_max <= static_max
> However, when the DMC feature flag is missing, Xapi instead applies
> the following constraint:
>       static_min <= dynamic_min = dynamic_max = static_max
> The following code checks for the DMC feature flag, and chooses the
> more restrictive constraint if the feature flag is not present:
> https://github.com/xen-org/xen-api/blob/master/ocaml/xapi/xapi_vm_memory_constraints.ml
> let assert_valid_and_pinned_at_static_max ~constraints =
>       if not (are_valid_and_pinned_at_static_max ~constraints)
>       then raise (Api_errors.Server_error (
>               Api_errors.memory_constraint_violation,
>                       ["Memory limits must satisfy: \
>                       static_min ≤ dynamic_min = dynamic_max = static_max"]))
> let assert_valid_for_current_context ~__context ~vm ~constraints =
>       (if Db.VM.get_is_control_domain ~__context
>                       ~self:vm || (Pool_features.is_enabled ~__context 
> Features.DMC)
>               then assert_valid
>               else assert_valid_and_pinned_at_static_max)
>       ~constraints
> So, to solve this problem, it's necessary to find out why the
> DMC feature flag is not being set.
> Cheers,
> Jonathan

xen-api mailing list

<Prev in Thread] Current Thread [Next in Thread>