请教一下，添加新的XenServer主机，是否可以升级物理主机的配置呢？还是建议选用同一配置的主机呢？
我目前面临的问题就是新的主机CPU主频变了 ? 这个会有影响么？在划分主机的时候 系统将怎么分配CPU呢？
cui6522123
?发件人：?tanthalas发送时间：?2014-03-26?19:08收件人：?users-cn主题：?Re: 回复: 回复:
虚拟机CPU主频是否可以高于物理机CPU主频Failed to alloc resource from host: 4 reservedCpu: 0,
used cpu: 52000, requested cpu: 3000, actual total cpu: 52800, total cpu with
overprovisioning: 52800, reservedMem: 0, used Mem: 121634816000, requested mem:
4194304000, total Mem:198546817024 ,considerReservedCapacity?: true
Host does not have enough CPU available, cannot allocate to this host.
日志里写的是，你的主机共有52800Hz，但已经用了52000，所以申请3000是分配不了的。
?
刘宇超
?
?
发件人： cui6522123
发送时间： 2014-03-26? 18:05:45
收件人： cloud
抄送：
主题： 回复: 回复: 虚拟机CPU主频是否可以高于物理机CPU主频
另外请教一下?? 在创建计算方案的时候? 这三个作用是什么？? 我可以让我的CPU仍然具有超线程技术么？
?
?
?
?
?
?
?
?
?
?
cui6522123
?
发件人： cui6522123
发送时间： 2014-03-26 18:03
收件人： cloud
主题： 回复: 回复: 虚拟机CPU主频是否可以高于物理机CPU主频
刘宇超
?
?
这个是之前的日志，请帮忙分析分析，谢谢！
?
?
2014-03-26 17:01:29,943 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-4:null) Ping from 2
2014-03-26 17:01:31,503 DEBUG [cloud.api.ApiServlet] (catalina-exec-10:null)
===START=== 114.251.179.130 -- GET
command=deployVirtualMachine&zoneId=4f8a1206-3712-4ad6-832e-f9bf430da511&templateId=0da260bc-620f-4ef0-abf7-e167dd217473&hypervisor=XenServer&serviceOfferingId=433d7c4f-e6a0-404c-8933-b8f51bd9016e&networkIds=0ef19e50-eef6-448c-af16-626e69b4fd58&displayname=test1&name=test1&response=json&sessionkey=W65MyiX8ZhTqdWc8zX6rxzd8c28%3D&_=1395824463805
2014-03-26 17:01:31,513 DEBUG [cloud.api.ApiDispatcher] (catalina-exec-10:null)
InfrastructureEntity name is:com.cloud.offering.ServiceOffering
2014-03-26 17:01:31,519 DEBUG [cloud.api.ApiDispatcher] (catalina-exec-10:null)
ControlledEntity name is:com.cloud.template.VirtualMachineTemplate
2014-03-26 17:01:31,523 DEBUG [cloud.api.ApiDispatcher] (catalina-exec-10:null)
ControlledEntity name is:com.cloud.network.Network
2014-03-26 17:01:31,542 DEBUG [cloud.network.NetworkModelImpl]
(catalina-exec-10:null) Service SecurityGroup is not supported in the network
id=204
2014-03-26 17:01:31,556 DEBUG [cloud.vm.UserVmManagerImpl]
(catalina-exec-10:null) Allocating in the DB for vm
2014-03-26 17:01:31,572 DEBUG [cloud.vm.VirtualMachineManagerImpl]
(catalina-exec-10:null) Allocating entries for VM: VM[User|test1]
2014-03-26 17:01:31,574 DEBUG [cloud.vm.VirtualMachineManagerImpl]
(catalina-exec-10:null) Allocating nics for VM[User|test1]
2014-03-26 17:01:31,576 DEBUG [cloud.network.NetworkManagerImpl]
(catalina-exec-10:null) Allocating nic for vm VM[User|test1] in network
Ntwk[204|Guest|15] with requested profile NicProfile[0-0-null-null-null
2014-03-26 17:01:31,601 DEBUG [cloud.network.NetworkModelImpl]
(catalina-exec-10:null) Service SecurityGroup is not supported in the network
id=204
2014-03-26 17:01:31,603 DEBUG [cloud.vm.VirtualMachineManagerImpl]
(catalina-exec-10:null) Allocating disks for VM[User|test1]
2014-03-26 17:01:31,621 DEBUG [cloud.vm.VirtualMachineManagerImpl]
(catalina-exec-10:null) Allocation completed for VM: VM[User|test1]
2014-03-26 17:01:31,621 DEBUG [cloud.vm.UserVmManagerImpl]
(catalina-exec-10:null) Successfully allocated DB entry for VM[User|test1]
2014-03-26 17:01:31,656 DEBUG [cloud.network.NetworkModelImpl]
(catalina-exec-10:null) Service SecurityGroup is not supported in the network
id=204
2014-03-26 17:01:31,662 DEBUG [cloud.network.NetworkModelImpl]
(catalina-exec-10:null) Service SecurityGroup is not supported in the network
id=204
2014-03-26 17:01:31,676 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-10:null) submit async job-360 = [
edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ], details: AsyncJobVO {id:360, userId: 2,
accountId: 2, sessionKey: null, instanceType: VirtualMachine, instanceId: 69,
cmd: org..apache.cloudstack.api.command.user.vm.DeployVMCmd, cmdOriginator:
null, cmdInfo:
{"sessionkey":"W65MyiX8ZhTqdWc8zX6rxzd8c28\u003d","cmdEventType":"VM.CREATE","ctxUserId":"2","serviceOfferingId":"433d7c4f-e6a0-404c-8933-b8f51bd9016e","httpmethod":"GET","zoneId":"4f8a1206-3712-4ad6-832e-f9bf430da511","templateId":"0da260bc-620f-4ef0-abf7-e167dd217473","response":"json","id":"69","networkIds":"0ef19e50-eef6-448c-af16-626e69b4fd58","hypervisor":"XenServer","name":"test1","_":"1395824463805","ctxAccountId":"2","ctxStartEventId":"1352","displayname":"test1"},
cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
processStatus: 0, resultCode: 0, result: null, initMsid: 264018885718825,
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2014-03-26 17:01:31,678 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-80:job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ]) Executing
org.apache.cloudstack.api.command.user..vm.DeployVMCmd for job-360 = [
edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ]
2014-03-26 17:01:31,679 DEBUG [cloud.api.ApiServlet] (catalina-exec-10:null)
===END=== 114.251.179.130 -- GET
command=deployVirtualMachine&zoneId=4f8a1206-3712-4ad6-832e-f9bf430da511&templateId=0da260bc-620f-4ef0-abf7-e167dd217473&hypervisor=XenServer&serviceOfferingId=433d7c4f-e6a0-404c-8933-b8f51bd9016e&networkIds=0ef19e50-eef6-448c-af16-626e69b4fd58&displayname=test1&name=test1&response=json&sessionkey=W65MyiX8ZhTqdWc8zX6rxzd8c28%3D&_=1395824463805
2014-03-26 17:01:31,686 DEBUG [cloud.api.ApiDispatcher]
(Job-Executor-80:job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ])
InfrastructureEntity name is:com.cloud.offering.ServiceOffering
2014-03-26 17:01:31,689 DEBUG [cloud.api.ApiDispatcher]
(Job-Executor-80:job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ])
ControlledEntity name is:com.cloud.template.VirtualMachineTemplate
2014-03-26 17:01:31,693 DEBUG [cloud.api.ApiDispatcher]
(Job-Executor-80:job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ])
ControlledEntity name is:com.cloud.network.Network
2014-03-26 17:01:31,722 DEBUG [cloud.network.NetworkModelImpl]
(Job-Executor-80:job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ]) Service
SecurityGroup is not supported in the network id=204
2014-03-26 17:01:31,728 DEBUG [cloud.network.NetworkModelImpl]
(Job-Executor-80:job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ]) Service
SecurityGroup is not supported in the network id=204
2014-03-26 17:01:31,749 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl]
(Job-Executor-80:job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ]) Deploy
avoids pods: [], clusters: [], hosts: []
2014-03-26 17:01:31,752 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl]
(Job-Executor-80:job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ])
DeploymentPlanner allocation algorithm:
com.cloud.deploy.FirstFitPlanner_EnhancerByCloudStack_6353a20@58fea438
2014-03-26 17:01:31,752 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl]
(Job-Executor-80:job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ]) Trying to
allocate a host and storage pools from dc:1, pod:null,cluster:null, requested
cpu: 3000, requested ram: 4194304000
2014-03-26 17:01:31,752 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl]
(Job-Executor-80:job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ]) Is ROOT
volume READY (pool already allocated)?: No
2014-03-26 17:01:31,752 DEBUG [cloud..deploy.FirstFitPlanner]
(Job-Executor-80:job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ]) Searching
all possible resources under this Zone: 1
2014-03-26 17:01:31,753 DEBUG [cloud.deploy.FirstFitPlanner]
(Job-Executor-80:job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ]) Listing
clusters in order of aggregate capacity, that have (atleast one host with)
enough CPU and RAM capacity under this Zone: 1
2014-03-26 17:01:31,758 DEBUG [cloud.deploy.FirstFitPlanner]
(Job-Executor-80:job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ]) Removing
from the clusterId list these clusters from avoid set: []
2014-03-26 17:01:31,768 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl]
(Job-Executor-80:job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ]) Checking
resources in Cluster: 1 under Pod: 1
2014-03-26 17:01:31,771 DEBUG [allocator.impl.FirstFitAllocator]
(Job-Executor-80:job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ]
FirstFitRoutingAllocator) Looking for hosts in dc: 1 pod:1 cluster:1
2014-03-26 17:01:31,776 DEBUG [allocator.impl.FirstFitAllocator]
(Job-Executor-80:job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ]
FirstFitRoutingAllocator) FirstFitAllocator has 2 hosts to check for
allocation: [Host[-1-Routing], Host[-4-Routing]]
2014-03-26 17:01:31,781 DEBUG [allocator.impl.FirstFitAllocator]
(Job-Executor-80:job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ]
FirstFitRoutingAllocator) Found 2 hosts for allocation after prioritization:
[Host[-1-Routing], Host[-4-Routing]]
2014-03-26 17:01:31,781 DEBUG [allocator.impl.FirstFitAllocator]
(Job-Executor-80:job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ]
FirstFitRoutingAllocator) Looking for speed=3000Mhz, Ram=4000
2014-03-26 17:01:31,787 DEBUG [cloud.capacity.CapacityManagerImpl]
(Job-Executor-80:job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ]
FirstFitRoutingAllocator) Checking if host: 1 has enough capacity for requested
CPU: 3000 and requested RAM: 4194304000 , cpuOverprovisioningFactor: 1.0
2014-03-26 17:01:31,790 DEBUG [cloud.capacity.CapacityManagerImpl]
(Job-Executor-80:job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ]
FirstFitRoutingAllocator) Hosts's actual total CPU: 52800 and CPU after
applying overprovisioning: 52800
2014-03-26 17:01:31,790 DEBUG [cloud.capacity.CapacityManagerImpl]
(Job-Executor-80:job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ]
FirstFitRoutingAllocator) Free CPU: 11300 , Requested CPU: 3000
2014-03-26 17:01:31,790 DEBUG [cloud.capacity.CapacityManagerImpl]
(Job-Executor-80:job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ]
FirstFitRoutingAllocator) Free RAM: 108990038016 , Requested RAM: 4194304000
2014-03-26 17:01:31,790 DEBUG [cloud.capacity.CapacityManagerImpl]
(Job-Executor-80:job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ]
FirstFitRoutingAllocator) Host has enough CPU and RAM available
2014-03-26 17:01:31,790 DEBUG [cloud.capacity.CapacityManagerImpl]
(Job-Executor-80:job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ]
FirstFitRoutingAllocator) STATS: Can alloc CPU from host: 1, used: 41500,
reserved: 0, actual total: 52800, total with overprovisioning: 52800; requested
cpu:3000,alloc_from_last_host?:false ,considerReservedCapacity?: true
2014-03-26 17:01:31,790 DEBUG [cloud..capacity.CapacityManagerImpl]
(Job-Executor-80:job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ]
FirstFitRoutingAllocator) STATS: Can alloc MEM from host: 1, used: 89556779008,
reserved: 0, total: 198546817024; requested mem:
4194304000,alloc_from_last_host?:false ,considerReservedCapacity?: true
2014-03-26 17:01:31,791 DEBUG [allocator.impl.FirstFitAllocator]
(Job-Executor-80:job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ]
FirstFitRoutingAllocator) Not using host 1; numCpusGood: true; cpuFreqGood:
false, host has capacity?true
2014-03-26 17:01:31,797 DEBUG [cloud.capacity.CapacityManagerImpl]
(Job-Executor-80:job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ]
FirstFitRoutingAllocator) Checking if host: 4 has enough capacity for requested
CPU: 3000 and requested RAM: 4194304000 , cpuOverprovisioningFactor: 1.0
2014-03-26 17:01:31,800 DEBUG [cloud.capacity.CapacityManagerImpl]
(Job-Executor-80:job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ]
FirstFitRoutingAllocator) Hosts's actual total CPU: 52800 and CPU after
applying overprovisioning: 52800
2014-03-26 17:01:31,800 DEBUG [cloud.capacity.CapacityManagerImpl]
(Job-Executor-80:job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ]
FirstFitRoutingAllocator) Free CPU: 800 , Requested CPU: 3000
2014-03-26 17:01:31,800 DEBUG [cloud.capacity.CapacityManagerImpl]
(Job-Executor-80:job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ]
FirstFitRoutingAllocator) Free RAM: 76912001024 , Requested RAM: 4194304000
2014-03-26 17:01:31,800 DEBUG [cloud.capacity.CapacityManagerImpl]
(Job-Executor-80:job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ]
FirstFitRoutingAllocator) STATS: Failed to alloc resource from host: 4
reservedCpu: 0, used cpu: 52000, requested cpu: 3000, actual total cpu: 52800,
total cpu with overprovisioning: 52800, reservedMem: 0, used Mem: 121634816000,
requested mem: 4194304000, total Mem:198546817024 ,considerReservedCapacity?:
true
2014-03-26 17:01:31,800 DEBUG [cloud.capacity.CapacityManagerImpl]
(Job-Executor-80:job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ]
FirstFitRoutingAllocator) Host does not have enough CPU available, cannot
allocate to this host.
2014-03-26 17:01:31,800 DEBUG [allocator.impl.FirstFitAllocator]
(Job-Executor-80:job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ]
FirstFitRoutingAllocator) Not using host 4; numCpusGood: true; cpuFreqGood:
false, host has capacity?false
2014-03-26 17:01:31,800 DEBUG [allocator.impl.FirstFitAllocator]
(Job-Executor-80:job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ]
FirstFitRoutingAllocator) Host Allocator returning 0 suitable hosts
2014-03-26 17:01:31,800 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl]
(Job-Executor-80:job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ]) No
suitable hosts found
2014-03-26 17:01:31,800 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl]
(Job-Executor-80:job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ]) No
suitable hosts found under this Cluster: 1
2014-03-26 17:01:31,804 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl]
(Job-Executor-80:job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ]) Could not
find suitable Deployment Destination for this VM under any clusters, returning.
2014-03-26 17:01:31,804 DEBUG [cloud.deploy.FirstFitPlanner]
(Job-Executor-80:job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ]) Searching
all possible resources under this Zone: 1
2014-03-26 17:01:31,806 DEBUG [cloud.deploy.FirstFitPlanner]
(Job-Executor-80:job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ]) Listing
clusters in order of aggregate capacity, that have (atleast one host with)
enough CPU and RAM capacity under this Zone: 1
2014-03-26 17:01:31,810 DEBUG [cloud.deploy.FirstFitPlanner]
(Job-Executor-80:job-360 = [ edd0f640-dc28-43cc-b02e-e4fc9a82aa44 ]) Removing
from the clusterId list these clusters from avoid set: [1]
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}}] }
?
?
?
?
?
cui6522123
?
发件人： cui6522123
发送时间： 2014-03-26 17:52
收件人： cloud
主题： 回复: RE: 虚拟机CPU主频是否可以高于物理机CPU主频
这个麻烦会在哪方面呢？？？？
?
?
?
?
我在想如果主频不同的话?? 放到一起的CPU 在划分新虚拟机的时候 能否会让分2.5GH在的主频呢? ？这个很让我纠结
?
?
?
?
?
cui6522123
?
发件人： zcsu
发送时间： 2014-03-26 17:46
收件人： users-cn@cloudstack.apache.org
主题： RE: 回复: RE: 虚拟机CPU主频是否可以高于物理机CPU主频
理论上是支持异构的服务器的，但是比较麻烦
> Date: Wed, 26 Mar 2014 17:35:24 +0800
> From: cui6522...@gmail..com
> To: users-cn@cloudstack.apache.org
> Subject: 回复: RE: 虚拟机CPU主频是否可以高于物理机CPU主频
>
>
>
>
>
>
>
> 您好~那我咨询一下另外的问题
>
> 我们已经生产的环境 ?现在要增加xensevrer主机了 ?
> 但我们之前的xenserver主机物理cpu主频是2.2GHz ? ?现在我新买的服务器 可以采购更高的主频CPU么？还是只能采购2.2GHz的呢？
> 以为我们发现虚拟机的单线程的CPU计算能力很低 ? 想提升下主频 ?这样是否可以呢？
>
>
> cui6522123
> ?发件人：?zcsu发送时间：?2014-03-26?17:20收件人：?users-cn@cloudstack.apache.org主题：?RE:
> 虚拟机CPU主频是否可以高于物理机CPU主频在我了解得情况下，不能高于物理机的主频
>?
> > Date: Wed, 26 Mar 2014 17:13:25 +0800
> > From: cui6522...@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
>? ?? ?
>
>
>
> ---
> 此电子邮件没有病毒和恶意软件，因为 avast! 防病毒保护处于活动状态。
> http://www.avast.com
????
?
?
?
?
此电子邮件不含病毒和恶意软件，因为 avast! 杀毒软件 保护处于活动状态。
---
此电子邮件没有病毒和恶意软件，因为 avast! 防病毒保护处于活动状态。
http://www.avast.com
