Mailing-List: contact users-cn-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users-cn@cloudstack.apache.org
Received-SPF: pass (nike.apache.org: domain of ahuabupt@gmail.com designates
 209.85.214.179 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <tencent_7296542A46F3BEB462060813@qq.com>
References: <tencent_7296542A46F3BEB462060813@qq.com>
Date: Mon, 10 Mar 2014 11:49:57 +0800
Message-ID: 
 <CAM6oDMeh2P1vFX+sWXRH6_ymtc+QLh=px2BL2+oUAuS4TApG1w@mail.gmail.com>
Subject: =?GB2312?B?UmU6IM2ouf1JU0/M7bzT0OnE4rv6yrXA/cqnsNw=?=
From: =?GB2312?B?1Pi52ruq?= <ahuabupt@gmail.com>
To: users-cn@cloudstack.apache.org
Content-Type: multipart/alternative; boundary=047d7b2e55ae4d21ab04f4387f31

--047d7b2e55ae4d21ab04f4387f31
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: quoted-printable

2014-03-10 11:09:27,924 DEBUG [cloud.deploy.FirstFitPlanner]
(Job-Executor-39:job-104) Listing clusters in order of aggregate capacity,
that have (atleast one host with) enough CPU and RAM capacity under this
Zone: 1
2014-03-10 11:09:27,926 DEBUG [cloud.deploy.FirstFitPlanner]
(Job-Executor-39:job-104) CPUOverprovisioningFactor considered: 2.0
2014-03-10 11:09:27,939 DEBUG [cloud.deploy.FirstFitPlanner]
(Job-Executor-39:job-104) 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.

=C4=E3=D3=A6=B8=C3=D6=BB=D3=D0=D2=BB=B8=F6hypervisor=A3=AC=C4=E3=B5=C4hyper=
visor=C0=E0=D0=CD=BA=CDvm=B5=C4=C0=E0=D0=CD=B6=D4=B2=BB=C9=CF=A3=AC=C3=BB=
=D3=D0=BA=CF=CA=CA=B5=C4hypervisor=A3=AC=CC=F8=B9=FD=C8=A5=C1=CB=A3=AC =D7=
=D4=C8=BB=BB=E1=B1=A8=D7=CA=D4=B4=B2=BB=D7=E3


2014-03-10 11:32 GMT+08:00 =B5=AD=BF=B4=B8=A1=BB=AA <360736449@qq.com>:

>
> =CE=D2=CA=C7=D4=DA=D2=BB=CC=A8=BB=FA=C6=F7=C9=CF=B0=B2=D7=B0ubuntu12.0.4=
=CF=B5=CD=B3=A3=AC=C8=BB=BA=F3=B2=BF=CA=F0cloudstack4.0.2=A3=AC=BC=C8=D7=F6=
=B9=DC=C0=ED=BD=DA=B5=E3=A3=AC=D3=D6=D7=F6=BC=C6=CB=E3=BD=DA=B5=E3=A1=A3=D6=
=F7=B4=E6=B4=A2=BA=CD=B6=FE=BC=B6=B4=E6=B4=A2=B6=BC=CA=C7=CD=A8=B9=FDNFS=B7=
=BD=CA=BD=CC=E1=B9=A9=A1=A3
>  =CD=A8=B9=FD=C9=CF=B4=CEISO=D6=C6=D7=F7=C1=CB=C4=A3=B0=E5=A3=AC=C8=BB=BA=
=F3=CD=A8=B9=FD=D5=E2=B8=F6ISO=C4=A3=B0=E5=B4=B4=BD=A8=D0=E9=C4=E2=BB=FA=CA=
=B5=C0=FD=A3=AC=CE=D2=B5=DA=D2=BB=B4=CE=B4=B4=BD=A8=B5=C4=CA=B1=BA=F2=CA=C7=
=B3=C9=B9=A6=C1=CB=A3=AC=BF=C9=CF=FA=BB=D9=CA=B5=C0=FD=D6=AE=BA=F3=A3=AC=D4=
=D9=B4=B4=BD=A8=A3=AC=BE=CD=B5=AF=B3=F6=CF=C2=C3=E6=B5=C4=B4=ED=CE=F3=CC=E1=
=CA=BE=A3=BA
>  Unable to create a deployment for VM[User|vm1]
>  =D0=E9=C4=E2=BB=FA=D7=B4=CC=AC=D2=B2=CF=D4=CA=BEerror.
>
>  =D7=EE=BD=FC=B8=D5=BD=D3=B4=A5cloudstack=A3=AC=BA=C3=B6=E0=B6=AB=CE=F7=
=B2=BB=B6=AE=A3=AC=BB=B9=CD=FB=B8=F7=CE=BB=B4=F3=C5=A3=C7=B0=B1=B2=B6=E0=B6=
=E0=D6=B8=B5=E3=B0=A1=A3=AC=D0=BB=D0=BB=A1=A3
>
>  =C8=D5=D6=BE=C8=E7=CF=C2=A3=A8=B1=A8=D5=D2=B2=BB=B5=BD=BA=CF=CA=CA=B5=C4=
=B2=BF=CA=F0=CE=BB=D6=C3=A3=A9=A3=BA
>  2014-03-10 11:09:24,075 DEBUG [cloud.cluster.ClusterManagerImpl]
> (Cluster-Heartbeat-1:null) Detected management node left, id:4,
> nodeIP:169.254.0.1
> 2014-03-10 11:09:24,076 INFO  [cloud.cluster.ClusterManagerImpl]
> (Cluster-Heartbeat-1:null) Trying to connect to 169.254.0.1
> 2014-03-10 11:09:24,076 INFO  [cloud.cluster.ClusterManagerImpl]
> (Cluster-Heartbeat-1:null) Management node 4 is detected inactive by
> timestamp but is pingable
> 2014-03-10 11:09:25,560 DEBUG [cloud.cluster.ClusterManagerImpl]
> (Cluster-Heartbeat-1:null) Detected management node left, id:4,
> nodeIP:169.254.0.1
> 2014-03-10 11:09:25,560 INFO  [cloud.cluster.ClusterManagerImpl]
> (Cluster-Heartbeat-1:null) Trying to connect to 169.254.0.1
> 2014-03-10 11:09:25,561 INFO  [cloud.cluster.ClusterManagerImpl]
> (Cluster-Heartbeat-1:null) Management node 4 is detected inactive by
> timestamp but is pingable
> 2014-03-10 11:09:26,995 DEBUG [cloud.api.ApiServlet]
> (catalina-exec-8:null) =3D=3D=3DSTART=3D=3D=3D  192.168.0.50 -- GET
>  command=3DdeployVirtualMachine&zoneId=3Dc27c3b63-6136-45bd-a779-95aafd3c=
91b4&templateId=3D5d6b7d6a-48fe-4009-8b11-cbea7242f971&hypervisor=3DKVM,KVM=
&serviceOfferingId=3D25c6d5d2-1feb-49c7-930e-69f51c1ea527&diskOfferingId=3D=
1f32d1e8-abe0-4d8c-8601-8fe2cf6c3835&displayname=3Dvm1&name=3Dvm1&response=
=3Djson&sessionkey=3DuazZwh3tFJL7FmrJVclZug8CMPo%3D&_=3D1394420930591
> 2014-03-10 11:09:27,029 DEBUG
> [cloud.configuration.ConfigurationManagerImpl] (catalina-exec-8:null)
> Access granted to Acct[2-admin] to zone:1 by DomainChecker
> 2014-03-10 11:09:27,029 DEBUG
> [cloud.configuration.ConfigurationManagerImpl] (catalina-exec-8:null)
> Access granted to Acct[2-admin] to zone:1 by DomainChecker
> 2014-03-10 11:09:27,085 DEBUG [cloud.cluster.ClusterManagerImpl]
> (Cluster-Heartbeat-1:null) Detected management node left, id:4,
> nodeIP:169.254.0.1
> 2014-03-10 11:09:27,085 INFO  [cloud.cluster.ClusterManagerImpl]
> (Cluster-Heartbeat-1:null) Trying to connect to 169.254.0.1
> 2014-03-10 11:09:27,085 INFO  [cloud.cluster.ClusterManagerImpl]
> (Cluster-Heartbeat-1:null) Management node 4 is detected inactive by
> timestamp but is pingable
> 2014-03-10 11:09:27,201 DEBUG [cloud.vm.UserVmManagerImpl]
> (catalina-exec-8:null) Allocating in the DB for vm
> 2014-03-10 11:09:27,202 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> (catalina-exec-8:null) Allocating entries for VM: VM[User|vm1]
> 2014-03-10 11:09:27,209 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> (catalina-exec-8:null) Allocating nics for VM[User|vm1]
> 2014-03-10 11:09:27,209 DEBUG [cloud.network.NetworkManagerImpl]
> (catalina-exec-8:null) Allocating nic for vm VM[User|vm1] in network
> Ntwk[204|Guest|6] with requested profile NicProfile[0-0-null-null-null
> 2014-03-10 11:09:27,221 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> (catalina-exec-8:null) Allocaing disks for VM[User|vm1]
> 2014-03-10 11:09:27,230 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> (catalina-exec-8:null) Allocation completed for VM: VM[User|vm1]
> 2014-03-10 11:09:27,231 DEBUG [cloud.vm.UserVmManagerImpl]
> (catalina-exec-8:null) Successfully allocated DB entry for VM[User|vm1]
> 2014-03-10 11:09:27,658 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-8:null) submit async job-104, details: AsyncJobVO {id:104,
> userId: 2, accountId: 2, sessionKey: null, instanceType: VirtualMachine,
> instanceId: 22, cmd: com.cloud.api.commands.DeployVMCmd, cmdOriginator:
> null, cmdInfo:
> {"sessionkey":"uazZwh3tFJL7FmrJVclZug8CMPo\u003d","ctxUserId":"2","servic=
eOfferingId":"25c6d5d2-1feb-49c7-930e-69f51c1ea527","zoneId":"c27c3b63-6136=
-45bd-a779-95aafd3c91b4","response":"json","templateId":"5d6b7d6a-48fe-4009=
-8b11-cbea7242f971","id":"22","hypervisor":"KVM,KVM","name":"vm1","diskOffe=
ringId":"1f32d1e8-abe0-4d8c-8601-8fe2cf6c3835","_":"1394420930591","ctxAcco=
untId":"2","ctxStartEventId":"392","displayname":"vm1"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 279278805450863,
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2014-03-10 11:09:27,660 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-39:job-104) Executing com.cloud.api.commands.DeployVMCmd fo=
r
> job-104
> 2014-03-10 11:09:27,665 DEBUG [cloud.api.ApiServlet]
> (catalina-exec-8:null) =3D=3D=3DEND=3D=3D=3D  192.168.0.50 -- GET
>  command=3DdeployVirtualMachine&zoneId=3Dc27c3b63-6136-45bd-a779-95aafd3c=
91b4&templateId=3D5d6b7d6a-48fe-4009-8b11-cbea7242f971&hypervisor=3DKVM,KVM=
&serviceOfferingId=3D25c6d5d2-1feb-49c7-930e-69f51c1ea527&diskOfferingId=3D=
1f32d1e8-abe0-4d8c-8601-8fe2cf6c3835&displayname=3Dvm1&name=3Dvm1&response=
=3Djson&sessionkey=3DuazZwh3tFJL7FmrJVclZug8CMPo%3D&_=3D1394420930591
> 2014-03-10 11:09:27,832 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-39:job-104) VM state transitted from :Stopped to Starting
> with event: StartRequestedvm's original host id: null new host id: null
> host id before state transition: null
> 2014-03-10 11:09:27,832 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-39:job-104) Successfully transitioned to start state for
> VM[User|vm1] reservation id =3D 26596ed8-6c57-451b-886a-63c31c9d3070
> 2014-03-10 11:09:27,917 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-39:job-104) Trying to deploy VM, vm has dcId: 1 and podId:
> null
> 2014-03-10 11:09:27,917 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-39:job-104) Deploy avoids pods: null, clusters: null, hosts=
:
> null
> 2014-03-10 11:09:27,920 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-39:job-104) DeploymentPlanner allocation algorithm: random
> 2014-03-10 11:09:27,921 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-39:job-104) Trying to allocate a host and storage pools fro=
m
> dc:1, pod:null,cluster:null, requested cpu: 1000, requested ram: 10737418=
24
> 2014-03-10 11:09:27,921 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-39:job-104) Is ROOT volume READY (pool already allocated)?:=
 No
