You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users-cn@cloudstack.apache.org by 虚无缥缈 <83...@qq.com> on 2014/03/11 07:34:32 UTC
创建虚机失败，突然出现的！资源没有问题!
2014-03-11 14:31:43,608 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) No suitable storagePools found under this Cluster: 1
2014-03-11 14:31:43,609 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) Could not find suitable Deployment Destination for this VM under any clusters, returning.
2014-03-11 14:31:43,609 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) Searching all possible resources under this Zone: 1
2014-03-11 14:31:43,610 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) Listing clusters in order of aggregate capacity, that have (atleast one host with) enough CPU and RAM capacity under this Zone: 1
2014-03-11 14:31:43,611 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) Removing from the clusterId list these clusters from avoid set: [1]
2014-03-11 14:31:43,612 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) No clusters found after removing disabled clusters and clusters in avoid list, returning.
2014-03-11 14:31:43,614 DEBUG [cloud.vm.UserVmManagerImpl] (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) Destroying vm VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc] as it failed to create on Host with Id:null
2014-03-11 14:31:43,617 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) 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
2014-03-11 14:31:43,619 WARN [apache.cloudstack.alerts] (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) alertType:: 8 // dataCenterId:: 1 // podId:: null // clusterId:: null // message:: Failed to deploy Vm with Id: 406, on Host with Id: null
2014-03-11 14:31:43,687 INFO [user.vm.DeployVMCmd] (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]Scope=interface com.cloud.dc.DataCenter; id=1
2014-03-11 14:31:43,687 INFO [user.vm.DeployVMCmd] (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) Unable to create a deployment for VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]
com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]Scope=interface com.cloud.dc.DataCenter; id=1
at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:209)
at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:198)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3405)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:701)
2014-03-11 14:31:43,688 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) Complete async job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ], jobStatus: 2, resultCode: 530, result: Error Code: 533 Error text: Unable to create a deployment for VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]
2014-03-11 14:31:47,029 DEBUG [cloud.api.ApiServlet] (catalina-exec-4:null) ===START=== 172.16.200.98 -- GET command=queryAsyncJobResult&jobId=b2f6f9f2-4b90-4595-8261-865d246c008f&response=json&sessionkey=YoE%2BsxQvpWDO2D1MA4KzAt1bQYo%3D&_=1394519535676
2014-03-11 14:31:47,035 DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-4:null) Async job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ] completed
Re: 创建虚机失败，突然出现的！资源没有问题!
Posted by "linuxbqj@gmail.com" <li...@gmail.com>.
请把你的基本环境信息先说明下 cs的版本，xen还是kvm 几台设备，存储怎么配置的
做什么操作时出错的
2014-03-11 14:34 GMT+08:00 虚无缥缈 <83...@qq.com>:
> 2014-03-11 14:31:43,608 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) No suitable storagePools found under this Cluster: 1
> 2014-03-11 14:31:43,609 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) Could not find suitable Deployment Destination for this VM under any clusters, returning.
> 2014-03-11 14:31:43,609 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) Searching all possible resources under this Zone: 1
> 2014-03-11 14:31:43,610 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) Listing clusters in order of aggregate capacity, that have (atleast one host with) enough CPU and RAM capacity under this Zone: 1
> 2014-03-11 14:31:43,611 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) Removing from the clusterId list these clusters from avoid set: [1]
> 2014-03-11 14:31:43,612 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) No clusters found after removing disabled clusters and clusters in avoid list, returning.
> 2014-03-11 14:31:43,614 DEBUG [cloud.vm.UserVmManagerImpl] (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) Destroying vm VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc] as it failed to create on Host with Id:null
> 2014-03-11 14:31:43,617 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) 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
> 2014-03-11 14:31:43,619 WARN [apache.cloudstack.alerts] (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) alertType:: 8 // dataCenterId:: 1 // podId:: null // clusterId:: null // message:: Failed to deploy Vm with Id: 406, on Host with Id: null
> 2014-03-11 14:31:43,687 INFO [user.vm.DeployVMCmd] (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]Scope=interface com.cloud.dc.DataCenter; id=1
> 2014-03-11 14:31:43,687 INFO [user.vm.DeployVMCmd] (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) Unable to create a deployment for VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]
> com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]Scope=interface com.cloud.dc.DataCenter; id=1
> at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:209)
> at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:198)
> at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3405)
> at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
> at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
> at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:701)
> 2014-03-11 14:31:43,688 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) Complete async job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ], jobStatus: 2, resultCode: 530, result: Error Code: 533 Error text: Unable to create a deployment for VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]
> 2014-03-11 14:31:47,029 DEBUG [cloud.api.ApiServlet] (catalina-exec-4:null) ===START=== 172.16.200.98 -- GET command=queryAsyncJobResult&jobId=b2f6f9f2-4b90-4595-8261-865d246c008f&response=json&sessionkey=YoE%2BsxQvpWDO2D1MA4KzAt1bQYo%3D&_=1394519535676
> 2014-03-11 14:31:47,035 DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-4:null) Async job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ] completed
--
白清杰 (Born Bai)
北京开源愿景信息技术有限公司
Mail: linuxbqj@gmail.com
Re: 回复： 回复：创建虚机失败，突然出现的！资源没有问题!
Posted by Wei ZHOU <us...@gmail.com>.
我这儿多数用的是ubuntu 12.04
在 2014年3月11日 上午9:45，淡看浮华 <36...@qq.com>写道：
> 好吧，那我再分析分析。
> 另外问一下啊，你用什么系统部署的，centos6.4？
> 我现在ubuntu下的问题比较多，不稳定，我想重新在centos系统下搭建一个cloudstack4.2.0新版本的，
> 但我的网络不行，在线安装估计比较困难，请问有没有完整的安装依赖包，可以先下载下来，然后做成本地安装源的啊？
>
>
>
> ------------------ 原始邮件 ------------------
> 发件人: "虚无缥缈";<83...@qq.com>;
> 发送时间: 2014年3月11日(星期二) 下午4:38
> 收件人: "users-cn"<us...@cloudstack.apache.org>;
>
> 主题: 回复： 回复：创建虚机失败，突然出现的！资源没有问题!
>
>
>
> 我的是kvm+cloudstack4.2.0，我这是存储问题，日志一样没用，这个日志没有报错原因。
>
>
>
>
> ------------------ 原始邮件 ------------------
> 发件人: "淡看浮华";<36...@qq.com>;
> 发送时间: 2014年3月11日(星期二) 下午4:17
> 收件人: "users-cn"<us...@cloudstack.apache.org>;
>
> 主题: 回复： 回复：创建虚机失败，突然出现的！资源没有问题!
>
>
>
>
> （我是在一台机器上安装ubuntu12.0.4系统，然后部署cloudstack4.0.2，既做管理节点，又做计算节点。hypervisor是用的kvm.主存储和二级存储都是通过NFS方式提供。）
> 通过上次ISO制作了模板，然后通过这个ISO模板创建虚拟机实例，我第一次创建的时候是成功了，可销毁实例之后，再创建，就弹出下面的错误提示：
> Unable to create a deployment for VM[User|vm1]
>
> 管理节点日志中显示,管理程序类型和VM不匹配,找不到部署位置.
> 具体相关日志如下：
> Cluster: 1 has HyperVisorType that does not match the VM, skipping this
> cluster
> 2014-03-10 11:09:27,939 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-39:job-104) Could not find suitable Deployment Destination
> for this VM under any clusters, returning.
>
> 从你贴出的日志看，和你的日志是一样的，确定是存储资源不足导致的吗？会不会还有其他方面的问题，可是我的主存储、二级存储空间都足够大啊，如下：
>
> root@ubuntu1:/opt/cCloud/runsh# df -h
> Filesystem Size Used Avail Use% Mounted on
> /dev/sda2 2.8T 50G 2.6T 2% /
> udev 3.9G 4.0K 3.9G 1% /dev
> tmpfs 1.6G 308K 1.6G 1% /run
> none 5.0M 0 5.0M 0% /run/lock
> none 3.9G 0 3.9G 0% /run/shm
> cgroup 3.9G 0 3.9G 0% /sys/fs/cgroup
> 192.168.3.72:/export/secondary 2.8T 50G 2.6T 2% /mnt/secondary
> 192.168.3.72:/export/primary 2.8T 50G 2.6T 2% /mnt/primary
> 192.168.3.72:/export/primary 2.8T 50G 2.6T 2%
> /mnt/01341da1-e5b5-32e4-9a63-18ba1517cf3c
>
>
>
>
>
>
> ------------------ 原始邮件 ------------------
> 发件人: "虚无缥缈";<83...@qq.com>;
> 发送时间: 2014年3月11日(星期二) 下午4:02
> 收件人: "users-cn"<us...@cloudstack.apache.org>;
>
> 主题: 回复： 回复：创建虚机失败，突然出现的！资源没有问题!
>
>
>
> 找到原因了，存储用了80%了，pool.storage.allocated.capacity.disablethreshold 0.85
> ，pool.storage.capacity.disablethreshold 0.85 ，改成1了。
> 日志没有报错原因，已经贴了全部日志，再往上的日志没有错误。
>
>
>
>
> ------------------ 原始邮件 ------------------
> 发件人: "Wei ZHOU";<us...@gmail.com>;
> 发送时间: 2014年3月11日(星期二) 下午3:28
> 收件人: "users-cn"<us...@cloudstack.apache.org>;
>
> 主题: Re: 回复：创建虚机失败，突然出现的！资源没有问题!
>
>
>
> 你最好把你的环境，和错误日志，都说清楚，这样好分析。
> 如果是kvm，我谨慎怀疑是libvirt的一个bug，主存储已经mount了，但是不在virsh pool-list中。
>
>
> 2014-03-11 7:47 GMT+01:00 虚无缥缈 <83...@qq.com>:
>
> > 我有个两个主存储，发现其中一个问题，但是手动mount建立文件也没有问题。
> >
> >
> >
> >
> > ------------------ 原始邮件 ------------------
> > 发件人: "我自己的邮箱";<83...@qq.com>;
> > 发送时间: 2014年3月11日(星期二) 下午2:34
> > 收件人: "users-cn"<us...@cloudstack.apache.org>;
> >
> > 主题: 创建虚机失败，突然出现的！资源没有问题!
> >
> >
> >
> > 2014-03-11 14:31:43,608 DEBUG
> [cloud.deploy.DeploymentPlanningManagerImpl]
> > (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) No
> > suitable storagePools found under this Cluster: 1
> > 2014-03-11 14:31:43,609 DEBUG
> [cloud.deploy.DeploymentPlanningManagerImpl]
> > (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> Could
> > not find suitable Deployment Destination for this VM under any clusters,
> > returning.
> > 2014-03-11 14:31:43,609 DEBUG [cloud.deploy.FirstFitPlanner]
> > (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> > Searching all possible resources under this Zone: 1
> > 2014-03-11 14:31:43,610 DEBUG [cloud.deploy.FirstFitPlanner]
> > (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> > Listing clusters in order of aggregate capacity, that have (atleast one
> > host with) enough CPU and RAM capacity under this Zone: 1
> > 2014-03-11 14:31:43,611 DEBUG [cloud.deploy.FirstFitPlanner]
> > (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> > Removing from the clusterId list these clusters from avoid set: [1]
> > 2014-03-11 14:31:43,612 DEBUG [cloud.deploy.FirstFitPlanner]
> > (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) No
> > clusters found after removing disabled clusters and clusters in avoid
> list,
> > returning.
> > 2014-03-11 14:31:43,614 DEBUG [cloud.vm.UserVmManagerImpl]
> > (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> > Destroying vm VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc] as it failed
> to
> > create on Host with Id:null
> > 2014-03-11 14:31:43,617 DEBUG [cloud.capacity.CapacityManagerImpl]
> > (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) 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
> > 2014-03-11 14:31:43,619 WARN [apache.cloudstack.alerts]
> > (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> > alertType:: 8 // dataCenterId:: 1 // podId:: null // clusterId:: null //
> > message:: Failed to deploy Vm with Id: 406, on Host with Id: null
> > 2014-03-11 14:31:43,687 INFO [user.vm.DeployVMCmd]
> > (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> > com.cloud.exception.InsufficientServerCapacityException: Unable to
> create a
> > deployment for
> VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]Scope=interface
> > com.cloud.dc.DataCenter; id=1
> > 2014-03-11 14:31:43,687 INFO [user.vm.DeployVMCmd]
> > (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> > Unable to create a deployment for
> > VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]
> > com.cloud.exception.InsufficientServerCapacityException: Unable to create
> > a deployment for
> > VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]Scope=interface
> > com.cloud.dc.DataCenter; id=1
> > at
> >
> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:209)
> > at
> >
> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:198)
> > at
> >
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3405)
> > at
> >
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
> > at
> >
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
> > at
> >
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> > at
> >
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
> > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> > at
> > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> > at
> > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> > at
> > java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> > at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> > at
> >
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> > at
> >
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> > at java.lang.Thread.run(Thread.java:701)
> > 2014-03-11 14:31:43,688 DEBUG [cloud.async.AsyncJobManagerImpl]
> > (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> > Complete async job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ],
> > jobStatus: 2, resultCode: 530, result: Error Code: 533 Error text: Unable
> > to create a deployment for VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]
> > 2014-03-11 14:31:47,029 DEBUG [cloud.api.ApiServlet]
> > (catalina-exec-4:null) ===START=== 172.16.200.98 -- GET
> >
> command=queryAsyncJobResult&jobId=b2f6f9f2-4b90-4595-8261-865d246c008f&response=json&sessionkey=YoE%2BsxQvpWDO2D1MA4KzAt1bQYo%3D&_=1394519535676
> > 2014-03-11 14:31:47,035 DEBUG [cloud.async.AsyncJobManagerImpl]
> > (catalina-exec-4:null) Async job-1884 = [
> > b2f6f9f2-4b90-4595-8261-865d246c008f ] completed
> >
>
回复： 回复：创建虚机失败，突然出现的！资源没有问题!
Posted by 虚无缥缈 <83...@qq.com>.
我是centos6.4 64 ，建本地源没有问题，社区共享里边有文档。
------------------ 原始邮件 ------------------
发件人: "淡看浮华";<36...@qq.com>;
发送时间: 2014年3月11日(星期二) 下午4:45
收件人: "users-cn"<us...@cloudstack.apache.org>;
主题: 回复： 回复：创建虚机失败，突然出现的！资源没有问题!
好吧，那我再分析分析。
另外问一下啊，你用什么系统部署的，centos6.4？
我现在ubuntu下的问题比较多，不稳定，我想重新在centos系统下搭建一个cloudstack4.2.0新版本的，
但我的网络不行，在线安装估计比较困难，请问有没有完整的安装依赖包，可以先下载下来，然后做成本地安装源的啊？
------------------ 原始邮件 ------------------
发件人: "虚无缥缈";<83...@qq.com>;
发送时间: 2014年3月11日(星期二) 下午4:38
收件人: "users-cn"<us...@cloudstack.apache.org>;
主题: 回复： 回复：创建虚机失败，突然出现的！资源没有问题!
我的是kvm+cloudstack4.2.0，我这是存储问题，日志一样没用，这个日志没有报错原因。
------------------ 原始邮件 ------------------
发件人: "淡看浮华";<36...@qq.com>;
发送时间: 2014年3月11日(星期二) 下午4:17
收件人: "users-cn"<us...@cloudstack.apache.org>;
主题: 回复： 回复：创建虚机失败，突然出现的！资源没有问题!
（我是在一台机器上安装ubuntu12.0.4系统，然后部署cloudstack4.0.2，既做管理节点，又做计算节点。hypervisor是用的kvm.主存储和二级存储都是通过NFS方式提供。）
通过上次ISO制作了模板，然后通过这个ISO模板创建虚拟机实例，我第一次创建的时候是成功了，可销毁实例之后，再创建，就弹出下面的错误提示：
Unable to create a deployment for VM[User|vm1]
管理节点日志中显示,管理程序类型和VM不匹配,找不到部署位置.
具体相关日志如下：
Cluster: 1 has HyperVisorType that does not match the VM, skipping this cluster
2014-03-10 11:09:27,939 DEBUG [cloud.deploy.FirstFitPlanner]
(Job-Executor-39:job-104) Could not find suitable Deployment Destination for this VM under any clusters, returning.
从你贴出的日志看，和你的日志是一样的，确定是存储资源不足导致的吗？会不会还有其他方面的问题，可是我的主存储、二级存储空间都足够大啊，如下：
root@ubuntu1:/opt/cCloud/runsh# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda2 2.8T 50G 2.6T 2% /
udev 3.9G 4.0K 3.9G 1% /dev
tmpfs 1.6G 308K 1.6G 1% /run
none 5.0M 0 5.0M 0% /run/lock
none 3.9G 0 3.9G 0% /run/shm
cgroup 3.9G 0 3.9G 0% /sys/fs/cgroup
192.168.3.72:/export/secondary 2.8T 50G 2.6T 2% /mnt/secondary
192.168.3.72:/export/primary 2.8T 50G 2.6T 2% /mnt/primary
192.168.3.72:/export/primary 2.8T 50G 2.6T 2% /mnt/01341da1-e5b5-32e4-9a63-18ba1517cf3c
------------------ 原始邮件 ------------------
发件人: "虚无缥缈";<83...@qq.com>;
发送时间: 2014年3月11日(星期二) 下午4:02
收件人: "users-cn"<us...@cloudstack.apache.org>;
主题: 回复： 回复：创建虚机失败，突然出现的！资源没有问题!
找到原因了，存储用了80%了，pool.storage.allocated.capacity.disablethreshold 0.85 ，pool.storage.capacity.disablethreshold 0.85 ，改成1了。
日志没有报错原因，已经贴了全部日志，再往上的日志没有错误。
------------------ 原始邮件 ------------------
发件人: "Wei ZHOU";<us...@gmail.com>;
发送时间: 2014年3月11日(星期二) 下午3:28
收件人: "users-cn"<us...@cloudstack.apache.org>;
主题: Re: 回复：创建虚机失败，突然出现的！资源没有问题!
你最好把你的环境，和错误日志，都说清楚，这样好分析。
如果是kvm，我谨慎怀疑是libvirt的一个bug，主存储已经mount了，但是不在virsh pool-list中。
2014-03-11 7:47 GMT+01:00 虚无缥缈 <83...@qq.com>:
> 我有个两个主存储，发现其中一个问题，但是手动mount建立文件也没有问题。
>
>
>
>
> ------------------ 原始邮件 ------------------
> 发件人: "我自己的邮箱";<83...@qq.com>;
> 发送时间: 2014年3月11日(星期二) 下午2:34
> 收件人: "users-cn"<us...@cloudstack.apache.org>;
>
> 主题: 创建虚机失败，突然出现的！资源没有问题!
>
>
>
> 2014-03-11 14:31:43,608 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) No
> suitable storagePools found under this Cluster: 1
> 2014-03-11 14:31:43,609 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) Could
> not find suitable Deployment Destination for this VM under any clusters,
> returning.
> 2014-03-11 14:31:43,609 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> Searching all possible resources under this Zone: 1
> 2014-03-11 14:31:43,610 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> Listing clusters in order of aggregate capacity, that have (atleast one
> host with) enough CPU and RAM capacity under this Zone: 1
> 2014-03-11 14:31:43,611 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> Removing from the clusterId list these clusters from avoid set: [1]
> 2014-03-11 14:31:43,612 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) No
> clusters found after removing disabled clusters and clusters in avoid list,
> returning.
> 2014-03-11 14:31:43,614 DEBUG [cloud.vm.UserVmManagerImpl]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> Destroying vm VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc] as it failed to
> create on Host with Id:null
> 2014-03-11 14:31:43,617 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) 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
> 2014-03-11 14:31:43,619 WARN [apache.cloudstack.alerts]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> alertType:: 8 // dataCenterId:: 1 // podId:: null // clusterId:: null //
> message:: Failed to deploy Vm with Id: 406, on Host with Id: null
> 2014-03-11 14:31:43,687 INFO [user.vm.DeployVMCmd]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> com.cloud.exception.InsufficientServerCapacityException: Unable to create a
> deployment for VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]Scope=interface
> com.cloud.dc.DataCenter; id=1
> 2014-03-11 14:31:43,687 INFO [user.vm.DeployVMCmd]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> Unable to create a deployment for
> VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]
> com.cloud.exception.InsufficientServerCapacityException: Unable to create
> a deployment for
> VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]Scope=interface
> com.cloud.dc.DataCenter; id=1
> at
> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:209)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:198)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3405)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at
> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:701)
> 2014-03-11 14:31:43,688 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> Complete async job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ],
> jobStatus: 2, resultCode: 530, result: Error Code: 533 Error text: Unable
> to create a deployment for VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]
> 2014-03-11 14:31:47,029 DEBUG [cloud.api.ApiServlet]
> (catalina-exec-4:null) ===START=== 172.16.200.98 -- GET
> command=queryAsyncJobResult&jobId=b2f6f9f2-4b90-4595-8261-865d246c008f&response=json&sessionkey=YoE%2BsxQvpWDO2D1MA4KzAt1bQYo%3D&_=1394519535676
> 2014-03-11 14:31:47,035 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-4:null) Async job-1884 = [
> b2f6f9f2-4b90-4595-8261-865d246c008f ] completed
>
回复： 回复：创建虚机失败，突然出现的！资源没有问题!
Posted by 淡看浮华 <36...@qq.com>.
好吧，那我再分析分析。
另外问一下啊，你用什么系统部署的，centos6.4？
我现在ubuntu下的问题比较多，不稳定，我想重新在centos系统下搭建一个cloudstack4.2.0新版本的，
但我的网络不行，在线安装估计比较困难，请问有没有完整的安装依赖包，可以先下载下来，然后做成本地安装源的啊？
------------------ 原始邮件 ------------------
发件人: "虚无缥缈";<83...@qq.com>;
发送时间: 2014年3月11日(星期二) 下午4:38
收件人: "users-cn"<us...@cloudstack.apache.org>;
主题: 回复： 回复：创建虚机失败，突然出现的！资源没有问题!
我的是kvm+cloudstack4.2.0，我这是存储问题，日志一样没用，这个日志没有报错原因。
------------------ 原始邮件 ------------------
发件人: "淡看浮华";<36...@qq.com>;
发送时间: 2014年3月11日(星期二) 下午4:17
收件人: "users-cn"<us...@cloudstack.apache.org>;
主题: 回复： 回复：创建虚机失败，突然出现的！资源没有问题!
（我是在一台机器上安装ubuntu12.0.4系统，然后部署cloudstack4.0.2，既做管理节点，又做计算节点。hypervisor是用的kvm.主存储和二级存储都是通过NFS方式提供。）
通过上次ISO制作了模板，然后通过这个ISO模板创建虚拟机实例，我第一次创建的时候是成功了，可销毁实例之后，再创建，就弹出下面的错误提示：
Unable to create a deployment for VM[User|vm1]
管理节点日志中显示,管理程序类型和VM不匹配,找不到部署位置.
具体相关日志如下：
Cluster: 1 has HyperVisorType that does not match the VM, skipping this cluster
2014-03-10 11:09:27,939 DEBUG [cloud.deploy.FirstFitPlanner]
(Job-Executor-39:job-104) Could not find suitable Deployment Destination for this VM under any clusters, returning.
从你贴出的日志看，和你的日志是一样的，确定是存储资源不足导致的吗？会不会还有其他方面的问题，可是我的主存储、二级存储空间都足够大啊，如下：
root@ubuntu1:/opt/cCloud/runsh# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda2 2.8T 50G 2.6T 2% /
udev 3.9G 4.0K 3.9G 1% /dev
tmpfs 1.6G 308K 1.6G 1% /run
none 5.0M 0 5.0M 0% /run/lock
none 3.9G 0 3.9G 0% /run/shm
cgroup 3.9G 0 3.9G 0% /sys/fs/cgroup
192.168.3.72:/export/secondary 2.8T 50G 2.6T 2% /mnt/secondary
192.168.3.72:/export/primary 2.8T 50G 2.6T 2% /mnt/primary
192.168.3.72:/export/primary 2.8T 50G 2.6T 2% /mnt/01341da1-e5b5-32e4-9a63-18ba1517cf3c
------------------ 原始邮件 ------------------
发件人: "虚无缥缈";<83...@qq.com>;
发送时间: 2014年3月11日(星期二) 下午4:02
收件人: "users-cn"<us...@cloudstack.apache.org>;
主题: 回复： 回复：创建虚机失败，突然出现的！资源没有问题!
找到原因了，存储用了80%了，pool.storage.allocated.capacity.disablethreshold 0.85 ，pool.storage.capacity.disablethreshold 0.85 ，改成1了。
日志没有报错原因，已经贴了全部日志，再往上的日志没有错误。
------------------ 原始邮件 ------------------
发件人: "Wei ZHOU";<us...@gmail.com>;
发送时间: 2014年3月11日(星期二) 下午3:28
收件人: "users-cn"<us...@cloudstack.apache.org>;
主题: Re: 回复：创建虚机失败，突然出现的！资源没有问题!
你最好把你的环境，和错误日志，都说清楚，这样好分析。
如果是kvm，我谨慎怀疑是libvirt的一个bug，主存储已经mount了，但是不在virsh pool-list中。
2014-03-11 7:47 GMT+01:00 虚无缥缈 <83...@qq.com>:
> 我有个两个主存储，发现其中一个问题，但是手动mount建立文件也没有问题。
>
>
>
>
> ------------------ 原始邮件 ------------------
> 发件人: "我自己的邮箱";<83...@qq.com>;
> 发送时间: 2014年3月11日(星期二) 下午2:34
> 收件人: "users-cn"<us...@cloudstack.apache.org>;
>
> 主题: 创建虚机失败，突然出现的！资源没有问题!
>
>
>
> 2014-03-11 14:31:43,608 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) No
> suitable storagePools found under this Cluster: 1
> 2014-03-11 14:31:43,609 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) Could
> not find suitable Deployment Destination for this VM under any clusters,
> returning.
> 2014-03-11 14:31:43,609 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> Searching all possible resources under this Zone: 1
> 2014-03-11 14:31:43,610 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> Listing clusters in order of aggregate capacity, that have (atleast one
> host with) enough CPU and RAM capacity under this Zone: 1
> 2014-03-11 14:31:43,611 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> Removing from the clusterId list these clusters from avoid set: [1]
> 2014-03-11 14:31:43,612 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) No
> clusters found after removing disabled clusters and clusters in avoid list,
> returning.
> 2014-03-11 14:31:43,614 DEBUG [cloud.vm.UserVmManagerImpl]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> Destroying vm VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc] as it failed to
> create on Host with Id:null
> 2014-03-11 14:31:43,617 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) 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
> 2014-03-11 14:31:43,619 WARN [apache.cloudstack.alerts]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> alertType:: 8 // dataCenterId:: 1 // podId:: null // clusterId:: null //
> message:: Failed to deploy Vm with Id: 406, on Host with Id: null
> 2014-03-11 14:31:43,687 INFO [user.vm.DeployVMCmd]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> com.cloud.exception.InsufficientServerCapacityException: Unable to create a
> deployment for VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]Scope=interface
> com.cloud.dc.DataCenter; id=1
> 2014-03-11 14:31:43,687 INFO [user.vm.DeployVMCmd]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> Unable to create a deployment for
> VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]
> com.cloud.exception.InsufficientServerCapacityException: Unable to create
> a deployment for
> VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]Scope=interface
> com.cloud.dc.DataCenter; id=1
> at
> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:209)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:198)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3405)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at
> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:701)
> 2014-03-11 14:31:43,688 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> Complete async job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ],
> jobStatus: 2, resultCode: 530, result: Error Code: 533 Error text: Unable
> to create a deployment for VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]
> 2014-03-11 14:31:47,029 DEBUG [cloud.api.ApiServlet]
> (catalina-exec-4:null) ===START=== 172.16.200.98 -- GET
> command=queryAsyncJobResult&jobId=b2f6f9f2-4b90-4595-8261-865d246c008f&response=json&sessionkey=YoE%2BsxQvpWDO2D1MA4KzAt1bQYo%3D&_=1394519535676
> 2014-03-11 14:31:47,035 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-4:null) Async job-1884 = [
> b2f6f9f2-4b90-4595-8261-865d246c008f ] completed
>
Re: 回复： 回复：创建虚机失败，突然出现的！资源没有问题!
Posted by Wei ZHOU <us...@gmail.com>.
自己看日志，肯定有说的。
2014-03-11 9:38 GMT+01:00 虚无缥缈 <83...@qq.com>:
> 我的是kvm+cloudstack4.2.0，我这是存储问题，日志一样没用，这个日志没有报错原因。
>
>
>
>
> ------------------ 原始邮件 ------------------
> 发件人: "淡看浮华";<36...@qq.com>;
> 发送时间: 2014年3月11日(星期二) 下午4:17
> 收件人: "users-cn"<us...@cloudstack.apache.org>;
>
> 主题: 回复： 回复：创建虚机失败，突然出现的！资源没有问题!
>
>
>
>
> （我是在一台机器上安装ubuntu12.0.4系统，然后部署cloudstack4.0.2，既做管理节点，又做计算节点。hypervisor是用的kvm.主存储和二级存储都是通过NFS方式提供。）
> 通过上次ISO制作了模板，然后通过这个ISO模板创建虚拟机实例，我第一次创建的时候是成功了，可销毁实例之后，再创建，就弹出下面的错误提示：
> Unable to create a deployment for VM[User|vm1]
>
> 管理节点日志中显示,管理程序类型和VM不匹配,找不到部署位置.
> 具体相关日志如下：
> Cluster: 1 has HyperVisorType that does not match the VM, skipping this
> cluster
> 2014-03-10 11:09:27,939 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-39:job-104) Could not find suitable Deployment Destination
> for this VM under any clusters, returning.
>
> 从你贴出的日志看，和你的日志是一样的，确定是存储资源不足导致的吗？会不会还有其他方面的问题，可是我的主存储、二级存储空间都足够大啊，如下：
>
> root@ubuntu1:/opt/cCloud/runsh# df -h
> Filesystem Size Used Avail Use% Mounted on
> /dev/sda2 2.8T 50G 2.6T 2% /
> udev 3.9G 4.0K 3.9G 1% /dev
> tmpfs 1.6G 308K 1.6G 1% /run
> none 5.0M 0 5.0M 0% /run/lock
> none 3.9G 0 3.9G 0% /run/shm
> cgroup 3.9G 0 3.9G 0% /sys/fs/cgroup
> 192.168.3.72:/export/secondary 2.8T 50G 2.6T 2% /mnt/secondary
> 192.168.3.72:/export/primary 2.8T 50G 2.6T 2% /mnt/primary
> 192.168.3.72:/export/primary 2.8T 50G 2.6T 2%
> /mnt/01341da1-e5b5-32e4-9a63-18ba1517cf3c
>
>
>
>
>
>
> ------------------ 原始邮件 ------------------
> 发件人: "虚无缥缈";<83...@qq.com>;
> 发送时间: 2014年3月11日(星期二) 下午4:02
> 收件人: "users-cn"<us...@cloudstack.apache.org>;
>
> 主题: 回复： 回复：创建虚机失败，突然出现的！资源没有问题!
>
>
>
> 找到原因了，存储用了80%了，pool.storage.allocated.capacity.disablethreshold 0.85
> ，pool.storage.capacity.disablethreshold 0.85 ，改成1了。
> 日志没有报错原因，已经贴了全部日志，再往上的日志没有错误。
>
>
>
>
> ------------------ 原始邮件 ------------------
> 发件人: "Wei ZHOU";<us...@gmail.com>;
> 发送时间: 2014年3月11日(星期二) 下午3:28
> 收件人: "users-cn"<us...@cloudstack.apache.org>;
>
> 主题: Re: 回复：创建虚机失败，突然出现的！资源没有问题!
>
>
>
> 你最好把你的环境，和错误日志，都说清楚，这样好分析。
> 如果是kvm，我谨慎怀疑是libvirt的一个bug，主存储已经mount了，但是不在virsh pool-list中。
>
>
> 2014-03-11 7:47 GMT+01:00 虚无缥缈 <83...@qq.com>:
>
> > 我有个两个主存储，发现其中一个问题，但是手动mount建立文件也没有问题。
> >
> >
> >
> >
> > ------------------ 原始邮件 ------------------
> > 发件人: "我自己的邮箱";<83...@qq.com>;
> > 发送时间: 2014年3月11日(星期二) 下午2:34
> > 收件人: "users-cn"<us...@cloudstack.apache.org>;
> >
> > 主题: 创建虚机失败，突然出现的！资源没有问题!
> >
> >
> >
> > 2014-03-11 14:31:43,608 DEBUG
> [cloud.deploy.DeploymentPlanningManagerImpl]
> > (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) No
> > suitable storagePools found under this Cluster: 1
> > 2014-03-11 14:31:43,609 DEBUG
> [cloud.deploy.DeploymentPlanningManagerImpl]
> > (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> Could
> > not find suitable Deployment Destination for this VM under any clusters,
> > returning.
> > 2014-03-11 14:31:43,609 DEBUG [cloud.deploy.FirstFitPlanner]
> > (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> > Searching all possible resources under this Zone: 1
> > 2014-03-11 14:31:43,610 DEBUG [cloud.deploy.FirstFitPlanner]
> > (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> > Listing clusters in order of aggregate capacity, that have (atleast one
> > host with) enough CPU and RAM capacity under this Zone: 1
> > 2014-03-11 14:31:43,611 DEBUG [cloud.deploy.FirstFitPlanner]
> > (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> > Removing from the clusterId list these clusters from avoid set: [1]
> > 2014-03-11 14:31:43,612 DEBUG [cloud.deploy.FirstFitPlanner]
> > (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) No
> > clusters found after removing disabled clusters and clusters in avoid
> list,
> > returning.
> > 2014-03-11 14:31:43,614 DEBUG [cloud.vm.UserVmManagerImpl]
> > (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> > Destroying vm VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc] as it failed
> to
> > create on Host with Id:null
> > 2014-03-11 14:31:43,617 DEBUG [cloud.capacity.CapacityManagerImpl]
> > (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) 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
> > 2014-03-11 14:31:43,619 WARN [apache.cloudstack.alerts]
> > (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> > alertType:: 8 // dataCenterId:: 1 // podId:: null // clusterId:: null //
> > message:: Failed to deploy Vm with Id: 406, on Host with Id: null
> > 2014-03-11 14:31:43,687 INFO [user.vm.DeployVMCmd]
> > (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> > com.cloud.exception.InsufficientServerCapacityException: Unable to
> create a
> > deployment for
> VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]Scope=interface
> > com.cloud.dc.DataCenter; id=1
> > 2014-03-11 14:31:43,687 INFO [user.vm.DeployVMCmd]
> > (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> > Unable to create a deployment for
> > VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]
> > com.cloud.exception.InsufficientServerCapacityException: Unable to create
> > a deployment for
> > VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]Scope=interface
> > com.cloud.dc.DataCenter; id=1
> > at
> >
> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:209)
> > at
> >
> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:198)
> > at
> >
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3405)
> > at
> >
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
> > at
> >
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
> > at
> >
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> > at
> >
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
> > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> > at
> > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> > at
> > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> > at
> > java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> > at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> > at
> >
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> > at
> >
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> > at java.lang.Thread.run(Thread.java:701)
> > 2014-03-11 14:31:43,688 DEBUG [cloud.async.AsyncJobManagerImpl]
> > (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> > Complete async job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ],
> > jobStatus: 2, resultCode: 530, result: Error Code: 533 Error text: Unable
> > to create a deployment for VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]
> > 2014-03-11 14:31:47,029 DEBUG [cloud.api.ApiServlet]
> > (catalina-exec-4:null) ===START=== 172.16.200.98 -- GET
> >
> command=queryAsyncJobResult&jobId=b2f6f9f2-4b90-4595-8261-865d246c008f&response=json&sessionkey=YoE%2BsxQvpWDO2D1MA4KzAt1bQYo%3D&_=1394519535676
> > 2014-03-11 14:31:47,035 DEBUG [cloud.async.AsyncJobManagerImpl]
> > (catalina-exec-4:null) Async job-1884 = [
> > b2f6f9f2-4b90-4595-8261-865d246c008f ] completed
> >
>
回复： 回复：创建虚机失败，突然出现的！资源没有问题!
Posted by 虚无缥缈 <83...@qq.com>.
我的是kvm+cloudstack4.2.0，我这是存储问题，日志一样没用，这个日志没有报错原因。
------------------ 原始邮件 ------------------
发件人: "淡看浮华";<36...@qq.com>;
发送时间: 2014年3月11日(星期二) 下午4:17
收件人: "users-cn"<us...@cloudstack.apache.org>;
主题: 回复： 回复：创建虚机失败，突然出现的！资源没有问题!
（我是在一台机器上安装ubuntu12.0.4系统，然后部署cloudstack4.0.2，既做管理节点，又做计算节点。hypervisor是用的kvm.主存储和二级存储都是通过NFS方式提供。）
通过上次ISO制作了模板，然后通过这个ISO模板创建虚拟机实例，我第一次创建的时候是成功了，可销毁实例之后，再创建，就弹出下面的错误提示：
Unable to create a deployment for VM[User|vm1]
管理节点日志中显示,管理程序类型和VM不匹配,找不到部署位置.
具体相关日志如下：
Cluster: 1 has HyperVisorType that does not match the VM, skipping this cluster
2014-03-10 11:09:27,939 DEBUG [cloud.deploy.FirstFitPlanner]
(Job-Executor-39:job-104) Could not find suitable Deployment Destination for this VM under any clusters, returning.
从你贴出的日志看，和你的日志是一样的，确定是存储资源不足导致的吗？会不会还有其他方面的问题，可是我的主存储、二级存储空间都足够大啊，如下：
root@ubuntu1:/opt/cCloud/runsh# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda2 2.8T 50G 2.6T 2% /
udev 3.9G 4.0K 3.9G 1% /dev
tmpfs 1.6G 308K 1.6G 1% /run
none 5.0M 0 5.0M 0% /run/lock
none 3.9G 0 3.9G 0% /run/shm
cgroup 3.9G 0 3.9G 0% /sys/fs/cgroup
192.168.3.72:/export/secondary 2.8T 50G 2.6T 2% /mnt/secondary
192.168.3.72:/export/primary 2.8T 50G 2.6T 2% /mnt/primary
192.168.3.72:/export/primary 2.8T 50G 2.6T 2% /mnt/01341da1-e5b5-32e4-9a63-18ba1517cf3c
------------------ 原始邮件 ------------------
发件人: "虚无缥缈";<83...@qq.com>;
发送时间: 2014年3月11日(星期二) 下午4:02
收件人: "users-cn"<us...@cloudstack.apache.org>;
主题: 回复： 回复：创建虚机失败，突然出现的！资源没有问题!
找到原因了，存储用了80%了，pool.storage.allocated.capacity.disablethreshold 0.85 ，pool.storage.capacity.disablethreshold 0.85 ，改成1了。
日志没有报错原因，已经贴了全部日志，再往上的日志没有错误。
------------------ 原始邮件 ------------------
发件人: "Wei ZHOU";<us...@gmail.com>;
发送时间: 2014年3月11日(星期二) 下午3:28
收件人: "users-cn"<us...@cloudstack.apache.org>;
主题: Re: 回复：创建虚机失败，突然出现的！资源没有问题!
你最好把你的环境，和错误日志，都说清楚，这样好分析。
如果是kvm，我谨慎怀疑是libvirt的一个bug，主存储已经mount了，但是不在virsh pool-list中。
2014-03-11 7:47 GMT+01:00 虚无缥缈 <83...@qq.com>:
> 我有个两个主存储，发现其中一个问题，但是手动mount建立文件也没有问题。
>
>
>
>
> ------------------ 原始邮件 ------------------
> 发件人: "我自己的邮箱";<83...@qq.com>;
> 发送时间: 2014年3月11日(星期二) 下午2:34
> 收件人: "users-cn"<us...@cloudstack.apache.org>;
>
> 主题: 创建虚机失败，突然出现的！资源没有问题!
>
>
>
> 2014-03-11 14:31:43,608 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) No
> suitable storagePools found under this Cluster: 1
> 2014-03-11 14:31:43,609 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) Could
> not find suitable Deployment Destination for this VM under any clusters,
> returning.
> 2014-03-11 14:31:43,609 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> Searching all possible resources under this Zone: 1
> 2014-03-11 14:31:43,610 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> Listing clusters in order of aggregate capacity, that have (atleast one
> host with) enough CPU and RAM capacity under this Zone: 1
> 2014-03-11 14:31:43,611 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> Removing from the clusterId list these clusters from avoid set: [1]
> 2014-03-11 14:31:43,612 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) No
> clusters found after removing disabled clusters and clusters in avoid list,
> returning.
> 2014-03-11 14:31:43,614 DEBUG [cloud.vm.UserVmManagerImpl]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> Destroying vm VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc] as it failed to
> create on Host with Id:null
> 2014-03-11 14:31:43,617 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) 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
> 2014-03-11 14:31:43,619 WARN [apache.cloudstack.alerts]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> alertType:: 8 // dataCenterId:: 1 // podId:: null // clusterId:: null //
> message:: Failed to deploy Vm with Id: 406, on Host with Id: null
> 2014-03-11 14:31:43,687 INFO [user.vm.DeployVMCmd]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> com.cloud.exception.InsufficientServerCapacityException: Unable to create a
> deployment for VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]Scope=interface
> com.cloud.dc.DataCenter; id=1
> 2014-03-11 14:31:43,687 INFO [user.vm.DeployVMCmd]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> Unable to create a deployment for
> VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]
> com.cloud.exception.InsufficientServerCapacityException: Unable to create
> a deployment for
> VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]Scope=interface
> com.cloud.dc.DataCenter; id=1
> at
> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:209)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:198)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3405)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at
> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:701)
> 2014-03-11 14:31:43,688 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> Complete async job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ],
> jobStatus: 2, resultCode: 530, result: Error Code: 533 Error text: Unable
> to create a deployment for VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]
> 2014-03-11 14:31:47,029 DEBUG [cloud.api.ApiServlet]
> (catalina-exec-4:null) ===START=== 172.16.200.98 -- GET
> command=queryAsyncJobResult&jobId=b2f6f9f2-4b90-4595-8261-865d246c008f&response=json&sessionkey=YoE%2BsxQvpWDO2D1MA4KzAt1bQYo%3D&_=1394519535676
> 2014-03-11 14:31:47,035 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-4:null) Async job-1884 = [
> b2f6f9f2-4b90-4595-8261-865d246c008f ] completed
>
回复： 回复：创建虚机失败，突然出现的！资源没有问题!
Posted by 淡看浮华 <36...@qq.com>.
（我是在一台机器上安装ubuntu12.0.4系统，然后部署cloudstack4.0.2，既做管理节点，又做计算节点。hypervisor是用的kvm.主存储和二级存储都是通过NFS方式提供。）
通过上次ISO制作了模板，然后通过这个ISO模板创建虚拟机实例，我第一次创建的时候是成功了，可销毁实例之后，再创建，就弹出下面的错误提示：
Unable to create a deployment for VM[User|vm1]
管理节点日志中显示,管理程序类型和VM不匹配,找不到部署位置.
具体相关日志如下：
Cluster: 1 has HyperVisorType that does not match the VM, skipping this cluster
2014-03-10 11:09:27,939 DEBUG [cloud.deploy.FirstFitPlanner]
(Job-Executor-39:job-104) Could not find suitable Deployment Destination for this VM under any clusters, returning.
从你贴出的日志看，和你的日志是一样的，确定是存储资源不足导致的吗？会不会还有其他方面的问题，可是我的主存储、二级存储空间都足够大啊，如下：
root@ubuntu1:/opt/cCloud/runsh# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda2 2.8T 50G 2.6T 2% /
udev 3.9G 4.0K 3.9G 1% /dev
tmpfs 1.6G 308K 1.6G 1% /run
none 5.0M 0 5.0M 0% /run/lock
none 3.9G 0 3.9G 0% /run/shm
cgroup 3.9G 0 3.9G 0% /sys/fs/cgroup
192.168.3.72:/export/secondary 2.8T 50G 2.6T 2% /mnt/secondary
192.168.3.72:/export/primary 2.8T 50G 2.6T 2% /mnt/primary
192.168.3.72:/export/primary 2.8T 50G 2.6T 2% /mnt/01341da1-e5b5-32e4-9a63-18ba1517cf3c
------------------ 原始邮件 ------------------
发件人: "虚无缥缈";<83...@qq.com>;
发送时间: 2014年3月11日(星期二) 下午4:02
收件人: "users-cn"<us...@cloudstack.apache.org>;
主题: 回复： 回复：创建虚机失败，突然出现的！资源没有问题!
找到原因了，存储用了80%了，pool.storage.allocated.capacity.disablethreshold 0.85 ，pool.storage.capacity.disablethreshold 0.85 ，改成1了。
日志没有报错原因，已经贴了全部日志，再往上的日志没有错误。
------------------ 原始邮件 ------------------
发件人: "Wei ZHOU";<us...@gmail.com>;
发送时间: 2014年3月11日(星期二) 下午3:28
收件人: "users-cn"<us...@cloudstack.apache.org>;
主题: Re: 回复：创建虚机失败，突然出现的！资源没有问题!
你最好把你的环境，和错误日志，都说清楚，这样好分析。
如果是kvm，我谨慎怀疑是libvirt的一个bug，主存储已经mount了，但是不在virsh pool-list中。
2014-03-11 7:47 GMT+01:00 虚无缥缈 <83...@qq.com>:
> 我有个两个主存储，发现其中一个问题，但是手动mount建立文件也没有问题。
>
>
>
>
> ------------------ 原始邮件 ------------------
> 发件人: "我自己的邮箱";<83...@qq.com>;
> 发送时间: 2014年3月11日(星期二) 下午2:34
> 收件人: "users-cn"<us...@cloudstack.apache.org>;
>
> 主题: 创建虚机失败，突然出现的！资源没有问题!
>
>
>
> 2014-03-11 14:31:43,608 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) No
> suitable storagePools found under this Cluster: 1
> 2014-03-11 14:31:43,609 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) Could
> not find suitable Deployment Destination for this VM under any clusters,
> returning.
> 2014-03-11 14:31:43,609 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> Searching all possible resources under this Zone: 1
> 2014-03-11 14:31:43,610 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> Listing clusters in order of aggregate capacity, that have (atleast one
> host with) enough CPU and RAM capacity under this Zone: 1
> 2014-03-11 14:31:43,611 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> Removing from the clusterId list these clusters from avoid set: [1]
> 2014-03-11 14:31:43,612 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) No
> clusters found after removing disabled clusters and clusters in avoid list,
> returning.
> 2014-03-11 14:31:43,614 DEBUG [cloud.vm.UserVmManagerImpl]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> Destroying vm VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc] as it failed to
> create on Host with Id:null
> 2014-03-11 14:31:43,617 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) 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
> 2014-03-11 14:31:43,619 WARN [apache.cloudstack.alerts]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> alertType:: 8 // dataCenterId:: 1 // podId:: null // clusterId:: null //
> message:: Failed to deploy Vm with Id: 406, on Host with Id: null
> 2014-03-11 14:31:43,687 INFO [user.vm.DeployVMCmd]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> com.cloud.exception.InsufficientServerCapacityException: Unable to create a
> deployment for VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]Scope=interface
> com.cloud.dc.DataCenter; id=1
> 2014-03-11 14:31:43,687 INFO [user.vm.DeployVMCmd]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> Unable to create a deployment for
> VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]
> com.cloud.exception.InsufficientServerCapacityException: Unable to create
> a deployment for
> VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]Scope=interface
> com.cloud.dc.DataCenter; id=1
> at
> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:209)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:198)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3405)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at
> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:701)
> 2014-03-11 14:31:43,688 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> Complete async job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ],
> jobStatus: 2, resultCode: 530, result: Error Code: 533 Error text: Unable
> to create a deployment for VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]
> 2014-03-11 14:31:47,029 DEBUG [cloud.api.ApiServlet]
> (catalina-exec-4:null) ===START=== 172.16.200.98 -- GET
> command=queryAsyncJobResult&jobId=b2f6f9f2-4b90-4595-8261-865d246c008f&response=json&sessionkey=YoE%2BsxQvpWDO2D1MA4KzAt1bQYo%3D&_=1394519535676
> 2014-03-11 14:31:47,035 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-4:null) Async job-1884 = [
> b2f6f9f2-4b90-4595-8261-865d246c008f ] completed
>
回复： 回复：创建虚机失败，突然出现的！资源没有问题!
Posted by 虚无缥缈 <83...@qq.com>.
找到原因了，存储用了80%了，pool.storage.allocated.capacity.disablethreshold 0.85 ，pool.storage.capacity.disablethreshold 0.85 ，改成1了。
日志没有报错原因，已经贴了全部日志，再往上的日志没有错误。
------------------ 原始邮件 ------------------
发件人: "Wei ZHOU";<us...@gmail.com>;
发送时间: 2014年3月11日(星期二) 下午3:28
收件人: "users-cn"<us...@cloudstack.apache.org>;
主题: Re: 回复：创建虚机失败，突然出现的！资源没有问题!
你最好把你的环境，和错误日志，都说清楚，这样好分析。
如果是kvm，我谨慎怀疑是libvirt的一个bug，主存储已经mount了，但是不在virsh pool-list中。
2014-03-11 7:47 GMT+01:00 虚无缥缈 <83...@qq.com>:
> 我有个两个主存储，发现其中一个问题，但是手动mount建立文件也没有问题。
>
>
>
>
> ------------------ 原始邮件 ------------------
> 发件人: "我自己的邮箱";<83...@qq.com>;
> 发送时间: 2014年3月11日(星期二) 下午2:34
> 收件人: "users-cn"<us...@cloudstack.apache.org>;
>
> 主题: 创建虚机失败，突然出现的！资源没有问题!
>
>
>
> 2014-03-11 14:31:43,608 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) No
> suitable storagePools found under this Cluster: 1
> 2014-03-11 14:31:43,609 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) Could
> not find suitable Deployment Destination for this VM under any clusters,
> returning.
> 2014-03-11 14:31:43,609 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> Searching all possible resources under this Zone: 1
> 2014-03-11 14:31:43,610 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> Listing clusters in order of aggregate capacity, that have (atleast one
> host with) enough CPU and RAM capacity under this Zone: 1
> 2014-03-11 14:31:43,611 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> Removing from the clusterId list these clusters from avoid set: [1]
> 2014-03-11 14:31:43,612 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) No
> clusters found after removing disabled clusters and clusters in avoid list,
> returning.
> 2014-03-11 14:31:43,614 DEBUG [cloud.vm.UserVmManagerImpl]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> Destroying vm VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc] as it failed to
> create on Host with Id:null
> 2014-03-11 14:31:43,617 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) 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
> 2014-03-11 14:31:43,619 WARN [apache.cloudstack.alerts]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> alertType:: 8 // dataCenterId:: 1 // podId:: null // clusterId:: null //
> message:: Failed to deploy Vm with Id: 406, on Host with Id: null
> 2014-03-11 14:31:43,687 INFO [user.vm.DeployVMCmd]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> com.cloud.exception.InsufficientServerCapacityException: Unable to create a
> deployment for VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]Scope=interface
> com.cloud.dc.DataCenter; id=1
> 2014-03-11 14:31:43,687 INFO [user.vm.DeployVMCmd]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> Unable to create a deployment for
> VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]
> com.cloud.exception.InsufficientServerCapacityException: Unable to create
> a deployment for
> VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]Scope=interface
> com.cloud.dc.DataCenter; id=1
> at
> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:209)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:198)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3405)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at
> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:701)
> 2014-03-11 14:31:43,688 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> Complete async job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ],
> jobStatus: 2, resultCode: 530, result: Error Code: 533 Error text: Unable
> to create a deployment for VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]
> 2014-03-11 14:31:47,029 DEBUG [cloud.api.ApiServlet]
> (catalina-exec-4:null) ===START=== 172.16.200.98 -- GET
> command=queryAsyncJobResult&jobId=b2f6f9f2-4b90-4595-8261-865d246c008f&response=json&sessionkey=YoE%2BsxQvpWDO2D1MA4KzAt1bQYo%3D&_=1394519535676
> 2014-03-11 14:31:47,035 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-4:null) Async job-1884 = [
> b2f6f9f2-4b90-4595-8261-865d246c008f ] completed
>
Re: 回复：创建虚机失败，突然出现的！资源没有问题!
Posted by Wei ZHOU <us...@gmail.com>.
你最好把你的环境，和错误日志，都说清楚，这样好分析。
如果是kvm，我谨慎怀疑是libvirt的一个bug，主存储已经mount了，但是不在virsh pool-list中。
2014-03-11 7:47 GMT+01:00 虚无缥缈 <83...@qq.com>:
> 我有个两个主存储，发现其中一个问题，但是手动mount建立文件也没有问题。
>
>
>
>
> ------------------ 原始邮件 ------------------
> 发件人: "我自己的邮箱";<83...@qq.com>;
> 发送时间: 2014年3月11日(星期二) 下午2:34
> 收件人: "users-cn"<us...@cloudstack.apache.org>;
>
> 主题: 创建虚机失败，突然出现的！资源没有问题!
>
>
>
> 2014-03-11 14:31:43,608 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) No
> suitable storagePools found under this Cluster: 1
> 2014-03-11 14:31:43,609 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) Could
> not find suitable Deployment Destination for this VM under any clusters,
> returning.
> 2014-03-11 14:31:43,609 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> Searching all possible resources under this Zone: 1
> 2014-03-11 14:31:43,610 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> Listing clusters in order of aggregate capacity, that have (atleast one
> host with) enough CPU and RAM capacity under this Zone: 1
> 2014-03-11 14:31:43,611 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> Removing from the clusterId list these clusters from avoid set: [1]
> 2014-03-11 14:31:43,612 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) No
> clusters found after removing disabled clusters and clusters in avoid list,
> returning.
> 2014-03-11 14:31:43,614 DEBUG [cloud.vm.UserVmManagerImpl]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> Destroying vm VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc] as it failed to
> create on Host with Id:null
> 2014-03-11 14:31:43,617 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) 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
> 2014-03-11 14:31:43,619 WARN [apache.cloudstack.alerts]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> alertType:: 8 // dataCenterId:: 1 // podId:: null // clusterId:: null //
> message:: Failed to deploy Vm with Id: 406, on Host with Id: null
> 2014-03-11 14:31:43,687 INFO [user.vm.DeployVMCmd]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> com.cloud.exception.InsufficientServerCapacityException: Unable to create a
> deployment for VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]Scope=interface
> com.cloud.dc.DataCenter; id=1
> 2014-03-11 14:31:43,687 INFO [user.vm.DeployVMCmd]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> Unable to create a deployment for
> VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]
> com.cloud.exception.InsufficientServerCapacityException: Unable to create
> a deployment for
> VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]Scope=interface
> com.cloud.dc.DataCenter; id=1
> at
> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:209)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:198)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3405)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at
> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:701)
> 2014-03-11 14:31:43,688 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> Complete async job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ],
> jobStatus: 2, resultCode: 530, result: Error Code: 533 Error text: Unable
> to create a deployment for VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]
> 2014-03-11 14:31:47,029 DEBUG [cloud.api.ApiServlet]
> (catalina-exec-4:null) ===START=== 172.16.200.98 -- GET
> command=queryAsyncJobResult&jobId=b2f6f9f2-4b90-4595-8261-865d246c008f&response=json&sessionkey=YoE%2BsxQvpWDO2D1MA4KzAt1bQYo%3D&_=1394519535676
> 2014-03-11 14:31:47,035 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-4:null) Async job-1884 = [
> b2f6f9f2-4b90-4595-8261-865d246c008f ] completed
>
回复：创建虚机失败，突然出现的！资源没有问题!
Posted by 虚无缥缈 <83...@qq.com>.
我有个两个主存储，发现其中一个问题，但是手动mount建立文件也没有问题。
------------------ 原始邮件 ------------------
发件人: "我自己的邮箱";<83...@qq.com>;
发送时间: 2014年3月11日(星期二) 下午2:34
收件人: "users-cn"<us...@cloudstack.apache.org>;
主题: 创建虚机失败，突然出现的！资源没有问题!
2014-03-11 14:31:43,608 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) No suitable storagePools found under this Cluster: 1
2014-03-11 14:31:43,609 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) Could not find suitable Deployment Destination for this VM under any clusters, returning.
2014-03-11 14:31:43,609 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) Searching all possible resources under this Zone: 1
2014-03-11 14:31:43,610 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) Listing clusters in order of aggregate capacity, that have (atleast one host with) enough CPU and RAM capacity under this Zone: 1
2014-03-11 14:31:43,611 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) Removing from the clusterId list these clusters from avoid set: [1]
2014-03-11 14:31:43,612 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) No clusters found after removing disabled clusters and clusters in avoid list, returning.
2014-03-11 14:31:43,614 DEBUG [cloud.vm.UserVmManagerImpl] (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) Destroying vm VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc] as it failed to create on Host with Id:null
2014-03-11 14:31:43,617 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) 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
2014-03-11 14:31:43,619 WARN [apache.cloudstack.alerts] (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) alertType:: 8 // dataCenterId:: 1 // podId:: null // clusterId:: null // message:: Failed to deploy Vm with Id: 406, on Host with Id: null
2014-03-11 14:31:43,687 INFO [user.vm.DeployVMCmd] (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]Scope=interface com.cloud.dc.DataCenter; id=1
2014-03-11 14:31:43,687 INFO [user.vm.DeployVMCmd] (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) Unable to create a deployment for VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]
com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]Scope=interface com.cloud.dc.DataCenter; id=1
at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:209)
at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:198)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3405)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:701)
2014-03-11 14:31:43,688 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) Complete async job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ], jobStatus: 2, resultCode: 530, result: Error Code: 533 Error text: Unable to create a deployment for VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]
2014-03-11 14:31:47,029 DEBUG [cloud.api.ApiServlet] (catalina-exec-4:null) ===START=== 172.16.200.98 -- GET command=queryAsyncJobResult&jobId=b2f6f9f2-4b90-4595-8261-865d246c008f&response=json&sessionkey=YoE%2BsxQvpWDO2D1MA4KzAt1bQYo%3D&_=1394519535676
2014-03-11 14:31:47,035 DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-4:null) Async job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ] completed
Re: 创建虚机失败，突然出现的！资源没有问题!
Posted by Wei ZHOU <us...@gmail.com>.
kvm？
host状态是up吗？
再往前贴点日志
2014-03-11 7:34 GMT+01:00 虚无缥缈 <83...@qq.com>:
> 2014-03-11 14:31:43,608 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) No
> suitable storagePools found under this Cluster: 1
> 2014-03-11 14:31:43,609 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) Could
> not find suitable Deployment Destination for this VM under any clusters,
> returning.
> 2014-03-11 14:31:43,609 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> Searching all possible resources under this Zone: 1
> 2014-03-11 14:31:43,610 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> Listing clusters in order of aggregate capacity, that have (atleast one
> host with) enough CPU and RAM capacity under this Zone: 1
> 2014-03-11 14:31:43,611 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> Removing from the clusterId list these clusters from avoid set: [1]
> 2014-03-11 14:31:43,612 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) No
> clusters found after removing disabled clusters and clusters in avoid list,
> returning.
> 2014-03-11 14:31:43,614 DEBUG [cloud.vm.UserVmManagerImpl]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> Destroying vm VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc] as it failed to
> create on Host with Id:null
> 2014-03-11 14:31:43,617 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ]) 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
> 2014-03-11 14:31:43,619 WARN [apache.cloudstack.alerts]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> alertType:: 8 // dataCenterId:: 1 // podId:: null // clusterId:: null //
> message:: Failed to deploy Vm with Id: 406, on Host with Id: null
> 2014-03-11 14:31:43,687 INFO [user.vm.DeployVMCmd]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> com.cloud.exception.InsufficientServerCapacityException: Unable to create a
> deployment for VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]Scope=interface
> com.cloud.dc.DataCenter; id=1
> 2014-03-11 14:31:43,687 INFO [user.vm.DeployVMCmd]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> Unable to create a deployment for
> VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]
> com.cloud.exception.InsufficientServerCapacityException: Unable to create
> a deployment for
> VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]Scope=interface
> com.cloud.dc.DataCenter; id=1
> at
> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveVirtualMachine(VMEntityManagerImpl.java:209)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.reserve(VirtualMachineEntityImpl.java:198)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3405)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2966)
> at
> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:2952)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.java:420)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at
> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:701)
> 2014-03-11 14:31:43,688 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-10:job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ])
> Complete async job-1884 = [ b2f6f9f2-4b90-4595-8261-865d246c008f ],
> jobStatus: 2, resultCode: 530, result: Error Code: 533 Error text: Unable
> to create a deployment for VM[User|57c35883-2f48-4b3b-8693-72fc2c81e5fc]
> 2014-03-11 14:31:47,029 DEBUG [cloud.api.ApiServlet]
> (catalina-exec-4:null) ===START=== 172.16.200.98 -- GET
> command=queryAsyncJobResult&jobId=b2f6f9f2-4b90-4595-8261-865d246c008f&response=json&sessionkey=YoE%2BsxQvpWDO2D1MA4KzAt1bQYo%3D&_=1394519535676
> 2014-03-11 14:31:47,035 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-4:null) Async job-1884 = [
> b2f6f9f2-4b90-4595-8261-865d246c008f ] completed