cloudstack-users-cn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peng Wei <pwpeng...@gmail.com>
Subject Re: Re: 答复: 为什么计算方案大一点的虚机无法启动啊
Date Thu, 02 May 2013 04:51:06 GMT
问题解决了,是我的问题,因为我的Service
Offering是自己通过接口创建的,主机标签的参数我传了个长度为0的字符串,这就出现了如各位兄弟所说的主机标签的问题,我看了源码,正常走的话是不可能出现
 Looking for hosts having tag specified on SvcOffering:  这样的日志的。

简单的办法是去数据库的Service_Offering表里看看HostTag字段是否为null,或者比对一下系统内置的Small
Instance记录的该字段和你自己的记录的该字段是否一样。

再次感谢
tanthalas
Qian Shaohua
伍乙生
张秉南

兄弟们太给力了,呵呵。



On Fri, Apr 26, 2013 at 5:40 PM, 张秉南 <zbnyoujian@gmail.com> wrote:

> 我尝试减少了cpu配置可以,为什么高配的cpu计划方案不行?
> cpu.overprovisioning.factor=1  是这个参数的原因吗?
>
>
> 2013/4/26 tanthalas <tanthalas510@hotmail.com>
>
> >
> > log研究的挺深入了,赞一个!
> > 这条日志的意思是判定CPU是否有超配。全局变量有对应的参数。
> >
> >
> > 2013-04-26
> > 刘宇超  Richard Liu
> >
> >
> >
> >
> > 发件人: Peng Wei
> > 发送时间: 2013-04-25  20:49:04
> > 收件人: users-cn
> > 抄送:
> > 主题: Re: 答复: 为什么计算方案大一点的虚机无法启动啊
> >
> > 恩。主机标签之前确实疏忽过,但后来换了好几个新的计算方案测试,难道这是CS
> > 3.0.2的bug?我看不像,因为我主频3G单核测试都成功过,对这条日志不是很理解:
> > 2013-04-23 20:17:50,742 DEBUG [cloud.deploy.FirstFitPlanner]
> > (Job-Executor-121:job-375) CPUOverprovisioningFactor considered: 1.0
> > 继续再试,呵呵。
> > 感谢  tanthalas 和 Qian Shaohua给了我很好的启发。
> > On Thu, Apr 25, 2013 at 2:10 PM, tanthalas <tanthalas510@hotmail.com>
> > wrote:
> > >
> > > KVM对xp的支持没有问题。
> > > 如@Qian Shaohua  说的,你新建的计算服务里,对于主机标签是否有设置?
> > > 看起来是想找带有这个标签的主机,但实际一个都没有。
> > > 但好像你的标签也是空的?如果显示是空的,是否以前做过设置又给删掉?
> > > 在进一步测试看看把。
> > >
> > > 2013-04-25
> > > 刘宇超  Richard Liu
> > >
> > >
> > >
> > >
> > > 发件人: Qian Shaohua
> > > 发送时间: 2013-04-25  12:46:35
> > > 收件人: users-cn@cloudstack.apache.org
> > > 抄送:
> > > 主题: 答复: 为什么计算方案大一点的虚机无法启动啊
> > >
> > > 服务目录上配置了主机标签?
> > > 2013-04-23 20:17:50,754 DEBUG [allocator.impl.FirstFitAllocator]
> > > (Job-Executor-121:job-375 FirstFitRoutingAllocator) Looking for hosts
> > > having
> > > tag specified on SvcOffering:
> > > 2013-04-23 20:17:50,756 DEBUG [allocator.impl.FirstFitAllocator]
> > > (Job-Executor-121:job-375 FirstFitRoutingAllocator) Hosts with tag ''
> > > are:[]
> > > -----邮件原件-----
> > > 发件人: Peng Wei [mailto:pwpengwei@gmail.com]
> > > 发送时间: 2013年4月24日 23:00
> > > 收件人: users-cn@cloudstack.apache.org
> > > 主题: Re: 为什么计算方案大一点的虚机无法启动啊
> > > 2013-04-23 20:17:50,122 DEBUG [cloud.vm.UserVmManagerImpl]
> > > (catalina-exec-2:null) Allocating in the DB for vm
> > > 2013-04-23 20:17:50,122 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> > > (catalina-exec-2:null) Allocating entries for VM: VM[User|i-2-673-VM]
> > > 2013-04-23 20:17:50,126 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> > > (catalina-exec-2:null) Allocating nics for VM[User|i-2-673-VM]
> > > 2013-04-23 20:17:50,135 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> > > (catalina-exec-2:null) Allocaing disks for VM[User|i-2-673-VM]
> > > 2013-04-23 20:17:50,141 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> > > (catalina-exec-2:null) Allocation completed for VM: VM[User|i-2-673-VM]
> > > 2013-04-23 20:17:50,142 DEBUG [cloud.vm.UserVmManagerImpl]
> > > (catalina-exec-2:null) Successfully allocated DB entry for
> > > VM[User|i-2-673-VM]
> > > 2013-04-23 20:17:50,519 DEBUG [cloud.async.AsyncJobManagerImpl]
> > > (catalina-exec-2:null) submit async job-375, details: AsyncJobVO
> {id:375,
> > > userId: 2, accountId: 2, sessionKey: null, instanceType:
> VirtualMachine,
> > > instanceId: 673, cmd: com.cloud.api.commands.DeployVMCmd,
> cmdOriginator:
> > > null, cmdInfo:
> > >
> > >
> >
> {"id":"673","response":"json","templateId":"ed9c5e9e-d433-4852-b876-9a6faad7
> > >
> > >
> >
> 0d2a","sessionkey":"HrhX+0818o0TJVwJ74waq2TdZsY\u003d","ctxUserId":"2","hype
> > >
> > >
> >
> rvisor":"KVM","serviceOfferingId":"f3b91fa7-bb14-41b5-b2a7-d620b0ae6562","na
> > >
> > >
> >
> me":"pengwei10","ctxAccountId":"2","ctxStartEventId":"2240","zoneId":"fa41de
> > > 34-956a-4d18-8e4d-69bf5de8285a","displayname":"pengwei10"},
> > > cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> > > processStatus: 0, resultCode: 0, result: null, initMsid:
> 255332415455510,
> > > completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> > > 2013-04-23 20:17:50,520 DEBUG [cloud.async.AsyncJobManagerImpl]
> > > (Job-Executor-121:job-375) Executing com.cloud.api.commands.DeployVMCmd
> > for
> > > job-375
> > > 2013-04-23 20:17:50,662 DEBUG [cloud.capacity.CapacityManagerImpl]
> > > (Job-Executor-121:job-375) VM state transitted from :Stopped to
> Starting
> > > with event: StartRequestedvm's original host id: null new host id: null
> > > host
> > > id before state transition: null
> > > 2013-04-23 20:17:50,662 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> > > (Job-Executor-121:job-375) Successfully transitioned to start state for
> > > VM[User|i-2-673-VM] reservation id =
> c91db620-653e-411e-945d-ea3677d246b4
> > > 2013-04-23 20:17:50,736 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> > > (Job-Executor-121:job-375) Trying to deploy VM, vm has dcId: 1 and
> podId:
> > > null
> > > 2013-04-23 20:17:50,736 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> > > (Job-Executor-121:job-375) Deploy avoids pods: null, clusters: null,
> > hosts:
> > > null
> > > 2013-04-23 20:17:50,739 DEBUG [cloud.deploy.FirstFitPlanner]
> > > (Job-Executor-121:job-375) DeploymentPlanner allocation algorithm:
> random
> > > 2013-04-23 20:17:50,739 DEBUG [cloud.deploy.FirstFitPlanner]
> > > (Job-Executor-121:job-375) Trying to allocate a host and storage pools
> > from
> > > dc:1, pod:null,cluster:null, requested cpu: 4000, requested ram:
> > 4194304000
> > > 2013-04-23 20:17:50,739 DEBUG [cloud.deploy.FirstFitPlanner]
> > > (Job-Executor-121:job-375) Is ROOT volume READY (pool already
> > allocated)?:
> > > No
> > > 2013-04-23 20:17:50,739 DEBUG [cloud.deploy.FirstFitPlanner]
> > > (Job-Executor-121:job-375) Searching all possible resources under this
> > > Zone: 1
> > > 2013-04-23 20:17:50,742 DEBUG [cloud.deploy.FirstFitPlanner]
> > > (Job-Executor-121:job-375) Listing clusters in order of aggregate
> > capacity,
> > > that have (atleast one host with) enough CPU and RAM capacity under
> this
> > > Zone: 1
> > > 2013-04-23 20:17:50,742 DEBUG [cloud.deploy.FirstFitPlanner]
> > > (Job-Executor-121:job-375) CPUOverprovisioningFactor considered: 1.0
> > > 2013-04-23 20:17:50,753 DEBUG [cloud.deploy.FirstFitPlanner]
> > > (Job-Executor-121:job-375) Checking resources in Cluster: 1 under Pod:
> 1
> > > 2013-04-23 20:17:50,753 DEBUG [cloud.deploy.FirstFitPlanner]
> > > (Job-Executor-121:job-375) Calling HostAllocators to find suitable
> hosts
> > > 2013-04-23 20:17:50,753 DEBUG [allocator.impl.FirstFitAllocator]
> > > (Job-Executor-121:job-375 FirstFitRoutingAllocator) Looking for hosts
> in
> > > dc: 1  pod:1  cluster:1
> > > 2013-04-23 20:17:50,754 DEBUG [allocator.impl.FirstFitAllocator]
> > > (Job-Executor-121:job-375 FirstFitRoutingAllocator) Looking for hosts
> > > having
> > > tag specified on SvcOffering:
> > > 2013-04-23 20:17:50,756 DEBUG [allocator.impl.FirstFitAllocator]
> > > (Job-Executor-121:job-375 FirstFitRoutingAllocator) Hosts with tag ''
> > > are:[]
> > > 2013-04-23 20:17:50,756 DEBUG [allocator.impl.FirstFitAllocator]
> > > (Job-Executor-121:job-375 FirstFitRoutingAllocator) FirstFitAllocator
> > has 0
> > > hosts to check for allocation: []
> > > 2013-04-23 20:17:50,757 DEBUG [allocator.impl.FirstFitAllocator]
> > > (Job-Executor-121:job-375 FirstFitRoutingAllocator) Found 0 hosts for
> > > allocation after prioritization: []
> > > 2013-04-23 20:17:50,758 DEBUG [allocator.impl.FirstFitAllocator]
> > > (Job-Executor-121:job-375 FirstFitRoutingAllocator) Looking for
> > > speed=4000Mhz, Ram=4000
> > > 2013-04-23 20:17:50,758 DEBUG [allocator.impl.FirstFitAllocator]
> > > (Job-Executor-121:job-375 FirstFitRoutingAllocator) Host Allocator
> > > returning
> > > 0 suitable hosts
> > > 2013-04-23 20:17:50,758 DEBUG [cloud.deploy.FirstFitPlanner]
> > > (Job-Executor-121:job-375) No suitable hosts found
> > > 2013-04-23 20:17:50,758 DEBUG [cloud.deploy.FirstFitPlanner]
> > > (Job-Executor-121:job-375) No suitable hosts found under this Cluster:
> 1
> > > 2013-04-23 20:17:50,758 DEBUG [cloud.deploy.FirstFitPlanner]
> > > (Job-Executor-121:job-375) Could not find suitable Deployment
> Destination
> > > for this VM under any clusters, returning.
> > > 2013-04-23 20:17:50,903 DEBUG [cloud.capacity.CapacityManagerImpl]
> > > (Job-Executor-121:job-375) VM state transitted from :Starting to
> Stopped
> > > with event: OperationFailedvm's original host id: null new host id:
> null
> > > host id before state transition: null
> > > 2013-04-23 20:17:51,046 DEBUG [cloud.capacity.CapacityManagerImpl]
> > > (Job-Executor-121:job-375) 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
> > > 2013-04-23 20:17:51,648 INFO  [api.commands.DeployVMCmd]
> > > (Job-Executor-121:job-375)
> > > com.cloud.exception.InsufficientServerCapacityException: Unable to
> > create a
> > > deployment for VM[User|i-2-673-VM]Scope=interface
> > com.cloud.dc.DataCenter;
> > > id=1
> > > 2013-04-23 20:17:51,648 WARN  [cloud.api.ApiDispatcher]
> > > (Job-Executor-121:job-375) class com.cloud.api.ServerApiException :
> > Unable
> > > to create a deployment for VM[User|i-2-673-VM]
> > > 感谢tanthalas ,这是较完整一些的日志,用同样的计算方案我是能创建
linux 虚机
> > > 的,很怀疑是否KVM对winxp的模板支持有问题。
> > > On Tue, Apr 23, 2013 at 10:36 PM, tanthalas <tanthalas510@hotmail.com
> > > >wrote:
> > > > 这些log无法判断问题,还要继续往上看
> > > >
> > > >
> > > > 2013-04-23
> > > > 刘宇超  Richard Liu
> > > >
> > > >
> > > >
> > > >
> > > > 发件人: Peng Wei
> > > > 发送时间: 2013-04-23  22:15:01
> > > > 收件人: users-cn
> > > > 抄送:
> > > > 主题: 为什么计算方案大一点的虚机无法启动啊
> > > >
> > > > 我在基本资源域里创建vm,双核,每核2G,4G内存不成功,日志报错为:
> > > > 2013-04-23 20:17:50,758 DEBUG [cloud.deploy.FirstFitPlanner]
> > > > (Job-Executor-121:job-375) No suitable hosts found
> > > > 2013-04-23 20:17:50,758 DEBUG [cloud.deploy.FirstFitPlanner]
> > > > (Job-Executor-121:job-375) No suitable hosts found under this
> Cluster:
> > > > 1
> > > > 2013-04-23 20:17:50,758 DEBUG [cloud.deploy.FirstFitPlanner]
> > > > (Job-Executor-121:job-375) Could not find suitable Deployment
> > > > Destination for this VM under any clusters, returning.
> > > > 2013-04-23 20:17:50,903 DEBUG [cloud.capacity.CapacityManagerImpl]
> > > > (Job-Executor-121:job-375) VM state transitted from :Starting to
> > > > Stopped with event: OperationFailedvm's original host id: null new
> > > > host id: null host id before state transition: null
> > > > 2013-04-23 20:17:51,046 DEBUG [cloud.capacity.CapacityManagerImpl]
> > > > (Job-Executor-121:job-375) 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
> > > > 2013-04-23 20:17:51,648 INFO  [api.commands.DeployVMCmd]
> > > > (Job-Executor-121:job-375)
> > > > com.cloud.exception.InsufficientServerCapacityException: Unable to
> > > > create a deployment for VM[User|i-2-673-VM]Scope=interface
> > > > com.cloud.dc.DataCenter;
> > > > id=1
> > > > 但是我创建 单核2G,内存4G的vm都是可以的,我的物理节点是12核,32G内存啊,问
> > > 题出在哪里啊,是不是有什么全局配置设置一下,求助各位。
> > > >
> > >
> >
>

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