[ https://issues.apache.org/jira/browse/CLOUDSTACK-2554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661555#comment-13661555 ]
ASF subversion and git services commented on CLOUDSTACK-2554: ------------------------------------------------------------- Commit fa086d0bb1d662c82cded083d3e9937349ee5a80 in branch refs/heads/CLOUDSTACK-2554 from [~tsp] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=fa086d0 ] CLOUDSTACK-2554: Ensuring that we honor hypervisor xen's memory constraints When setting memory constraints on Xen guests we should honor: static-min <= dynamic-min <= dynamic-max <= static-max Our VmSpec while allows the guests to like between dynamic-min and dynamic-max the memory set by the resource set the static min to be equal to the dynamic max. This restricts the hypervisor from ensuring optimized memory handling of guests. see: http://wiki.xen.org/wiki/XCP_FAQ_Dynamic_Memory_Control#How_does_XCP_choose_targets_for_guests_in_dynamic_range_mode.3F Another fix was related the restrict_dmc option. when enabled (true) this option disallows scaling a vm. The logic was reverse handled allowing scaling when restrict_dmc was on. This control flow is now fixed. Signed-off-by: Prasanna Santhanam <t...@apache.org> > java.lang.NoSuchMethodException: > com.cloud.hypervisor.xen.resource.XcpServerResource.<init>() > --------------------------------------------------------------------------------------------- > > Key: CLOUDSTACK-2554 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2554 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Affects Versions: 4.1.0 > Environment: Debian, cloudstack builded from git, branch 4.1 > host XCP 1.6 > Reporter: Andrew Artemyev > Priority: Blocker > > CloudStack first start normaly. > I start zone with systemvm`s on local storage > instances work perfectly > but then i reboot management server XCP host switch to disconnected state > in managment server logs i see > 2013-05-17 14:09:41,758 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] > (RouterStatusMonitor-1:null) Found 1 routers to update status. > 2013-05-17 14:09:41,761 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] > (RouterStatusMonitor-1:null) Found 0 networks to update RvR status. > 2013-05-17 14:09:41,851 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] > (RouterStatusMonitor-1:null) Found 1 routers to update status. > 2013-05-17 14:09:41,854 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] > (RouterStatusMonitor-1:null) Found 0 networks to update RvR status. > 2013-05-17 14:09:47,155 DEBUG [agent.manager.ClusteredAgentManagerImpl] > (ClusteredAgentManager Timer:null) Found 1 unmanaged direct hosts, processing > connect for them... > 2013-05-17 14:09:47,155 DEBUG [agent.manager.ClusteredAgentManagerImpl] > (ClusteredAgentManager Timer:null) Loading directly connected host > 3(host1-c1-p1-siberia1.cloud0.omsk.ru) > 2013-05-17 14:09:47,155 WARN [cloud.resource.DiscovererBase] > (ClusteredAgentManager Timer:null) NoSuchMethodException error on > com.cloud.hypervisor.xen.resource.XcpServerResource > java.lang.NoSuchMethodException: > com.cloud.hypervisor.xen.resource.XcpServerResource.<init>() > at java.lang.Class.getConstructor0(Class.java:2733) > at java.lang.Class.getConstructor(Class.java:1676) > at com.cloud.resource.DiscovererBase.getResource(DiscovererBase.java:83) > at > com.cloud.resource.DiscovererBase.reloadResource(DiscovererBase.java:138) > at > com.cloud.agent.manager.AgentManagerImpl.loadDirectlyConnectedHost(AgentManagerImpl.java:767) > at > com.cloud.agent.manager.ClusteredAgentManagerImpl.scanDirectAgentToLoad(ClusteredAgentManagerImpl.java:202) > at > com.cloud.agent.manager.ClusteredAgentManagerImpl.runDirectAgentScanTimerTask(ClusteredAgentManagerImpl.java:168) > at > com.cloud.agent.manager.ClusteredAgentManagerImpl.access$100(ClusteredAgentManagerImpl.java:93) > at > com.cloud.agent.manager.ClusteredAgentManagerImpl$DirectAgentScanTimerTask.run(ClusteredAgentManagerImpl.java:218) > at java.util.TimerThread.mainLoop(Timer.java:534) > at java.util.TimerThread.run(Timer.java:484) > 2013-05-17 14:09:47,160 WARN [agent.manager.AgentManagerImpl] > (ClusteredAgentManager Timer:null) Unable to load the resource: 3 > 2013-05-17 14:09:47,161 DEBUG [cloud.host.Status] (ClusteredAgentManager > Timer:null) Transition:[Resource state = Enabled, Agent event = > AgentDisconnected, Host id = 3, name = host1-c1-p1-siberia1.cloud0.omsk.ru] > 2013-05-17 14:09:47,352 DEBUG [cloud.host.Status] (ClusteredAgentManager > Timer:null) Agent status update: [id = 3; name = > host1-c1-p1-siberia1.cloud0.omsk.ru; old status = Disconnected; event = > AgentDisconnected; new status = Disconnected; old update count = 61; new > update count = 62] -- 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