cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sebastien Goasguen <run...@gmail.com>
Subject Re: MEMORY_CONSTRAINT_VIOLATIONMemory limits must satisfy:
Date Thu, 21 Feb 2013 20:41:08 GMT
Anthony,

I ran into the CLOUDSTACK-587 bug you created and fixed back in december.

I am running ubuntu 12.04 with latest xcp-xapi and xen 4.1 kernel.

From the bug I can't tell if it was applied to 4.0.1 ? Do you recall ?

-Sebastien

On Dec 5, 2012, at 8:57 PM, Anthony Xu <Xuefei.Xu@citrix.com> wrote:

> https://issues.apache.org/jira/browse/CLOUDSTACK-587
> 
> I filed the bug and fixed it.
> 
> Anthony
> 
>> -----Original Message-----
>> From: Anthony Xu
>> Sent: Wednesday, December 05, 2012 11:29 AM
>> To: cloudstack-dev
>> Subject: RE: MEMORY_CONSTRAINT_VIOLATIONMemory limits must satisfy:
>> 
>> Hi Charles,
>> 
>> This is a bug, have you filed a bug for this?
>> 
>> Anthony
>> 
>>> -----Original Message-----
>>> From: Charles Moulliard [mailto:ch007m@gmail.com]
>>> Sent: Tuesday, December 04, 2012 8:52 AM
>>> To: cloudstack-dev
>>> Subject: Fwd: MEMORY_CONSTRAINT_VIOLATIONMemory limits must satisfy:
>>> 
>>> Hi,
>>> 
>>> How can I figure out this exception when I try to create a new
>> instance
>>> using by example Centos 6.3 ISO (compute offering = 500MHertz, 500MB,
>>> local
>>> storage) ?
>>> 
>>> WARN  [xen.resource.CitrixResourceBase] (DirectAgent-36:) Catch
>>> Exception:
>>> class com.xensource.xenapi.Types$XenAPIException due to
>>> MEMORY_CONSTRAINT_VIOLATIONMemory limits must satisfy: static_min ?
>>> dynamic_min ? dynamic_max ? static_max
>>> MEMORY_CONSTRAINT_VIOLATIONMemory limits must satisfy: static_min ?
>>> dynamic_min ? dynamic_max ? static_max
>>> at com.xensource.xenapi.Types.checkResponse(Types.java:1732)
>>> at com.xensource.xenapi.Connection.dispatch(Connection.java:368)
>>> at
>>> 
>> com.cloud.hypervisor.xen.resource.XenServerConnectionPool$XenServerConn
>>> ection.dispatch(XenServerConnectionPool.java:909)
>>> at com.xensource.xenapi.VM.setMemoryStaticMin(VM.java:3450)
>>> at
>>> 
>> com.cloud.hypervisor.xen.resource.CitrixResourceBase.setMemory(CitrixRe
>>> sourceBase.java:3116)
>>> at
>>> 
>> com.cloud.hypervisor.xen.resource.CitrixResourceBase.createVmFromTempla
>>> te(CitrixResourceBase.java:985)
>>> at
>>> 
>> com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixReso
>>> urceBase.java:1278)
>>> at
>>> 
>> com.cloud.hypervisor.xen.resource.XcpOssResource.execute(XcpOssResource
>>> .java:142)
>>> at
>>> 
>> com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(Cit
>>> rixResourceBase.java:497)
>>> at
>>> 
>> com.cloud.hypervisor.xen.resource.XcpOssResource.executeRequest(XcpOssR
>>> esource.java:136)
>>> at
>>> 
>> com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.
>>> java:191)
>>> at
>>> 
>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
>>> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>>> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>>> at
>>> 
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.ac
>>> cess$301(ScheduledThreadPoolExecutor.java:98)
>>> at
>>> 
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.ru
>>> n(ScheduledThreadPoolExecutor.java:206)
>>> at
>>> 
>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecut
>>> or.java:886)
>>> at
>>> 
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.j
>>> ava:908)
>>> at java.lang.Thread.run(Thread.java:680)
>>> 
>>> Regards,
>>> 
>>> --
>>> Charles Moulliard
>>> Apache Committer / Sr. Enterprise Architect (RedHat)
>>> Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com
>>> 
>>> 
>>> 
>>> 
>>> 
>>> --
>>> Charles Moulliard
>>> Apache Committer / Sr. Enterprise Architect (RedHat)
>>> Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com


Mime
View raw message