cloudstack-users-cn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Royal Yang <rayang2...@gmail.com>
Subject Re: 如果加上data卷就不能启动
Date Wed, 13 May 2015 09:30:17 GMT
secondary storage 是不是有问题,要不检查s 虚拟机是否启动正常?

2015-05-13 9:35 GMT+08:00 20400992@qq.com <20400992@qq.com>:

>
>
> 我有20及个VM。凡是带有root+data卷的都不能启动,但是带有root卷的都能启动。有management-server.log和catalina.out
>
> management-server的日志如下:
>
>
> 2015-05-11 17:44:40,984 DEBUG [cloud.api.ApiServlet]
> (catalina-exec-2:null) ===START===  192.168.30.15 -- GET
> command=startVirtualMachine&id=57235500-a144-4ef9-9c54-127bfcbbe2bf&response=json&sessionkey=EAUq4gPt8MHpLGiP8Jg%2FTF4So90%3D&_=1431338025150
> 2015-05-11 17:44:41,055 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-2:null) submit async job-86, details: AsyncJobVO {id:86,
> userId: 2, accountId: 2, sessionKey: null, instanceType: VirtualMachine,
> instanceId: 41, cmd: com.cloud.api.commands.StartVMCmd, cmdOriginator:
> null, cmdInfo:
> {"response":"json","id":"57235500-a144-4ef9-9c54-127bfcbbe2bf","sessionkey":"EAUq4gPt8MHpLGiP8Jg/TF4So90\u003d","ctxUserId":"2","_":"1431338025150","ctxAccountId":"2","ctxStartEventId":"260"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 163683356600315,
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2015-05-11 17:44:41,056 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-37:job-86) Executing com.cloud.api.commands.StartVMCmd for
> job-86
> 2015-05-11 17:44:41,057 DEBUG [cloud.api.ApiServlet]
> (catalina-exec-2:null) ===END===  192.168.30.15 -- GET
> command=startVirtualMachine&id=57235500-a144-4ef9-9c54-127bfcbbe2bf&response=json&sessionkey=EAUq4gPt8MHpLGiP8Jg%2FTF4So90%3D&_=1431338025150
> 2015-05-11 17:44:41,103 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-37:job-86) VM state transitted from :Stopped to Starting with
> event: StartRequestedvm's original host id: 5 new host id: null host id
> before state transition: null
> 2015-05-11 17:44:41,103 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-37:job-86) Successfully transitioned to start state for
> VM[User|TestMachine] reservation id = 0f80b148-9b51-434e-97fd-79f090a0383b
> 2015-05-11 17:44:41,132 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-37:job-86) Trying to deploy VM, vm has dcId: 1 and podId: 1
> 2015-05-11 17:44:41,132 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-37:job-86) Deploy avoids pods: null, clusters: null, hosts:
> null
> 2015-05-11 17:44:41,133 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-37:job-86) Root volume is ready, need to place VM in volume's
> cluster
> 2015-05-11 17:44:41,133 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-37:job-86) Vol[48|vm=41|ROOT] is READY, changing deployment
> plan to use this pool's dcId: 1 , podId: 1 , and clusterId: 1
> 2015-05-11 17:44:41,133 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) DeploymentPlanner allocation algorithm: random
> 2015-05-11 17:44:41,133 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) Trying to allocate a host and storage pools from
> dc:1, pod:1,cluster:1, requested cpu: 4000, requested ram: 4294967296
> 2015-05-11 17:44:41,133 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) Is ROOT volume READY (pool already allocated)?: Yes
> 2015-05-11 17:44:41,133 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) This VM has last host_id specified, trying to
> choose the same host: 5
> 2015-05-11 17:44:41,135 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-37:job-86) Checking if host: 5 has enough capacity for
> requested CPU: 4000 and requested RAM: 4294967296 ,
> cpuOverprovisioningFactor: 1.0
> 2015-05-11 17:44:41,135 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-37:job-86) Hosts's actual total CPU: 27136 and CPU after
> applying overprovisioning: 27136
> 2015-05-11 17:44:41,135 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-37:job-86) We need to allocate to the last host again, so
> checking if there is enough reserved capacity
> 2015-05-11 17:44:41,135 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-37:job-86) Reserved CPU: 4000 , Requested CPU: 4000
> 2015-05-11 17:44:41,135 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-37:job-86) Reserved RAM: 4294967296 , Requested RAM:
> 4294967296
> 2015-05-11 17:44:41,135 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-37:job-86) Host has enough CPU and RAM available
> 2015-05-11 17:44:41,136 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-37:job-86) STATS: Can alloc CPU from host: 5, used: 13500,
> reserved: 4000, actual total: 27136, total with overprovisioning: 27136;
> requested cpu:4000,alloc_from_last_host?:true ,considerReservedCapacity?:
> true
> 2015-05-11 17:44:41,136 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-37:job-86) STATS: Can alloc MEM from host: 5, used:
> 8858370048, reserved: 4294967296, total: 33624601920; requested mem:
> 4294967296,alloc_from_last_host?:true ,considerReservedCapacity?: true
> 2015-05-11 17:44:41,136 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) The last host of this VM is UP and has enough
> capacity
> 2015-05-11 17:44:41,136 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) Now checking for suitable pools under zone: 1,
> pod: 1, cluster: 1
> 2015-05-11 17:44:41,136 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) Checking suitable pools for volume (Id, Type):
> (35,DATADISK)
> 2015-05-11 17:44:41,136 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) Volume is in READY state and has pool already
> allocated, checking if pool can be reused, poolId: 200
> 2015-05-11 17:44:41,137 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) Planner need not allocate a pool for this volume
> since its READY
> 2015-05-11 17:44:41,137 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) Checking suitable pools for volume (Id, Type):
> (48,ROOT)
> 2015-05-11 17:44:41,137 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) Volume is in READY state and has pool already
> allocated, checking if pool can be reused, poolId: 200
> 2015-05-11 17:44:41,137 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) Planner need not allocate a pool for this volume
> since its READY
> 2015-05-11 17:44:41,137 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) Trying to find a potenial host and associated
> storage pools from the suitable host/pool lists for this VM
> 2015-05-11 17:44:41,137 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) Checking if host: 5 can access any suitable
> storage pool for volume: ROOT
> 2015-05-11 17:44:41,138 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) Host: 5 can access pool: 200
> 2015-05-11 17:44:41,138 DEBUG [cloud.storage.StorageManagerImpl]
> (Job-Executor-37:job-86) Checking pool 200 for storage, totalSize:
> 154819100672, usedBytes: 98194948096, usedPct: 0.6342560295840756, disable
> threshold: 0.85
> 2015-05-11 17:44:41,139 DEBUG [cloud.storage.StorageManagerImpl]
> (Job-Executor-37:job-86) Checking pool: 200 for volume allocation
> [Vol[48|vm=41|ROOT]], maxSize : 309638201344, totalAllocatedSize :
> 370105075712, askingSize : 0, allocated disable threshold: 0.85
> 2015-05-11 17:44:41,139 DEBUG [cloud.storage.StorageManagerImpl]
> (Job-Executor-37:job-86) Insufficient un-allocated capacity on: 200 for
> volume allocation: [Vol[48|vm=41|ROOT]] since its allocated percentage:
> 1.1952823459945852 has crossed the allocated
> pool.storage.allocated.capacity.disablethreshold: 0.85, skipping this pool
> 2015-05-11 17:44:41,139 WARN  [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) insufficient capacity to allocate all volumes
> 2015-05-11 17:44:41,139 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) Could not find a potential host that has
> associated storage pools from the suitable host/pool lists for this VM
> 2015-05-11 17:44:41,139 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) Cannot choose the last host to deploy this VM
> 2015-05-11 17:44:41,139 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) Searching resources only under specified Cluster: 1
> 2015-05-11 17:44:41,141 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) Checking resources in Cluster: 1 under Pod: 1
> 2015-05-11 17:44:41,141 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) Calling HostAllocators to find suitable hosts
> 2015-05-11 17:44:41,141 DEBUG [allocator.impl.FirstFitAllocator]
> (Job-Executor-37:job-86 FirstFitRoutingAllocator) Looking for hosts in dc:
> 1  pod:1  cluster:1
> 2015-05-11 17:44:41,142 DEBUG [allocator.impl.FirstFitAllocator]
> (Job-Executor-37:job-86 FirstFitRoutingAllocator) FirstFitAllocator has 3
> hosts to check for allocation: [Host[-5-Routing], Host[-6-Routing],
> Host[-1-Routing]]
> 2015-05-11 17:44:41,144 DEBUG [allocator.impl.FirstFitAllocator]
> (Job-Executor-37:job-86 FirstFitRoutingAllocator) Found 3 hosts for
> allocation after prioritization: [Host[-5-Routing], Host[-6-Routing],
> Host[-1-Routing]]
> 2015-05-11 17:44:41,144 DEBUG [allocator.impl.FirstFitAllocator]
> (Job-Executor-37:job-86 FirstFitRoutingAllocator) Looking for
> speed=4000Mhz, Ram=4096
> 2015-05-11 17:44:41,144 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-37:job-86 FirstFitRoutingAllocator) Checking if host: 5 has
> enough capacity for requested CPU: 4000 and requested RAM: 4294967296 ,
> cpuOverprovisioningFactor: 1.0
> 2015-05-11 17:44:41,145 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-37:job-86 FirstFitRoutingAllocator) Hosts's actual total CPU:
> 27136 and CPU after applying overprovisioning: 27136
> 2015-05-11 17:44:41,145 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-37:job-86 FirstFitRoutingAllocator) Free CPU: 9636 ,
> Requested CPU: 4000
> 2015-05-11 17:44:41,145 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-37:job-86 FirstFitRoutingAllocator) Free RAM: 20471264576 ,
> Requested RAM: 4294967296
> 2015-05-11 17:44:41,145 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-37:job-86 FirstFitRoutingAllocator) Host has enough CPU and
> RAM available
> 2015-05-11 17:44:41,145 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-37:job-86 FirstFitRoutingAllocator) STATS: Can alloc CPU from
> host: 5, used: 13500, reserved: 4000, actual total: 27136, total with
> overprovisioning: 27136; requested cpu:4000,alloc_from_last_host?:false
> ,considerReservedCapacity?: true
> 2015-05-11 17:44:41,145 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-37:job-86 FirstFitRoutingAllocator) STATS: Can alloc MEM from
> host: 5, used: 8858370048, reserved: 4294967296, total: 33624601920;
> requested mem: 4294967296,alloc_from_last_host?:false
> ,considerReservedCapacity?: true
> 2015-05-11 17:44:41,145 DEBUG [allocator.impl.FirstFitAllocator]
> (Job-Executor-37:job-86 FirstFitRoutingAllocator) Found a suitable host,
> adding to list: 5
> 2015-05-11 17:44:41,146 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-37:job-86 FirstFitRoutingAllocator) Checking if host: 6 has
> enough capacity for requested CPU: 4000 and requested RAM: 4294967296 ,
> cpuOverprovisioningFactor: 1.0
> 2015-05-11 17:44:41,147 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-37:job-86 FirstFitRoutingAllocator) Hosts's actual total CPU:
> 23744 and CPU after applying overprovisioning: 23744
> 2015-05-11 17:44:41,147 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-37:job-86 FirstFitRoutingAllocator) Free CPU: 5244 ,
> Requested CPU: 4000
> 2015-05-11 17:44:41,147 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-37:job-86 FirstFitRoutingAllocator) Free RAM: 13385593216 ,
> Requested RAM: 4294967296
> 2015-05-11 17:44:41,147 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-37:job-86 FirstFitRoutingAllocator) Host has enough CPU and
> RAM available
> 2015-05-11 17:44:41,147 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-37:job-86 FirstFitRoutingAllocator) STATS: Can alloc CPU from
> host: 6, used: 18500, reserved: 0, actual total: 23744, total with
> overprovisioning: 23744; requested cpu:4000,alloc_from_last_host?:false
> ,considerReservedCapacity?: true
> 2015-05-11 17:44:41,147 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-37:job-86 FirstFitRoutingAllocator) STATS: Can alloc MEM from
> host: 6, used: 19461570560, reserved: 0, total: 32847163776; requested mem:
> 4294967296,alloc_from_last_host?:false ,considerReservedCapacity?: true
> 2015-05-11 17:44:41,147 DEBUG [allocator.impl.FirstFitAllocator]
> (Job-Executor-37:job-86 FirstFitRoutingAllocator) Found a suitable host,
> adding to list: 6
> 2015-05-11 17:44:41,148 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-37:job-86 FirstFitRoutingAllocator) Checking if host: 1 has
> enough capacity for requested CPU: 4000 and requested RAM: 4294967296 ,
> cpuOverprovisioningFactor: 1.0
> 2015-05-11 17:44:41,148 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-37:job-86 FirstFitRoutingAllocator) Hosts's actual total CPU:
> 27136 and CPU after applying overprovisioning: 27136
> 2015-05-11 17:44:41,148 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-37:job-86 FirstFitRoutingAllocator) Free CPU: 6636 ,
> Requested CPU: 4000
> 2015-05-11 17:44:41,149 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-37:job-86 FirstFitRoutingAllocator) Free RAM: 10298524992 ,
> Requested RAM: 4294967296
> 2015-05-11 17:44:41,149 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-37:job-86 FirstFitRoutingAllocator) Host has enough CPU and
> RAM available
> 2015-05-11 17:44:41,149 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-37:job-86 FirstFitRoutingAllocator) STATS: Can alloc CPU from
> host: 1, used: 20500, reserved: 0, actual total: 27136, total with
> overprovisioning: 27136; requested cpu:4000,alloc_from_last_host?:false
> ,considerReservedCapacity?: true
> 2015-05-11 17:44:41,149 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-37:job-86 FirstFitRoutingAllocator) STATS: Can alloc MEM from
> host: 1, used: 22548578304, reserved: 0, total: 32847103296; requested mem:
> 4294967296,alloc_from_last_host?:false ,considerReservedCapacity?: true
> 2015-05-11 17:44:41,149 DEBUG [allocator.impl.FirstFitAllocator]
> (Job-Executor-37:job-86 FirstFitRoutingAllocator) Found a suitable host,
> adding to list: 1
> 2015-05-11 17:44:41,149 DEBUG [allocator.impl.FirstFitAllocator]
> (Job-Executor-37:job-86 FirstFitRoutingAllocator) Host Allocator returning
> 3 suitable hosts
> 2015-05-11 17:44:41,149 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) Checking suitable pools for volume (Id, Type):
> (35,DATADISK)
> 2015-05-11 17:44:41,149 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) Volume is in READY state and has pool already
> allocated, checking if pool can be reused, poolId: 200
> 2015-05-11 17:44:41,150 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) Planner need not allocate a pool for this volume
> since its READY
> 2015-05-11 17:44:41,150 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) Checking suitable pools for volume (Id, Type):
> (48,ROOT)
> 2015-05-11 17:44:41,150 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) Volume is in READY state and has pool already
> allocated, checking if pool can be reused, poolId: 200
> 2015-05-11 17:44:41,150 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) Planner need not allocate a pool for this volume
> since its READY
> 2015-05-11 17:44:41,150 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) Trying to find a potenial host and associated
> storage pools from the suitable host/pool lists for this VM
> 2015-05-11 17:44:41,150 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) Checking if host: 5 can access any suitable
> storage pool for volume: ROOT
> 2015-05-11 17:44:41,151 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) Host: 5 can access pool: 200
> 2015-05-11 17:44:41,151 DEBUG [cloud.storage.StorageManagerImpl]
> (Job-Executor-37:job-86) Checking pool 200 for storage, totalSize:
> 154819100672, usedBytes: 98194948096, usedPct: 0.6342560295840756, disable
> threshold: 0.85
> 2015-05-11 17:44:41,152 DEBUG [cloud.storage.StorageManagerImpl]
> (Job-Executor-37:job-86) Checking pool: 200 for volume allocation
> [Vol[48|vm=41|ROOT]], maxSize : 309638201344, totalAllocatedSize :
> 370105075712, askingSize : 0, allocated disable threshold: 0.85
> 2015-05-11 17:44:41,152 DEBUG [cloud.storage.StorageManagerImpl]
> (Job-Executor-37:job-86) Insufficient un-allocated capacity on: 200 for
> volume allocation: [Vol[48|vm=41|ROOT]] since its allocated percentage:
> 1.1952823459945852 has crossed the allocated
> pool.storage.allocated.capacity.disablethreshold: 0.85, skipping this pool
> 2015-05-11 17:44:41,152 WARN  [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) insufficient capacity to allocate all volumes
> 2015-05-11 17:44:41,152 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) Checking if host: 6 can access any suitable
> storage pool for volume: ROOT
> 2015-05-11 17:44:41,152 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) Host: 6 can access pool: 200
> 2015-05-11 17:44:41,152 DEBUG [cloud.storage.StorageManagerImpl]
> (Job-Executor-37:job-86) Checking pool 200 for storage, totalSize:
> 154819100672, usedBytes: 98194948096, usedPct: 0.6342560295840756, disable
> threshold: 0.85
> 2015-05-11 17:44:41,154 DEBUG [cloud.storage.StorageManagerImpl]
> (Job-Executor-37:job-86) Checking pool: 200 for volume allocation
> [Vol[48|vm=41|ROOT]], maxSize : 309638201344, totalAllocatedSize :
> 370105075712, askingSize : 0, allocated disable threshold: 0.85
> 2015-05-11 17:44:41,154 DEBUG [cloud.storage.StorageManagerImpl]
> (Job-Executor-37:job-86) Insufficient un-allocated capacity on: 200 for
> volume allocation: [Vol[48|vm=41|ROOT]] since its allocated percentage:
> 1.1952823459945852 has crossed the allocated
> pool.storage.allocated.capacity.disablethreshold: 0.85, skipping this pool
> 2015-05-11 17:44:41,154 WARN  [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) insufficient capacity to allocate all volumes
> 2015-05-11 17:44:41,154 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) Checking if host: 1 can access any suitable
> storage pool for volume: ROOT
> 2015-05-11 17:44:41,154 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) Host: 1 can access pool: 200
> 2015-05-11 17:44:41,154 DEBUG [cloud.storage.StorageManagerImpl]
> (Job-Executor-37:job-86) Checking pool 200 for storage, totalSize:
> 154819100672, usedBytes: 98194948096, usedPct: 0.6342560295840756, disable
> threshold: 0.85
> 2015-05-11 17:44:41,155 DEBUG [cloud.storage.StorageManagerImpl]
> (Job-Executor-37:job-86) Checking pool: 200 for volume allocation
> [Vol[48|vm=41|ROOT]], maxSize : 309638201344, totalAllocatedSize :
> 370105075712, askingSize : 0, allocated disable threshold: 0.85
> 2015-05-11 17:44:41,155 DEBUG [cloud.storage.StorageManagerImpl]
> (Job-Executor-37:job-86) Insufficient un-allocated capacity on: 200 for
> volume allocation: [Vol[48|vm=41|ROOT]] since its allocated percentage:
> 1.1952823459945852 has crossed the allocated
> pool.storage.allocated.capacity.disablethreshold: 0.85, skipping this pool
> 2015-05-11 17:44:41,155 WARN  [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) insufficient capacity to allocate all volumes
> 2015-05-11 17:44:41,155 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) Could not find a potential host that has
> associated storage pools from the suitable host/pool lists for this VM
> 2015-05-11 17:44:41,156 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) Could not find suitable Deployment Destination for
> this VM under any clusters, returning.
> 2015-05-11 17:44:41,156 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) DeploymentPlanner allocation algorithm: random
> 2015-05-11 17:44:41,156 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) Trying to allocate a host and storage pools from
> dc:1, pod:1,cluster:null, requested cpu: 4000, requested ram: 4294967296
> 2015-05-11 17:44:41,156 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) Is ROOT volume READY (pool already allocated)?: No
> 2015-05-11 17:44:41,156 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) This VM has last host_id specified, trying to
> choose the same host: 5
> 2015-05-11 17:44:41,156 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) The last host of this VM is in avoid set
> 2015-05-11 17:44:41,156 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) Cannot choose the last host to deploy this VM
> 2015-05-11 17:44:41,156 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) Searching resources only under specified Pod: 1
> 2015-05-11 17:44:41,157 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) Listing clusters in order of aggregate capacity,
> that have (atleast one host with) enough CPU and RAM capacity under this
> Pod: 1
> 2015-05-11 17:44:41,157 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) CPUOverprovisioningFactor considered: 1.0
> 2015-05-11 17:44:41,158 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) Removing from the clusterId list these clusters
> from avoid set: [1]
> 2015-05-11 17:44:41,158 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-37:job-86) No clusters found after removing disabled clusters
> and clusters in avoid list, returning.
> 2015-05-11 17:44:41,222 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-37:job-86) VM state transitted from :Starting to Stopped with
> event: OperationFailedvm's original host id: 5 new host id: null host id
> before state transition: null
> 2015-05-11 17:44:41,249 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-37:job-86) Complete async job-86, jobStatus: 2, resultCode:
> 530, result: Error Code: 533 Error text: Unable to create a deployment for
> VM[User|TestMachine]
>
>
>
> catalina.out的日志。一直报“insufficient capacity to allocate all volumes”
>
> WARN  [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-59) insufficient
> capacity to allocate all volumes
> WARN  [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-59) insufficient
> capacity to allocate all volumes
> WARN  [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-59) insufficient
> capacity to allocate all volumes
> WARN  [cloud.deploy.FirstFitPlanner] (Job-Executor-11:job-60) insufficient
> capacity to allocate all volumes
> WARN  [cloud.deploy.FirstFitPlanner] (Job-Executor-11:job-60) insufficient
> capacity to allocate all volumes
> WARN  [cloud.deploy.FirstFitPlanner] (Job-Executor-11:job-60) insufficient
> capacity to allocate all volumes
> WARN  [cloud.deploy.FirstFitPlanner] (Job-Executor-16:job-65) insufficient
> capacity to allocate all volumes
> WARN  [cloud.deploy.FirstFitPlanner] (Job-Executor-16:job-65) insufficient
> capacity to allocate all volumes
> WARN  [cloud.deploy.FirstFitPlanner] (Job-Executor-16:job-65) insufficient
> capacity to allocate all volumes
> WARN  [cloud.deploy.FirstFitPlanner] (Job-Executor-16:job-65) insufficient
> capacity to allocate all volumes
> WARN  [cloud.deploy.FirstFitPlanner] (Job-Executor-17:job-66) insufficient
> capacity to allocate all volumes
> WARN  [cloud.deploy.FirstFitPlanner] (Job-Executor-17:job-66) insufficient
> capacity to allocate all volumes
> WARN  [cloud.deploy.FirstFitPlanner] (Job-Executor-27:job-86) insufficient
> capacity to allocate all volumes
>
>
>

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