cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rohit Yadav (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CLOUDSTACK-587) MEMORY_CONSTRAINT_VIOLATIONMemory limits must satisfy:
Date Wed, 05 Dec 2012 20:53:58 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rohit Yadav resolved CLOUDSTACK-587.
------------------------------------

    Resolution: Fixed

Fixed by Anthony on master:
commit 40682fc43dc202b1dbffb4fd32388ad1a46f6e6a
Author: anthony <anthony@cloud.com>
Date:   Wed Dec 5 05:24:46 2012 -0800

    CLOUDSTACK-587:
     use setMemoryLimits instead
                
> MEMORY_CONSTRAINT_VIOLATIONMemory limits must satisfy:
> ------------------------------------------------------
>
>                 Key: CLOUDSTACK-587
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-587
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Anthony Xu
>            Assignee: Anthony Xu
>
> > 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$XenServerCon
> > n
> > ection.dispatch(XenServerConnectionPool.java:909)
> >  at com.xensource.xenapi.VM.setMemoryStaticMin(VM.java:3450)
> > at
> > com.cloud.hypervisor.xen.resource.CitrixResourceBase.setMemory(CitrixR
> > e
> > sourceBase.java:3116)
> >  at
> > com.cloud.hypervisor.xen.resource.CitrixResourceBase.createVmFromTempl
> > a
> > te(CitrixResourceBase.java:985)
> > at
> > com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixRes
> > o
> > urceBase.java:1278)
> >  at
> > com.cloud.hypervisor.xen.resource.XcpOssResource.execute(XcpOssResourc
> > e
> > .java:142)
> > at
> > com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(Ci
> > t
> > rixResourceBase.java:497)
> >  at
> > com.cloud.hypervisor.xen.resource.XcpOssResource.executeRequest(XcpOss
> > R
> > 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.a
> > c
> > cess$301(ScheduledThreadPoolExecutor.java:98)
> >  at
> > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.r
> > u
> > n(ScheduledThreadPoolExecutor.java:206)
> > at
> > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecu
> > t
> > or.java:886)
> >  at
> > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.
> > j
> > ava:908)
> > at java.lang.Thread.run(Thread.java:680)
> > 
> > Regards,
> > 
> > --

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message