> 2014-03-10 11:09:27,921 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-39:job-104) Searching all possible resources under this Zon=
e:
> 1
> 2014-03-10 11:09:27,924 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-39:job-104) Listing clusters in order of aggregate capacity=
,
> that have (atleast one host with) enough CPU and RAM capacity under this
> Zone: 1
> 2014-03-10 11:09:27,926 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-39:job-104) CPUOverprovisioningFactor considered: 2.0
> 2014-03-10 11:09:27,939 DEBUG [cloud.deploy.FirstFitPlanner]
> (Job-Executor-39:job-104) Cluster: 1 has HyperVisorType that does not mat=
ch
> 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.
> 2014-03-10 11:09:28,075 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-39:job-104) VM state transitted from :Starting to Stopped
> with event: OperationFailedvm's original host id: null new host id: null
> host id before state transition: null
> 2014-03-10 11:09:28,081 DEBUG [cloud.vm.UserVmManagerImpl]
> (Job-Executor-39:job-104) Destroying vm VM[User|vm1] as it failed to crea=
te
> 2014-03-10 11:09:28,228 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-39:job-104) VM state transitted from :Stopped to Error with
> event: OperationFailedToErrorvm's original host id: null new host id: nul=
l
> host id before state transition: null
> 2014-03-10 11:09:28,580 DEBUG [cloud.cluster.ClusterManagerImpl]
> (Cluster-Heartbeat-1:null) Detected management node left, id:4,
> nodeIP:169.254.0.1
> 2014-03-10 11:09:28,580 INFO  [cloud.cluster.ClusterManagerImpl]
> (Cluster-Heartbeat-1:null) Trying to connect to 169.254.0.1
> 2014-03-10 11:09:28,580 INFO  [cloud.cluster.ClusterManagerImpl]
> (Cluster-Heartbeat-1:null) Management node 4 is detected inactive by
> timestamp but is pingable
> 2014-03-10 11:09:28,788 INFO  [api.commands.DeployVMCmd]
> (Job-Executor-39:job-104)
> com.cloud.exception.InsufficientServerCapacityException: Unable to create=
 a
