How did you increase the memory? It's actually a bit tricky with Xen, as the kernel splits out what's available to the VM guests vs the dom0 host early on. Increasing the RAM for the devcloud guest will just leave more memory for VMs to run in, not create more memory for devcloud itself to run applications.
On Fri, May 24, 2013 at 4:00 PM, Shane Witbeck <sh...@digitalsanctum.com> wrote: > Hi, > > I'm attempting to use the devcloud appliance referenced from the following: > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/DevCloud > > with latest 4.2 code. Everything works great up until the point of spinning > up the system VM's at which time I'm getting: > > WARN [xen.resource.CitrixResourceBase] (DirectAgent-21:) 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:1936) > at com.xensource.xenapi.Connection.dispatch(Connection.java:368) > at > com.cloud.hypervisor.xen.resource.XenServerConnectionPool$XenServerConnection.dispatch(XenServerConnectionPool.java:909) > at com.xensource.xenapi.VM.setMemoryLimits(VM.java:3735) > at > com.cloud.hypervisor.xen.resource.CitrixResourceBase.setMemory(CitrixResourceBase.java:3530) > at > com.cloud.hypervisor.xen.resource.CitrixResourceBase.createVmFromTemplate(CitrixResourceBase.java:1240) > at > com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1582) > at > com.cloud.hypervisor.xen.resource.XcpOssResource.execute(XcpOssResource.java:143) > at > com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:546) > at > com.cloud.hypervisor.xen.resource.XcpOssResource.executeRequest(XcpOssResource.java:137) > at > com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186) > 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.access$301(ScheduledThreadPoolExecutor.java:98) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) > at java.lang.Thread.run(Thread.java:680) > > > > This appears to be coming from the xen api. I have also tried increasing the > amount of memory to devcloud to 3G from the default 2G. > > Any ideas? > > > Thanks, > Shane >
