 Home |
Products |
Support |
Community |
News |
xen-api
Re: [Xen-API] [XCP] xencenter MEMORY_CONSTRAINT_VIOLATION
| To: | Muriel <mucawhite@xxxxxxxxx> |
|---|---|
| Subject: | Re: [Xen-API] [XCP] xencenter MEMORY_CONSTRAINT_VIOLATION |
| From: | Todd Deshane <todd.deshane@xxxxxxx> |
| Date: | Fri, 9 Sep 2011 23:04:56 -0400 |
| Cc: | xen-api@xxxxxxxxxxxxxxxxxxx |
| Delivery-date: | Fri, 09 Sep 2011 20:05:35 -0700 |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=zTxZSJCADdxZGc82gMxi/0++HyDP9eIpo0TzYWkGhhI=; b=tUOpqVgCGAVCQnThU9aNoA3PhY0WlEUwxdCmyqIw5qywRxKZywyhLkHoYoS+PV8wXn l12PKNICkhHPFfC0a7WSs0oo+j1jyThE0zZFt87zH16vNR/IKVkKbGHkp0GIzSeh9wWq nm+1H8x9qFJbXduGuZ56yO5L2uDjGBF4tAHHU= |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxxx |
| In-reply-to: | <CAHfipj1ZDjSWYtFqu_7K6W9j0AjwGvVWZN+nkfC7-dLWV6-WoA@xxxxxxxxxxxxxx> |
| 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: | <CAHfipj1ZDjSWYtFqu_7K6W9j0AjwGvVWZN+nkfC7-dLWV6-WoA@xxxxxxxxxxxxxx> |
| Sender: | xen-api-bounces@xxxxxxxxxxxxxxxxxxx |
On Fri, Sep 9, 2011 at 9:10 AM, Muriel <mucawhite@xxxxxxxxx> wrote: > Hi all, > when I create a new virtual machine using xencenter (last version) RAM > values are set wrong: > VM.set_memory_dynamic_min: VM = '0a3d5154-2ca6-a47b-c9ee-72fdccc47a8b > (test)'; value = 1073741824 > VM.set_memory_dynamic_range: VM = > 'OpaqueRef:a6af3589-b34c-ad93-38e1-99e1e239ab8c'; min = 1073741824; > max = 268435456 > I've seen this too. I've also seen it with OpenXenManager. The workaround is to set the memory values in the right order on the command line (as to not violate the constraints). Can we trace this back to whether it is a xapi or XenCenter issue and submit the relevant bug? Thanks, Todd -- Todd Deshane http://www.linkedin.com/in/deshantm http://www.xen.org/products/cloudxen.html http://runningxen.com/ _______________________________________________ xen-api mailing list xen-api@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/mailman/listinfo/xen-api |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [Xen-API] Re: ovs-vswitchd high cpu and memory use eventually crashes, Ben Pfaff |
|---|---|
| Next by Date: | Re: [Xen-API] [XCP] xencenter MEMORY_CONSTRAINT_VIOLATION, Muriel |
| Previous by Thread: | [Xen-API] [XCP] xencenter MEMORY_CONSTRAINT_VIOLATION, Muriel |
| Next by Thread: | Re: [Xen-API] [XCP] xencenter MEMORY_CONSTRAINT_VIOLATION, Muriel |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