> deployment for VM[User|vm1]Scope=3Dinterface com.cloud.dc.DataCenter; id=
=3D1
> 2014-03-10 11:09:28,788 WARN  [cloud.api.ApiDispatcher]
> (Job-Executor-39:job-104) class com.cloud.api.ServerApiException : Unable
> to create a deployment for VM[User|vm1]
> 2014-03-10 11:09:28,788 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-39:job-104) Complete async job-104, jobStatus: 2, resultCod=
e:
> 530, result: Error Code: 533 Error text: Unable to create a deployment fo=
r
> VM[User|vm1]
> 2014-03-10 11:09:30,057 DEBUG [cloud.cluster.ClusterManagerImpl]
> (Cluster-Heartbeat-1:null) Detected management node left, id:4,
> nodeIP:169.254.0.1
> 2014-03-10 11:09:30,057 INFO  [cloud.cluster.ClusterManagerImpl]
> (Cluster-Heartbeat-1:null) Trying to connect to 169.254.0.1
> 2014-03-10 11:09:30,057 INFO  [cloud.cluster.ClusterManagerImpl]
> (Cluster-Heartbeat-1:null) Management node 4 is detected inactive by
> timestamp but is pingable
> 2014-03-10 11:09:31,582 DEBUG [cloud.cluster.ClusterManagerImpl]
> (Cluster-Heartbeat-1:null) Detected management node left, id:4,
> nodeIP:169.254.0.1
> 2014-03-10 11:09:31,583 INFO  [cloud.cluster.ClusterManagerImpl]
> (Cluster-Heartbeat-1:null) Trying to connect to 169.254.0.1
> 2014-03-10 11:09:31,583 INFO  [cloud.cluster.ClusterManagerImpl]
> (Cluster-Heartbeat-1:null) Management node 4 is detected inactive by
> timestamp but is pingable
> 2014-03-10 11:09:32,779 DEBUG [cloud.api.ApiServlet]
> (catalina-exec-9:null) =3D=3D=3DSTART=3D=3D=3D  192.168.0.50 -- GET
>  command=3DqueryAsyncJobResult&jobId=3Dfa74b389-fd45-4eae-8027-019cea2abc=
b7&response=3Djson&sessionkey=3DuazZwh3tFJL7FmrJVclZug8CMPo%3D&_=3D13944209=
36375
> 2014-03-10 11:09:32,795 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-9:null) Async job-104 completed
> 2014-03-10 11:09:32,806 DEBUG [cloud.api.ApiServlet]
> (catalina-exec-9:null) =3D=3D=3DEND=3D=3D=3D  192.168.0.50 -- GET
>  command=3DqueryAsyncJobResult&jobId=3Dfa74b389-fd45-4eae-8027-019cea2abc=
b7&response=3Djson&sessionkey=3DuazZwh3tFJL7FmrJVclZug8CMPo%3D&_=3D13944209=
36375
> 2014-03-10 11:09:32,819 DEBUG [cloud.api.ApiServlet]
> (catalina-exec-2:null) =3D=3D=3DSTART=3D=3D=3D  192.168.0.50 -- GET
>  command=3DlistVirtualMachines&id=3D29273813-ed66-4106-97fb-4b80356fd243&=
response=3Djson&sessionkey=3DuazZwh3tFJL7FmrJVclZug8CMPo%3D&_=3D13944209364=
10
> 2014-03-10 11:09:32,827 DEBUG [cloud.vm.UserVmManagerImpl]
> (catalina-exec-2:null) THE WHERE CLAUSE IS:user_vm.id =3D ?
> 2014-03-10 11:09:32,866 DEBUG [cloud.api.ApiServlet]
> (catalina-exec-2:null) =3D=3D=3DEND=3D=3D=3D  192.168.0.50 -- GET
>  command=3DlistVirtualMachines&id=3D29273813-ed66-4106-97fb-4b80356fd243&=
response=3Djson&sessionkey=3DuazZwh3tFJL7FmrJVclZug8CMPo%3D&_=3D13944209364=
10
> 2014-03-10 11:09:33,083 DEBUG [cloud.cluster.ClusterManagerImpl]
> (Cluster-Heartbeat-1:null) Detected management node left, id:4,
> nodeIP:169.254.0.1
> 2014-03-10 11:09:33,083 INFO  [cloud.cluster.ClusterManagerImpl]
> (Cluster-Heartbeat-1:null) Trying to connect to 169.254.0.1
> 2014-03-10 11:09:33,083 INFO  [cloud.cluster.ClusterManagerImpl]
> (Cluster-Heartbeat-1:null) Management node 4 is detected inactive by
> timestamp but is pingable
> 2014-03-10 11:09:34,567 DEBUG [cloud.cluster.ClusterManagerImpl]
> (Cluster-Heartbeat-1:null) Detected management node left, id:4,
> nodeIP:169.254.0.1
> 2014-03-10 11:09:34,567 INFO  [cloud.cluster.ClusterManagerImpl]
> (Cluster-Heartbeat-1:null) Trying to connect to 169.254.0.1
> 2014-03-10 11:09:34,567 INFO  [cloud.cluster.ClusterManagerImpl]
> (Cluster-Heartbeat-1:null) Management node 4 is detected inactive by
> timestamp but is pingable
> 2014-03-10 11:09:34,768 DEBUG [cloud.server.StatsCollector]
> (StatsCollector-3:null) VmStatsCollector is running...
> 2014-03-10 11:09:36,059 DEBUG [cloud.cluster.ClusterManagerImpl]
> (Cluster-Heartbeat-1:null) Detected management node left, id:4,
> nodeIP:169.254.0.1
> 2014-03-10 11:09:36,060 INFO  [cloud.cluster.ClusterManagerImpl]
> (Cluster-Heartbeat-1:null) Trying to connect to 169.254.0.1
> 2014-03-10 11:09:36,060 INFO  [cloud.cluster.ClusterManagerImpl]
> (Cluster-Heartbeat-1:null) Management node 4 is detected inactive by
> timestamp but is pingable
> 2014-03-10 11:09:36,969 DEBUG
> [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Zone =
1
> is ready to launch secondary storage VM
> 2014-03-10 11:09:37,126 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl=
]
> (consoleproxy-1:null) Zone 1 is ready to launch console proxy

--047d7b2e55ae4d21ab04f4387f31--