我觉得你说的着一块各种原因都可能会有，xenserver须在6.2以上版本或者6.0企业版才支持内存超配（设定了静态最小内存为静态最大内存的1/4，这就意味xenserver内存超配不能超过实际内存的4倍），也有可能是CS的某个版本对超配功能的实现有BUG. 你再分析一下环境及日志，看看是什么情况造成超配不成功吧 实在不行的话你可以拿到源码调试一下。
2014/1/16 王磊 <wang...@smartdot.com> > > 有人做过这种超额分配的实验吗，我用的是xenserver，启用了本地存储，CPU、mem、storage都做了5倍的超额分配，但还是报这种资源不够的提示 > > > > 发件人：严思恒 <yansiheng...@163.com> > 发送时间：2014-01-16 09:37 > 主题：Re:回复: Re:日志 > 收件人："users-cn"<users-cn@cloudstack.apache.org> > 抄送： > > 你这个确实是资源不够所造成的创建失败 > 在 2014-01-15 18:33:38，"王磊" <wang...@smartdot.com> 写道： > >下面的日志能否判断出是资源不够造成的无法创建实例？因为我现在CPU占81%，内存占35%，本地存储占69% > >但是cpu.overprovisioning.factor、mem.overprovisioning.factor、storage.overprovisioning.factor > 这三项的值我都已经设成了5 > > > >2014-01-10 18:04:19,332 DEBUG > [cloud.deploy.DeploymentPlanningManagerImpl] (Job-Executor-8:job-106 = [ > 88506db5-d1a6-431a-8fd6-9f0bdedf9281 ]) Is ROOT volume READY (pool already > allocated)?: No > >2014-01-10 18:04:19,332 DEBUG [cloud.deploy.FirstFitPlanner] > (Job-Executor-8:job-106 = [ 88506db5-d1a6-431a-8fd6-9f0bdedf9281 ]) > Searching all possible resources under this Zone: 1 > >2014-01-10 18:04:19,333 DEBUG [cloud.deploy.FirstFitPlanner] > (Job-Executor-8:job-106 = [ 88506db5-d1a6-431a-8fd6-9f0bdedf9281 ]) Listing > clusters in order of aggregate capacity, that have (atleast one host with) > enough CPU and RAM capacity under this Zone: 1 > >2014-01-10 18:04:19,336 DEBUG [cloud.deploy.FirstFitPlanner] > (Job-Executor-8:job-106 = [ 88506db5-d1a6-431a-8fd6-9f0bdedf9281 ]) > Removing from the clusterId list these clusters from avoid set: [] > >2014-01-10 18:04:19,340 DEBUG [cloud.deploy.FirstFitPlanner] > (Job-Executor-8:job-106 = [ 88506db5-d1a6-431a-8fd6-9f0bdedf9281 ]) Cannot > allocate cluster list [1] for vm creation since their allocated percentage > crosses the disable capacity threshold defined at each cluster/ at global > value for capacity Type : 1, skipping these clusters > >2014-01-10 18:04:19,340 DEBUG [cloud.deploy.FirstFitPlanner] > (Job-Executor-8:job-106 = [ 88506db5-d1a6-431a-8fd6-9f0bdedf9281 ]) No > clusters found after removing disabled clusters and clusters in avoid list, > returning. > >2014-01-10 18:04:19,342 DEBUG [cloud.vm.UserVmManagerImpl] > (Job-Executor-8:job-106 = [ 88506db5-d1a6-431a-8fd6-9f0bdedf9281 ]) > Destroying vm VM[User|centos-7] as it failed to create on Host with Id:null > >2014-01-10 18:04:19,351 DEBUG [cloud.capacity.CapacityManagerImpl] > (Job-Executor-8:job-106 = [ 88506db5-d1a6-431a-8fd6-9f0bdedf9281 ]) 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-01-10 18:04:19,358 WARN [apache.cloudstack.alerts] > (Job-Executor-8:job-106 = [ 88506db5-d1a6-431a-8fd6-9f0bdedf9281 ]) > alertType:: 8 // dataCenterId:: 1 // podId:: null // clusterId:: null // > message:: Failed to deploy Vm with Id: 30, on Host with Id: null > >2014-01-10 18:04:19,381 INFO [user.vm.DeployVMCmd] > (Job-Executor-8:job-106 = [ 88506db5-d1a6-431a-8fd6-9f0bdedf9281 ]) > com.cloud.exception.InsufficientServerCapacityException: Unable to create a > deployment for VM[User|centos-7]Scope=interface com.cloud.dc.DataCenter; > id=1 > >2014-01-10 18:04:19,381 INFO [user.vm.DeployVMCmd] > (Job-Executor-8:job-106 = [ 88506db5-d1a6-431a-8fd6-9f0bdedf9281 ]) Unable > to create a deployment for VM[User|centos-7] > >com.cloud.exception.InsufficientServerCapacityException: Unable to create > a deployment for VM[User|centos-7]Scope=interface com.cloud.dc.DataCenter; > id=1 > > > > > > > >发件人：严思恒 <yansiheng...@163.com> > >发送时间：2014-01-15 18:14 > >主题：Re:日志 > >收件人："users-cn"<users-cn@cloudstack.apache.org> > >抄送： > > > >出现这种情况，不一定就是系统资源不足，也有可能是配置问题 > >在 2014-01-15 17:36:07，"王磊" <wang...@smartdot.com> 写道： > >>是不是只要出现 > >> > >>“com.cloud.exception.InsufficientServerCapacityException: Unable to > create a deployment for VM[User|centos-2341]Scope=interface > com.cloud.dc.DataCenter; id=1” > >> > >>就表示是系统资源不足造成的实例创建失败 >
