incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ram Ganesh <Ram.Gan...@citrix.com>
Subject RE: MEMORY_CONSTRAINT_VIOLATIONMemory limits must satisfy:
Date Tue, 04 Dec 2012 17:11:37 GMT
Google'ing around the exception took me to this link - http://old-list-archives.xen.org/archives/html/xen-api/2009-11/msg00123.html


> -----Original Message-----
> From: Alex Huang [mailto:Alex.Huang@citrix.com]
> Sent: 04 December 2012 22:32
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: MEMORY_CONSTRAINT_VIOLATIONMemory limits must satisfy:
> 
> This is an exception returned by the xapi layer in XenServer.  You can
> track it down further by looking at the xenserver logs on the
> hypervisor the vm tried to start on.  There's a log on
> /var/log/xensource.log.  Look through there and see what it doesn't
> like about the parameter it's trying to set.  My guess is somehow you
> have a mismatch in the client stub version and the server version.
> 
> --Alex
> 
> > -----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$XenServerCo
> > nnection.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.createVmFromTemp
> > late(CitrixResourceBase.java:985)
> > at
> >
> com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixReso
> u
> > rceBase.java:1278)
> >  at
> > com.cloud.hypervisor.xen.resource.XcpOssResource.execute(XcpOssResour
> > ce.java:142)
> > at
> >
> com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(Cit
> r
> > ixResourceBase.java:497)
> >  at
> > com.cloud.hypervisor.xen.resource.XcpOssResource.executeRequest(XcpOs
> > sResource.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
> a
> > va: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