cloudstack-users-cn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yujiang Pang <yujiang.p...@tieto.com>
Subject Re: 回复: 问题 InsufficientServerCapacityException: Unable to create a deployment for VM[User|vm1]
Date Tue, 24 Jun 2014 03:17:43 GMT
我通过给第二个xen cluster新添加一个主存储解决了这个问题。VM被创建起来了。


On 20 June 2014 17:25, Yujiang Pang <yujiang.pang@tieto.com> wrote:

> 成功了的。初步判断是 “No storage pools available for shared volume allocation,
> returning” 日志里面的这个问题。
>
> 现在Google了下,有个帖子
> http://comments.gmane.org/gmane.comp.apache.cloudstack.user/7871
>  说要给我的第二个xen cluster的host加一个primary,刚试了下, 没有InsuffientServerCapacity了,
> VM还在创建中。
>
>
> On 20 June 2014 16:45, Adagio <68630607@qq.com> wrote:
>
>> 好像host没有被正确识别,你确定添加host成功了吗?
>>
>>
>>
>>
>>
>>
>> ------------------ 原始邮件 ------------------
>> 发件人: "Yujiang Pang";<yujiang.pang@tieto.com>;
>> 发送时间: 2014年6月20日(星期五) 下午4:33
>> 收件人: "users-cn"<users-cn@cloudstack.apache.org>;
>>
>> 主题: Re: 问题 InsufficientServerCapacityException: Unable to create a
>> deployment for VM[User|vm1]
>>
>>
>>
>> hi 大家好,
>>
>> 我按照第一个方法 改好日志输出级别后 发现日志如下, 麻烦大家帮忙看下呢:
>> {{
>> DEBUG [c.c.a.ApiServlet] (catalina-exec-23:ctx-4284f15a ctx-a17c36f3)
>> ===END===  10.121.123.166 -- GET
>>
>>  command=deployVirtualMachine&response=json&sessionkey=S%2FzlgI8p4FapWwN%2BW39POd5RkBs%3D&zoneid=d718cbb3-2a42-47b1-b428-9fe80e6abfef&templateid=ef7f2226-f775-11e3-b668-14feb5e24708&hypervisor=XenServer&serviceofferingid=3ead12b2-77af-4ef5-9fbf-b6b4b313f398&diskofferingid=8257cf83-9328-4ad2-aad2-775de2a17a8f&networkids=90bccdc2-4580-46d4-8e2f-a8f7bed9c6cc&displayname=vm1&name=vm1&_=1403251372470
>> DEBUG [c.c.a.ApiDispatcher] (Job-Executor-2:ctx-6349746a ctx-a17c36f3)
>> InfrastructureEntity name is:com.cloud.offering.ServiceOffering
>> DEBUG [c.c.a.ApiDispatcher] (Job-Executor-2:ctx-6349746a ctx-a17c36f3)
>> ControlledEntity name is:com.cloud.template.VirtualMachineTemplate
>> DEBUG [c.c.a.ApiDispatcher] (Job-Executor-2:ctx-6349746a ctx-a17c36f3)
>> ControlledEntity name is:com.cloud.network.Network
>> DEBUG [c.c.a.ApiDispatcher] (Job-Executor-2:ctx-6349746a ctx-a17c36f3)
>> InfrastructureEntity name is:com.cloud.offering.DiskOffering
>> DEBUG [c.c.n.NetworkModelImpl] (Job-Executor-2:ctx-6349746a ctx-a17c36f3)
>> Service SecurityGroup is not supported in the network id=204
>> DEBUG [c.c.n.NetworkModelImpl] (Job-Executor-2:ctx-6349746a ctx-a17c36f3)
>> Service SecurityGroup is not supported in the network id=204
>> DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Job-Executor-2:ctx-6349746a
>> ctx-a17c36f3) Deploy avoids pods: [], clusters: [], hosts: []
>> DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Job-Executor-2:ctx-6349746a
>> ctx-a17c36f3) DeploymentPlanner allocation algorithm:
>> com.cloud.deploy.FirstFitPlanner@67619b83
>> DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Job-Executor-2:ctx-6349746a
>> ctx-a17c36f3) Trying to allocate a host and storage pools from dc:1,
>> pod:null,cluster:null, requested cpu: 500, requested ram: 536870912
>> DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Job-Executor-2:ctx-6349746a
>> ctx-a17c36f3) Is ROOT volume READY (pool already allocated)?: No
>> DEBUG [c.c.d.FirstFitPlanner] (Job-Executor-2:ctx-6349746a ctx-a17c36f3)
>> Searching all possible resources under this Zone: 1
>> DEBUG [c.c.d.FirstFitPlanner] (Job-Executor-2:ctx-6349746a ctx-a17c36f3)
>> Listing clusters in order of aggregate capacity, that have (atleast one
>> host with) enough CPU and RAM capacity under this Zone: 1
>> DEBUG [c.c.d.FirstFitPlanner] (Job-Executor-2:ctx-6349746a ctx-a17c36f3)
>> Removing from the clusterId list these clusters from avoid set: []
>> DEBUG [c.c.d.FirstFitPlanner] (Job-Executor-2:ctx-6349746a ctx-a17c36f3)
>> Cannot allocate cluster list [1] for vm creation since their allocated
>> percentage crosses the disable capacity threshold defined at each cluster/
>> at global value for capacity Type : 0, skipping these clusters
>> DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Job-Executor-2:ctx-6349746a
>> ctx-a17c36f3) Checking resources in Cluster: 2 under Pod: 1
>> DEBUG [c.c.a.m.a.i.FirstFitAllocator] (Job-Executor-2:ctx-6349746a
>> ctx-a17c36f3 FirstFitRoutingAllocator) Looking for hosts in dc: 1  pod:1
>>  cluster:2
>> DEBUG [c.c.a.m.a.i.FirstFitAllocator] (Job-Executor-2:ctx-6349746a
>> ctx-a17c36f3 FirstFitRoutingAllocator) FirstFitAllocator has 1 hosts to
>> check for allocation: [Host[-4-Routing]]
>> DEBUG [c.c.a.m.a.i.FirstFitAllocator] (Job-Executor-2:ctx-6349746a
>> ctx-a17c36f3 FirstFitRoutingAllocator) Found 1 hosts for allocation after
>> prioritization: [Host[-4-Routing]]
>> DEBUG [c.c.a.m.a.i.FirstFitAllocator] (Job-Executor-2:ctx-6349746a
>> ctx-a17c36f3 FirstFitRoutingAllocator) Looking for speed=500Mhz, Ram=512
>> DEBUG [c.c.c.CapacityManagerImpl] (Job-Executor-2:ctx-6349746a
>> ctx-a17c36f3
>> FirstFitRoutingAllocator) Host: 4 has cpu capability (cpu:2, speed:2926)
>> to
>> support requested CPU: 1 and requested speed: 500
>> DEBUG [c.c.c.CapacityManagerImpl] (Job-Executor-2:ctx-6349746a
>> ctx-a17c36f3
>> FirstFitRoutingAllocator) Checking if host: 4 has enough capacity for
>> requested CPU: 500 and requested RAM: 536870912 ,
>> cpuOverprovisioningFactor: 1.0
>> DEBUG [c.c.c.CapacityManagerImpl] (Job-Executor-2:ctx-6349746a
>> ctx-a17c36f3
>> FirstFitRoutingAllocator) Hosts's actual total CPU: 5852 and CPU after
>> applying overprovisioning: 5852
>> DEBUG [c.c.c.CapacityManagerImpl] (Job-Executor-2:ctx-6349746a
>> ctx-a17c36f3
>> FirstFitRoutingAllocator) Free CPU: 5852 , Requested CPU: 500
>> DEBUG [c.c.c.CapacityManagerImpl] (Job-Executor-2:ctx-6349746a
>> ctx-a17c36f3
>> FirstFitRoutingAllocator) Free RAM: 1186625664 , Requested RAM: 536870912
>> DEBUG [c.c.c.CapacityManagerImpl] (Job-Executor-2:ctx-6349746a
>> ctx-a17c36f3
>> FirstFitRoutingAllocator) Host has enough CPU and RAM available
>> DEBUG [c.c.c.CapacityManagerImpl] (Job-Executor-2:ctx-6349746a
>> ctx-a17c36f3
>> FirstFitRoutingAllocator) STATS: Can alloc CPU from host: 4, used: 0,
>> reserved: 0, actual total: 5852, total with overprovisioning: 5852;
>> requested cpu:500,alloc_from_last_host?:false ,considerReservedCapacity?:
>> true
>> DEBUG [c.c.c.CapacityManagerImpl] (Job-Executor-2:ctx-6349746a
>> ctx-a17c36f3
>> FirstFitRoutingAllocator) STATS: Can alloc MEM from host: 4, used: 0,
>> reserved: 0, total: 1186625664; requested mem:
>> 536870912,alloc_from_last_host?:false ,considerReservedCapacity?: true
>> DEBUG [c.c.a.m.a.i.FirstFitAllocator] (Job-Executor-2:ctx-6349746a
>> ctx-a17c36f3 FirstFitRoutingAllocator) Found a suitable host, adding to
>> list: 4
>> DEBUG [c.c.a.m.a.i.FirstFitAllocator] (Job-Executor-2:ctx-6349746a
>> ctx-a17c36f3 FirstFitRoutingAllocator) Host Allocator returning 1 suitable
>> hosts
>> DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Job-Executor-2:ctx-6349746a
>> ctx-a17c36f3) Checking suitable pools for volume (Id, Type): (5,ROOT)
>> DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Job-Executor-2:ctx-6349746a
>> ctx-a17c36f3) We need to allocate new storagepool for this volume
>> DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Job-Executor-2:ctx-6349746a
>> ctx-a17c36f3) Calling StoragePoolAllocators to find suitable pools
>> DEBUG [o.a.c.s.a.LocalStoragePoolAllocator] (Job-Executor-2:ctx-6349746a
>> ctx-a17c36f3) LocalStoragePoolAllocator trying to find storage pool to fit
>> the vm
>> DEBUG [o.a.c.s.a.ClusterScopeStoragePoolAllocator]
>> (Job-Executor-2:ctx-6349746a ctx-a17c36f3)
>> ClusterScopeStoragePoolAllocator
>> looking for storage pool
>> DEBUG [o.a.c.s.a.ClusterScopeStoragePoolAllocator]
>> (Job-Executor-2:ctx-6349746a ctx-a17c36f3) Looking for pools in dc: 1
>>  pod:1  cluster:2
>> DEBUG [o.a.c.s.a.ClusterScopeStoragePoolAllocator]
>> (Job-Executor-2:ctx-6349746a ctx-a17c36f3) Found pools matching tags: []
>> DEBUG [o.a.c.s.a.ClusterScopeStoragePoolAllocator]
>> (Job-Executor-2:ctx-6349746a ctx-a17c36f3) No storage pools available for
>> shared volume allocation, returning
>> DEBUG [o.a.c.s.a.ZoneWideStoragePoolAllocator]
>> (Job-Executor-2:ctx-6349746a
>> ctx-a17c36f3) ZoneWideStoragePoolAllocator to find storage pool
>> DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Job-Executor-2:ctx-6349746a
>> ctx-a17c36f3) No suitable pools found for volume: Vol[5|vm=4|ROOT] under
>> cluster: 2
>> DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Job-Executor-2:ctx-6349746a
>> ctx-a17c36f3) No suitable pools found
>> DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Job-Executor-2:ctx-6349746a
>> ctx-a17c36f3) No suitable storagePools found under this Cluster: 2
>> DEBUG [c.c.d.DeploymentPlanningManagerImpl] (Job-Executor-2:ctx-6349746a
>> ctx-a17c36f3) Could not find suitable Deployment Destination for this VM
>> under any clusters, returning.
>> DEBUG [c.c.d.FirstFitPlanner] (Job-Executor-2:ctx-6349746a ctx-a17c36f3)
>> Searching all possible resources under this Zone: 1
>> DEBUG [c.c.d.FirstFitPlanner] (Job-Executor-2:ctx-6349746a ctx-a17c36f3)
>> Listing clusters in order of aggregate capacity, that have (atleast one
>> host with) enough CPU and RAM capacity under this Zone: 1
>> DEBUG [c.c.d.FirstFitPlanner] (Job-Executor-2:ctx-6349746a ctx-a17c36f3)
>> Removing from the clusterId list these clusters from avoid set: [2]
>> DEBUG [c.c.d.FirstFitPlanner] (Job-Executor-2:ctx-6349746a ctx-a17c36f3)
>> No
>> clusters found after removing disabled clusters and clusters in avoid
>> list,
>> returning.
>> DEBUG [c.c.v.UserVmManagerImpl] (Job-Executor-2:ctx-6349746a ctx-a17c36f3)
>> Destroying vm VM[User|vm1] as it failed to create on Host with Id:null
>> DEBUG [c.c.c.CapacityManagerImpl] (Job-Executor-2:ctx-6349746a
>> ctx-a17c36f3) VM state transitted from :Stopped to Error with event:
>> OperationFailedToErrorvm's original host id: null new host id: null host
>> id
>> before state transition: null
>> WARN  [o.a.c.alerts] (Job-Executor-2:ctx-6349746a ctx-a17c36f3)
>>  alertType:: 8 // dataCenterId:: 1 // podId:: null // clusterId:: null //
>> message:: Failed to deploy Vm with Id: 4, on Host with Id: null
>> INFO  [o.a.c.a.c.u.v.DeployVMCmd] (Job-Executor-2:ctx-6349746a
>> ctx-a17c36f3) com.cloud.exception.InsufficientServerCapacityException:
>> Unable to create a deployment for VM[User|vm1]Scope=interface
>> com.cloud.dc.DataCenter; id=1
>> INFO  [o.a.c.a.c.u.v.DeployVMCmd] (Job-Executor-2:ctx-6349746a
>> ctx-a17c36f3) Unable to create a deployment for VM[User|vm1]
>> com.cloud.exception.InsufficientServerCapacityException: Unable to create
>> a
>> deployment for VM[User|vm1]Scope=interface com.cloud.dc.DataCenter; id=1
>>         at
>>
>> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:210)
>>         at
>>
>> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:196)
>>         at
>>
>> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3580)
>>
>> }}
>>
>>
>> On 19 June 2014 16:21, Yujiang Pang <yujiang.pang@tieto.com> wrote:
>>
>> > Dear all
>> >
>> > 在创建实例的时候碰到这个问题:
>> > {{
>> > INFO  [o.a.c.a.c.u.v.DeployVMCmd] (Job-Executor-15:ctx-1522f972
>> > ctx-df9998b2) com.cloud.exception.InsufficientServerCapacityException:
>> > Unable to create a deployment for VM[User|vm1]Scope=interface
>> > com.cloud.dc.DataCenter; id=1
>> > INFO  [o.a.c.a.c.u.v.DeployVMCmd] (Job-Executor-15:ctx-1522f972
>> > ctx-df9998b2) Unable to create a deployment for VM[User|vm1]
>> > com.cloud.exception.InsufficientServerCapacityException: Unable to
>> create
>> > a deployment for VM[User|vm1]Scope=interface com.cloud.dc.DataCenter;
>> id=1
>> > }}
>> >
>> > 再往前点日志:
>> > {{
>> >
>> >  INFO  [c.c.h.HighAvailabilityManagerImpl] (HA-2:ctx-6eacae6e) checking
>> health of usage server
>> >
>> > WARN  [o.a.c.alerts] (HA-2:ctx-6eacae6e)  alertType:: 13 //
>> dataCenterId:: 0 // podId:: 0 // clusterId:: null // message:: No usage
>> server process running
>> >
>> > INFO  [c.c.n.v.VpcManagerImpl] (VpcChecker-1:ctx-f93671c3) Found 0
>> removed VPCs to cleanup
>> >
>> > WARN  [c.c.n.NetworkModelImpl] (catalina-exec-18:ctx-4376b0fb
>> ctx-a51a5864) Unable to find provider Netscaler in physical network id=200
>> >
>> > WARN  [c.c.n.NetworkModelImpl] (catalina-exec-21:ctx-58ea5141
>> ctx-272a2b74) Unable to find provider Netscaler in physical network id=200
>> >
>> > WARN  [o.a.c.alerts] (CapacityChecker:ctx-445e0e4f)  alertType:: 0 //
>> dataCenterId:: 1 // podId:: 1 // clusterId:: null // message:: System
>> Alert: Low Available Memory in cluster kvmCluster1 pod pod1 of availability
>> zone C11F13
>> >
>> > INFO  [c.c.a.ApiServer] (catalina-exec-23:ctx-c7f38f38 ctx-b1331d85)
>> The VLAN tag 177 is already being used for dynamic vlan allocation for the
>> guest network in zone C11F13
>> >
>> > WARN  [c.c.n.NetworkModelImpl] (catalina-exec-2:ctx-fe2dede2
>> ctx-0c9ac9f9) Unable to find provider Netscaler in physical network id=200
>> >
>> > WARN  [c.c.n.NetworkModelImpl] (catalina-exec-6:ctx-2d0b6f51
>> ctx-bd984fe7) Unable to find provider Netscaler in physical network id=200
>> >
>> > INFO  [o.a.c.f.j.i.AsyncJobMonitor] (Job-Executor-15:ctx-1522f972) Add
>> job-17 into job monitoring
>> >
>> > WARN  [o.a.c.alerts] (Job-Executor-15:ctx-1522f972 ctx-df9998b2)
>>  alertType:: 8 // dataCenterId:: 1 // podId:: null // clusterId:: null //
>> message:: Failed to deploy Vm with Id: 3, on Host with Id: null
>> > }}
>> > 这里有个警告说的是其中一台KVM内存不足,是因为这台KVM被装了SSVM
CVM系统VM。
>> >
>> > 我有两个host,所以总的系统硬件应该是够了的。附件有截图。
>> >
>> > 我想解决的两个方法:
>> >
>> > 1. 打开更低级别的日志,看有没有更具体的办法?谁知道设置
/etc/cloudstack/management/log4j-cloud.xml
>> > 中的哪项?
>> >
>> > 2. 给那台KVM升级内存,直接关机插内存重启,cloudstack可以自动识别吗?
>> >
>> > 先谢过大家。
>> >
>> > --
>> > BR John (Pang Yujiang)
>> >
>>
>>
>>
>> --
>> BR John (Pang Yujiang)
>>
>
>
>
> --
> BR John (Pang Yujiang)
>



-- 
BR John (Pang Yujiang)

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