cloudstack-issues mailing list archives

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

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

Prasanna Santhanam commented on CLOUDSTACK-2683:
------------------------------------------------

Fresh deploysvr on devcloud corrects the limits:

[20130526T09:10:15.349Z|debug|devcloud|468 INET 127.0.0.1:80|VM.set_memory_limits R:c098b5a48cb7|audit]
VM.set_memory_limits: self = 0a293520-3189-e45e-45f3-1853ea777202 (s-3-VM); static_min = 33554432;
static_max = 104857600; dynamic_min = 104857600; dynamic_max = 104857600
[20130526T09:10:15.910Z|debug|devcloud|477|Async.VM.start_on R:081685cdad05|xapi] host devcloud;
available_memory = 1580138496; memory_required = 108003328
[20130526T09:10:15.918Z|debug|devcloud|477|Async.VM.start_on R:081685cdad05|memory_control]
logging into ballooning service
[20130526T09:10:15.923Z|debug|devcloud|477|Async.VM.start_on R:081685cdad05|memory_control]
reserve_memory_range min=105472 max=105472
[20130526T09:10:15.925Z|debug|devcloud|477|Async.VM.start_on R:081685cdad05|xenops] watch:
watching xenstore paths: [ /squeezed/rpc/response/reserve-memory-range/6b6755e8-0d19-f40d-2203-2784c6db5c3f
] with timeout 300.000000 seconds
[20130526T09:10:15.934Z|debug|devcloud|477|Async.VM.start_on R:081685cdad05|memory_control]
reserve_memory_range actual = 105472
[20130526T09:10:15.934Z|debug|devcloud|477|Async.VM.start_on R:081685cdad05|memory_control]
reserved_memory = 105472; min = 105472; max = 105472
[20130526T09:10:15.944Z|debug|devcloud|477|Async.VM.start_on R:081685cdad05|memory_control]
transfer_reservation_to_domain de959da1-c1a5-06b1-020a-64950d8d2983 -> 1
[20130526T09:10:15.949Z|debug|devcloud|477|Async.VM.start_on R:081685cdad05|memory_control]
delete_reservation de959da1-c1a5-06b1-020a-64950d8d2983


root@devcloud:/var/log# xe vm-list
uuid ( RO)           : 0a293520-3189-e45e-45f3-1853ea777202
     name-label ( RW): s-3-VM
    power-state ( RO): running


                
> 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