cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Sorensen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-2683) creation of system VMs fail when using devcloud
Date Sun, 26 May 2013 07:10:20 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-2683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13667220#comment-13667220
] 

Marcus Sorensen commented on CLOUDSTACK-2683:
---------------------------------------------

I should say that it randomly fails with the larger memory limits (as
the process grows it eventually causes problems), if dom0 has a small
amount of memory like devcloud does. Shane said in a previous message
that 4.1 works. So I'm not entirely sure, but one thing to check at
least would be that the java process isn't asking for as much or more
memory than dom0 has.


                
> 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

Mime
View raw message