incubator-cloudstack-users-cn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Wayne Wei <wayne.w...@gmail.com>
Subject Re: 答复: VM 停止后不会能启动
Date Fri, 14 Dec 2012 04:54:43 GMT
有的,其它也是一样的都正常运行,后来调整了容量阀值能够起来。就是这个日志太诡异了,应该说容量不够比较好

2012/12/14 Qian Shaohua <qianshaohua@ctsi.com.cn>

> VM用的计算方案要求使用标签为ht-host-77的主机,而没有主机带这个标签。
>
>
> -----邮件原件-----
> 发件人: Wayne Wei [mailto:wayne.weiy@gmail.com]
> 发送时间: 2012年12月14日 11:03
> 收件人: cloudstack-users-cn@incubator.apache.org
> 主题: VM 停止后不会能启动
>
> 一个vm重启后不能启动,错误如下,分析应该是内存分配到85%,但是抛出的错误比较
> 奇怪?有谁了解allocator.impl.FirstFitAllocator分配原理吗
>
> turning 0 suitable hosts
> 2012-12-14 10:32:36,328 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-88:job-94) No suitable hosts found
> 2012-12-14 10:32:36,328 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-88:job-94) No suitable hosts found under this Cluster: 3
> 2012-12-14 10:32:36,329 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-88:job-94) Checking resources in Cluster: 4 under Pod: 1
> 2012-12-14 10:32:36,329 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-88:job-94) Calling HostAllocators to find suitable hosts
> 2012-12-14 10:32:36,329 DEBUG [allocator.impl.FirstFitAllocator]
> (Job-Executor-88:job-94 FirstFitRoutingAllocator) Looking for hosts in dc:
> 1  pod:1  cluster:4
> 2012-12-14 10:32:36,329 DEBUG [allocator.impl.FirstFitAllocator]
> (Job-Executor-88:job-94 FirstFitRoutingAllocator) Looking for hosts having
> tag specified on SvcOffering:ht-host-77
> 2012-12-14 10:32:36,331 DEBUG [allocator.impl.FirstFitAllocator]
> (Job-Executor-88:job-94 FirstFitRoutingAllocator) Hosts with tag
> 'ht-host-77' are:[]
> 2012-12-14 10:32:36,331 DEBUG [allocator.impl.FirstFitAllocator]
> (Job-Executor-88:job-94 FirstFitRoutingAllocator) FirstFitAllocator has 0
> hosts to check for allocation: []
> 2012-12-14 10:32:36,333 DEBUG [allocator.impl.FirstFitAllocator]
> (Job-Executor-88:job-94 FirstFitRoutingAllocator) Found 0 hosts for
> allocation after prioritization: []
> 2012-12-14 10:32:36,333 DEBUG [allocator.impl.FirstFitAllocator]
> (Job-Executor-88:job-94 FirstFitRoutingAllocator) Looking for
> speed=8000Mhz,
> Ram=4000
> 2012-12-14 10:32:36,333 DEBUG [allocator.impl.FirstFitAllocator]
> (Job-Executor-88:job-94 FirstFitRoutingAllocator) Host Allocator returning
> 0 suitable hosts
> 2012-12-14 10:32:36,333 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-88:job-94) No suitable hosts found
> 2012-12-14 10:32:36,333 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-88:job-94) No suitable hosts found under this Cluster: 4
> 2012-12-14 10:32:36,333 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-88:job-94) Could not find suitable Deployment Destination for
> this VM under any clusters, returning.
> 2012-12-14 10:32:36,336 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-88:job-94) VM state transitted from :Starting to Stopped with
> event: OperationFailedvm's original host id: 1 new host id: null host id
> before state transition: null
> 2012-12-14 10:32:36,341 INFO  [cloud.api.ApiDispatcher]
> (Job-Executor-88:job-94) Unable to create a deployment for
> VM[User|i-2-11-VM]
> 2012-12-14 10:32:36,341 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-88:job-94) Complete async job-94, jobStatus: 2, resultCode:
> 530, result: com.cloud.api.response.ExceptionResponse@35dc0aa4
> ^C
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message