Return-Path: X-Original-To: apmail-cloudstack-issues-archive@www.apache.org Delivered-To: apmail-cloudstack-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5006EDE68 for ; Sun, 26 May 2013 07:03:21 +0000 (UTC) Received: (qmail 73842 invoked by uid 500); 26 May 2013 07:03:20 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 73716 invoked by uid 500); 26 May 2013 07:03:20 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 73704 invoked by uid 500); 26 May 2013 07:03:20 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 73696 invoked by uid 99); 26 May 2013 07:03:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 26 May 2013 07:03:20 +0000 Date: Sun, 26 May 2013 07:03:19 +0000 (UTC) From: "Marcus Sorensen (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CLOUDSTACK-2683) creation of system VMs fail when using devcloud MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CLOUDSTACK-2683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13667219#comment-13667219 ] Marcus Sorensen commented on CLOUDSTACK-2683: --------------------------------------------- It's because the tomcat memory limits were raised in 4.1 to deal with the initial memory footprint increase back in Feb. It hasn't run in stock devcloud since. I increased the dom0 memory on mine to make it work. I think there was subsequent work in April or so to get the memory back down, so we may be able to decrease the xmx=2G or whatever it is back down. XCP may not have ever increased their run limit. On Sun, May 26, 2013 at 12:43 AM, Prasanna Santhanam (JIRA) > creation of system VMs fail when using devcloud > ----------------------------------------------- > > Key: CLOUDSTACK-2683 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2683 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the default.) > Components: Install and Setup, Xen > Affects Versions: 4.2.0 > Environment: Host OS is Mac OS X, devcloud 2.0 appliance > Reporter: Shane Witbeck > > Following the devcloud guide [1] in the wiki, I get the following exception when the management server attempts to create system VMs: > 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) > [1] https://cwiki.apache.org/confluence/display/CLOUDSTACK/DevCloud > Verified same setup steps work with 4.1. -- 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