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 "yhzhao@pipgame.com" <yh...@pipgame.com> on 2014/03/26 10:26:53 UTC
回复: RE: 虚拟机CPU主频是否可以高于物理机CPU主频
新添加进集群中的主机物理主频要高于现有集群中的主要的主频，请问下，划分虚拟机的时候主频应该以哪个为准。。用的是XenServer
赵元海
平台MIS部
9095
yhzhao@pipgame.com
*****************************************************
发件人： zcsu
发送时间： 2014-03-26 17:20
收件人： users-cn@cloudstack.apache.org
主题： RE: 虚拟机CPU主频是否可以高于物理机CPU主频
在我了解得情况下，不能高于物理机的主频
> Date: Wed, 26 Mar 2014 17:13:25 +0800
> From: cui6522123@gmail.com
> To: users-cn@cloudstack.apache.org
> Subject: 虚拟机CPU主频是否可以高于物理机CPU主频
>
>
>
>
>
>
>
> 请教创建虚拟机时的报错信息：看样子是资源不足，但我只创建了1个核心 3GHz的CPU ?为什么会提示这样的错误呢？
> 另外想咨询一下：物理主机CPU的主频是2.2GHz ? 我虚拟机分配的时候计算方案可以高于这个主频么？我现在分配的就是3GHz ?就报错了，不知道是否会是这样的问题？
>
> 具体报错信息如下：
> 2014-03-26 17:01:31,812 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-80:job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ]) No clusters found after removing disabled clusters and clusters in avoid list, returning.
>
> 2014-03-26 17:01:31,816 DEBUG [cloud.vm.UserVmManagerImpl] (Job-Executor-80:job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ]) Destroying vm VM[User|test1] as it failed to create on Host with Id:null
>
> 2014-03-26 17:01:31,831 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-80:job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ]) 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-26 17:01:31,837 WARN [apache.cloudstack.alerts] (Job-Executor-80:job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ]) alertType:: 8 // dataCenterId:: 1 // podId:: null // clusterId:: null // message:: Failed to deploy Vm with Id: 69, on Host with Id: null
>
> 2014-03-26 17:01:31,859 INFO [user.vm.DeployVMCmd] (Job-Executor-80:job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ]) com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[User|test1]Scope=interface com.cloud.dc.DataCenter; id=1
>
> 2014-03-26 17:01:31,860 INFO [user.vm.DeployVMCmd] (Job-Executor-80:job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ]) Unable to create a deployment for VM[User|test1]
>
> com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[User|test1]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:441)
>
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>
> at java.lang.Thread.run(Thread.java:662)
>
> 2014-03-26 17:01:31,862 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-80:job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ]) Complete async job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ], jobStatus: 2, resultCode: 530, result: Error Code: 533 Error text: Unable to create a deployment for VM[User|test1]
>
> 2014-03-26 17:01:31,983 DEBUG [agent.manager.AgentManagerImpl] (AgentManager-Handler-1:null) SeqA 2-956037: Processing Seq 2-956037: { Cmd , MgmtId: -1, via: 2, Ver: v1, Flags: 11, [{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":2,"_loadInfo":"{\n \"connections\": []\n}","wait":0}}] }
>
> 2014-03-26 17:01:31,986 DEBUG [agent.manager.AgentManagerImpl] (AgentManager-Handler-1:null) SeqA 2-956037: Sending Seq 2-956037: { Ans: , MgmtId: 264018885718825, via: 2, Ver: v1, Flags: 100010, [{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}] }
>
> 2014-03-26 17:01:34,753 DEBUG [cloud.api.ApiServlet] (catalina-exec-22:null) ===START=== 114.251.179.130 -- GET command=queryAsyncJobResult&jobId=edd0f640-dc28-43cc-b02e-e4fc9a82aa44&response=json&sessionkey=W65MyiX8ZhTqdWc8zX6rxzd8c28%3D&_=1395824467039
>
> 2014-03-26 17:01:34,768 DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-22:null) Async job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ] completed
>
> 2014-03-26 17:01:34,774 DEBUG [cloud.api.ApiServlet] (catalina-exec-22:null) ===END=== 114.251.179.130 -- GET command=queryAsyncJobResult&jobId=edd0f640-dc28-43cc-b02e-e4fc9a82aa44&response=json&sessionkey=W65MyiX8ZhTqdWc8zX6rxzd8c28%3D&_=1395824467039
>
> 2014-03-26 17:01:34,832 DEBUG [cloud.api.ApiServlet] (catalina-exec-3:null) ===START=== 114.251.179.130 -- GET command=listVirtualMachines&id=a4edf352-07d5-439a-9a5c-95912d1379aa&response=json&sessionkey=W65MyiX8ZhTqdWc8zX6rxzd8c28%3D&_=1395824467133
>
> 2014-03-26 17:01:34,857 DEBUG [cloud.api.ApiServlet] (catalina-exec-3:null) ===END=== 114.251.179.130 -- GET command=listVirtualMachines&id=a4edf352-07d5-439a-9a5c-95912d1379aa&response=json&sessionkey=W65MyiX8ZhTqdWc8zX6rxzd8c28%3D&_=1395824467133
>
> 2014-03-26 17:01:35,168 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-495:null) Ping from 1
>
>
> cui6522123
>
>
>
> ---
> 此电子邮件没有病毒和恶意软件，因为 avast! 防病毒保护处于活动状态。
> http://www.avast.com