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 toudsf <18...@163.com> on 2014/03/06 07:08:20 UTC
回复: Re: 4.2.1版本中，vmha功能无效
到后台看了一下。没有再启动的相关日志。
2014-03-06
toudsf
发件人："linuxbqj@gmail.com" <li...@gmail.com>
发送时间：2014-03-06 12:23
主题：Re: 4.2.1版本中，vmha功能无效
收件人："users-cn"<us...@cloudstack.apache.org>
抄送：
有相关的日志吗？建议提供一些日志信息
在 2014年3月6日 上午10:44，toudsf <18...@163.com> 写道：
> 虚拟化平台使用VMWARE
> 1、设置了全局设置中的ha.tag
> 2、设置了主机的host的主机标签
> 3、在服务器中增加计算方案，启用高可用性和设置主机标签
> 4、创建虚拟机选择HA的计算方案
> 5、关闭虚拟机后，没有新的虚拟机启动起来。
>
> 以前测试过4.1是好的，请各位大侠指教！
>
> 2014-03-06
>
>
>
> toudsf
--
白清杰 (Born Bai)
北京开源愿景信息技术有限公司
Mail: linuxbqj@gmail.com
回复: Re: Re: 4.2.1版本中，vmha功能无效
Posted by toudsf <18...@163.com>.
关闭后有以下日志，关闭的是i-2-14,用init 0命令直接到vcenter上关闭的。
DEBUG [agent.manager.AgentManagerImpl] (AgentManager-Handler-11:) SeqA 3-22496: Processing Seq 3-22496: { Cmd , MgmtId: -1, via: 3, Ver: v1, Flags: 11, [{"com.cloud.a
gent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":2,"_loadInfo":"{\n \"connections\": []\n}","wait":0}}] }
DEBUG [agent.manager.AgentManagerImpl] (AgentManager-Handler-11:) SeqA 3-22496: Sending Seq 3-22496: { Ans: , MgmtId: 90520735180840, via: 3, Ver: v1, Flags: 100010,
[{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}] }
DEBUG [cloud.api.ApiServlet] (catalina-exec-22:) ===START=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=jso
n&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086872614
DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-22:) Async job-77 = [ 1219fffc-fcd4-481d-8393-bc57e052cc52 ] completed
DEBUG [cloud.api.ApiServlet] (catalina-exec-22:) ===END=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=json&
sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086872614
DEBUG [cloud.server.StatsCollector] (StatsCollector-1:) StorageCollector is running...
DEBUG [agent.transport.Request] (StatsCollector-1:) Seq 4-592184689: Received: { Ans: , MgmtId: 90520735180840, via: 4, Ver: v1, Flags: 10, { GetStorageStatsAnswer }
}
DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-440:) Seq 1-1589709769: Executing request
DEBUG [vmware.resource.VmwareResource] (DirectAgent-440:192.168.10.7) Datastore summary info, storageId: 2f3ce86c-4de2-3f29-8af8-339fdb21e47a, localPath: /data1/export
s/vmware1, poolType: NetworkFilesystem, capacity: 845791174656, free: 497398603776, used: 348392570880
DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-440:) Seq 1-1589709769: Response Received:
DEBUG [agent.transport.Request] (StatsCollector-1:) Seq 1-1589709769: Received: { Ans: , MgmtId: 90520735180840, via: 1, Ver: v1, Flags: 10, { GetStorageStatsAnswer }
}
DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-113:) Seq 1-1589709770: Executing request
DEBUG [vmware.resource.VmwareResource] (DirectAgent-113:192.168.10.7) Datastore summary info, storageId: 7e04423c-575a-3825-9242-3f37ab421a52, localPath: /data1/export
s/vmware2, poolType: NetworkFilesystem, capacity: 845791174656, free: 497431793664, used: 348359380992
DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-113:) Seq 1-1589709770: Response Received:
DEBUG [agent.transport.Request] (StatsCollector-1:) Seq 1-1589709770: Received: { Ans: , MgmtId: 90520735180840, via: 1, Ver: v1, Flags: 10, { GetStorageStatsAnswer }
}
DEBUG [cloud.api.ApiServlet] (catalina-exec-20:) ===START=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=jso
n&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086875614
DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-20:) Async job-77 = [ 1219fffc-fcd4-481d-8393-bc57e052cc52 ] completed
DEBUG [cloud.api.ApiServlet] (catalina-exec-20:) ===END=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=json&
sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086875614
INFO [vmware.resource.VmwareResource] (DirectAgent-194:) Scan hung worker VM to recycle
DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-194:) Ping from 1
INFO [vmware.resource.VmwareResource] (DirectAgent-489:) Scan hung worker VM to recycle
DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-489:) Ping from 2
DEBUG [cloud.api.ApiServlet] (catalina-exec-15:) ===START=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=jso
n&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086878615
DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-15:) Async job-77 = [ 1219fffc-fcd4-481d-8393-bc57e052cc52 ] completed
DEBUG [cloud.api.ApiServlet] (catalina-exec-15:) ===END=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=json&
sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086878615
DEBUG [agent.manager.AgentManagerImpl] (AgentManager-Handler-12:) SeqA 3-22497: Processing Seq 3-22497: { Cmd , MgmtId: -1, via: 3, Ver: v1, Flags: 11, [{"com.cloud.a
gent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":2,"_loadInfo":"{\n \"connections\": []\n}","wait":0}}] }
DEBUG [agent.manager.AgentManagerImpl] (AgentManager-Handler-12:) SeqA 3-22497: Sending Seq 3-22497: { Ans: , MgmtId: 90520735180840, via: 3, Ver: v1, Flags: 100010,
[{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}] }
DEBUG [cloud.api.ApiServlet] (catalina-exec-25:) ===START=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=jso
n&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086881614
DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-25:) Async job-77 = [ 1219fffc-fcd4-481d-8393-bc57e052cc52 ] completed
DEBUG [cloud.api.ApiServlet] (catalina-exec-25:) ===END=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=json&
sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086881614
DEBUG [cloud.api.ApiServlet] (catalina-exec-19:) ===START=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=jso
n&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086884612
DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-19:) Async job-77 = [ 1219fffc-fcd4-481d-8393-bc57e052cc52 ] completed
DEBUG [cloud.api.ApiServlet] (catalina-exec-19:) ===END=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=json&
sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086884612
DEBUG [cloud.api.ApiServlet] (catalina-exec-9:) ===START=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=json
&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086887616
DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-9:) Async job-77 = [ 1219fffc-fcd4-481d-8393-bc57e052cc52 ] completed
DEBUG [cloud.api.ApiServlet] (catalina-exec-9:) ===END=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=json&s
essionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086887616
DEBUG [cloud.server.StatsCollector] (StatsCollector-1:) HostStatsCollector is running...
DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-245:) Seq 1-1589709771: Executing request
DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-245:) Seq 1-1589709771: Response Received:
DEBUG [agent.transport.Request] (StatsCollector-1:) Seq 1-1589709771: Received: { Ans: , MgmtId: 90520735180840, via: 1, Ver: v1, Flags: 10, { GetHostStatsAnswer } }
DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-365:) Seq 2-700518432: Executing request
DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-365:) Seq 2-700518432: Response Received:
DEBUG [agent.transport.Request] (StatsCollector-1:) Seq 2-700518432: Received: { Ans: , MgmtId: 90520735180840, via: 2, Ver: v1, Flags: 10, { GetHostStatsAnswer } }
DEBUG [agent.manager.AgentManagerImpl] (AgentManager-Handler-14:) SeqA 3-22498: Processing Seq 3-22498: { Cmd , MgmtId: -1, via: 3, Ver: v1, Flags: 11, [{"com.cloud.a
gent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":2,"_loadInfo":"{\n \"connections\": []\n}","wait":0}}] }
DEBUG [agent.manager.AgentManagerImpl] (AgentManager-Handler-14:) SeqA 3-22498: Sending Seq 3-22498: { Ans: , MgmtId: 90520735180840, via: 3, Ver: v1, Flags: 100010,
[{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}] }
DEBUG [cloud.api.ApiServlet] (catalina-exec-3:) ===START=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=json
&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086890613
DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-3:) Async job-77 = [ 1219fffc-fcd4-481d-8393-bc57e052cc52 ] completed
DEBUG [cloud.api.ApiServlet] (catalina-exec-3:) ===END=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=json&s
essionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086890613
DEBUG [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:) Zone 1 is ready to launch secondary storage VM
DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] (consoleproxy-1:) Zone 1 is ready to launch console proxy
DEBUG [cloud.server.StatsCollector] (StatsCollector-3:) VmStatsCollector is running...
DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-182:) Seq 1-1589709772: Executing request
DEBUG [vmware.mo.HostMO] (DirectAgent-182:192.168.10.7) find VM i-2-10-VM on host
INFO [vmware.mo.HostMO] (DirectAgent-182:192.168.10.7) VM i-2-10-VM not found in host cache
DEBUG [vmware.mo.HostMO] (DirectAgent-182:192.168.10.7) load VM cache on host
DEBUG [vmware.mo.HostMO] (DirectAgent-182:192.168.10.7) find VM i-2-17-VM on host
DEBUG [vmware.mo.HostMO] (DirectAgent-182:192.168.10.7) VM i-2-17-VM found in host cache
DEBUG [vmware.mo.HostMO] (DirectAgent-182:192.168.10.7) find VM i-2-7-VM on host
DEBUG [vmware.mo.HostMO] (DirectAgent-182:192.168.10.7) VM i-2-7-VM found in host cache
DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-182:) Seq 1-1589709772: Response Received:
DEBUG [agent.transport.Request] (StatsCollector-3:) Seq 1-1589709772: Received: { Ans: , MgmtId: 90520735180840, via: 1, Ver: v1, Flags: 10, { GetVmStatsAnswer } }
DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-279:) Seq 2-700518433: Executing request
DEBUG [vmware.mo.HostMO] (DirectAgent-279:192.168.10.8) find VM i-2-14-VM on host
INFO [vmware.mo.HostMO] (DirectAgent-279:192.168.10.8) VM i-2-14-VM not found in host cache
DEBUG [vmware.mo.HostMO] (DirectAgent-279:192.168.10.8) load VM cache on host
DEBUG [vmware.mo.HostMO] (DirectAgent-279:192.168.10.8) find VM i-2-16-VM on host
DEBUG [vmware.mo.HostMO] (DirectAgent-279:192.168.10.8) VM i-2-16-VM found in host cache
DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-279:) Seq 2-700518433: Response Received:
DEBUG [agent.transport.Request] (StatsCollector-3:) Seq 2-700518433: Received: { Ans: , MgmtId: 90520735180840, via: 2, Ver: v1, Flags: 10, { GetVmStatsAnswer } }
DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (RouterStatusMonitor-1:) Found 1 routers to update status.
DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (RouterStatusMonitor-1:) Found 0 networks to update RvR status.
DEBUG [cloud.api.ApiServlet] (catalina-exec-2:) ===START=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=json
&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086893606
DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-2:) Async job-77 = [ 1219fffc-fcd4-481d-8393-bc57e052cc52 ] completed
DEBUG [cloud.api.ApiServlet] (catalina-exec-2:) ===END=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=json&s
essionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086893606
DEBUG [agent.manager.AgentManagerImpl] (AgentManager-Handler-1:) SeqA 3-22499: Processing Seq 3-22499: { Cmd , MgmtId: -1, via: 3, Ver: v1, Flags: 11, [{"com.cloud.ag
ent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":2,"_loadInfo":"{\n \"connections\": []\n}","wait":0}}] }
DEBUG [agent.manager.AgentManagerImpl] (AgentManager-Handler-1:) SeqA 3-22499: Sending Seq 3-22499: { Ans: , MgmtId: 90520735180840, via: 3, Ver: v1, Flags: 100010, [
{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}] }
DEBUG [cloud.api.ApiServlet] (catalina-exec-12:) ===START=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=jso
n&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086896602
DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-12:) Async job-77 = [ 1219fffc-fcd4-481d-8393-bc57e052cc52 ] completed
DEBUG [cloud.api.ApiServlet] (catalina-exec-12:) ===END=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=json&
sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086896602
DEBUG [cloud.api.ApiServlet] (catalina-exec-11:) ===START=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=jso
n&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086899616
DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-11:) Async job-77 = [ 1219fffc-fcd4-481d-8393-bc57e052cc52 ] completed
DEBUG [cloud.api.ApiServlet] (catalina-exec-11:) ===END=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=json&
sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086899616
DEBUG [agent.manager.AgentManagerImpl] (AgentManager-Handler-2:) SeqA 3-22500: Processing Seq 3-22500: { Cmd , MgmtId: -1, via: 3, Ver: v1, Flags: 11, [{"com.cloud.ag
ent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":2,"_loadInfo":"{\n \"connections\": []\n}","wait":0}}] }
DEBUG [agent.manager.AgentManagerImpl] (AgentManager-Handler-2:) SeqA 3-22500: Sending Seq 3-22500: { Ans: , MgmtId: 90520735180840, via: 3, Ver: v1, Flags: 100010, [
{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}] }
DEBUG [cloud.api.ApiServlet] (catalina-exec-1:) ===START=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=json
&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086902611
DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-1:) Async job-77 = [ 1219fffc-fcd4-481d-8393-bc57e052cc52 ] completed
DEBUG [cloud.api.ApiServlet] (catalina-exec-1:) ===END=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=json&s
essionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086902611
DEBUG [cloud.api.ApiServlet] (catalina-exec-16:) ===START=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=jso
n&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086905632
DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-16:) Async job-77 = [ 1219fffc-fcd4-481d-8393-bc57e052cc52 ] completed
DEBUG [cloud.api.ApiServlet] (catalina-exec-16:) ===END=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=json&
sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086905632
DEBUG [cloud.api.ApiServlet] (catalina-exec-8:) ===START=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=json
&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086908630
DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-8:) Async job-77 = [ 1219fffc-fcd4-481d-8393-bc57e052cc52 ] completed
DEBUG [cloud.api.ApiServlet] (catalina-exec-8:) ===END=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=json&s
essionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086908630
DEBUG [agent.manager.AgentManagerImpl] (AgentManager-Handler-4:) SeqA 3-22501: Processing Seq 3-22501: { Cmd , MgmtId: -1, via: 3, Ver: v1, Flags: 11, [{"com.cloud.ag
ent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":2,"_loadInfo":"{\n \"connections\": []\n}","wait":0}}] }
DEBUG [agent.manager.AgentManagerImpl] (AgentManager-Handler-4:) SeqA 3-22501: Sending Seq 3-22501: { Ans: , MgmtId: 90520735180840, via: 3, Ver: v1, Flags: 100010, [
{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}] }
DEBUG [cloud.api.ApiServlet] (catalina-exec-18:) ===START=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=jso
n&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086911626
DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-18:) Async job-77 = [ 1219fffc-fcd4-481d-8393-bc57e052cc52 ] completed
DEBUG [cloud.api.ApiServlet] (catalina-exec-18:) ===END=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=json&
sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086911626
2014-03-06
toudsf
发件人："linuxbqj@gmail.com" <li...@gmail.com>
发送时间：2014-03-06 14:11
主题：Re: Re: 4.2.1版本中，vmha功能无效
收件人："users-cn"<us...@cloudstack.apache.org>
抄送：
你在关闭VM之后，系统有哪些日志？
在 2014年3月6日 下午2:08，toudsf <18...@163.com> 写道：
> 到后台看了一下。没有再启动的相关日志。
>
> 2014-03-06
>
>
>
> toudsf
>
>
>
> 发件人："linuxbqj@gmail.com" <li...@gmail.com>
> 发送时间：2014-03-06 12:23
> 主题：Re: 4.2.1版本中，vmha功能无效
> 收件人："users-cn"<us...@cloudstack.apache.org>
> 抄送：
>
> 有相关的日志吗？建议提供一些日志信息
>
> 在 2014年3月6日 上午10:44，toudsf <18...@163.com> 写道：
>> 虚拟化平台使用VMWARE
>> 1、设置了全局设置中的ha.tag
>> 2、设置了主机的host的主机标签
>> 3、在服务器中增加计算方案，启用高可用性和设置主机标签
>> 4、创建虚拟机选择HA的计算方案
>> 5、关闭虚拟机后，没有新的虚拟机启动起来。
>>
>> 以前测试过4.1是好的，请各位大侠指教！
>>
>> 2014-03-06
>>
>>
>>
>> toudsf
>
>
>
> --
> 白清杰 (Born Bai)
>
> 北京开源愿景信息技术有限公司
>
> Mail: linuxbqj@gmail.com
--
白清杰 (Born Bai)
北京开源愿景信息技术有限公司
Mail: linuxbqj@gmail.com
回复: Re: Re: 4.2.1版本中，vmha功能无效
Posted by toudsf <18...@163.com>.
刚才又看了一下，日志里面有一段【 Skip HA for VMware VM i-2-14-VM】，为什么会跳过HA了？
DEBUG [agent.transport.Request] (DirectAgent-160:) Seq 2-700518435: Sending { Cmd , MgmtId: 90520735180840, via: 2, Ver: v1, Flags: 100111, [{"com.cloud.agent.api.StopCommand":{"isProxy":false,"executeInSequence":true,"vmName":"i-2-14-VM","wait":0}}] }
DEBUG [agent.transport.Request] (DirectAgent-160:) Seq 2-700518435: Executing: { Cmd , MgmtId: 90520735180840, via: 2, Ver: v1, Flags: 100111, [{"com.cloud.agent.api.StopCommand":{"isProxy":false,"executeInSequence":true,"vmName":"i-2-14-VM","wait":0}}] }
DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-31:) Seq 2-700518435: Executing request
INFO [vmware.resource.VmwareResource] (DirectAgent-31:192.168.10.8) Executing resource StopCommand: {"isProxy":false,"executeInSequence":true,"vmName":"i-2-14-VM","wait":0}
DEBUG [vmware.mo.HostMO] (DirectAgent-31:192.168.10.8) find VM i-2-14-VM on host
INFO [vmware.mo.HostMO] (DirectAgent-31:192.168.10.8) VM i-2-14-VM not found in host cache
DEBUG [vmware.mo.HostMO] (DirectAgent-31:192.168.10.8) load VM cache on host
INFO [vmware.resource.VmwareResource] (DirectAgent-31:192.168.10.8) VM i-2-14-VM is already in stopped state
DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-31:) Seq 2-700518435: Response Received:
DEBUG [agent.transport.Request] (DirectAgent-31:) Seq 2-700518435: Processing: { Ans: , MgmtId: 90520735180840, via: 2, Ver: v1, Flags: 110, [{"com.cloud.agent.api.StopAnswer":{"result":true,"details":"VM i-2-14-VM is already in stopped state","wait":0}}] }
DEBUG [agent.manager.AgentAttache] (DirectAgent-31:) Seq 2-700518435: No more commands found
DEBUG [agent.transport.Request] (DirectAgent-160:) Seq 2-700518435: Received: { Ans: , MgmtId: 90520735180840, via: 2, Ver: v1, Flags: 110, { StopAnswer } }
DEBUG [cloud.vm.VirtualMachineManagerImpl] (DirectAgent-160:) VM[User|vmwareiso1] is stopped on the host. Proceeding to release resource held.
DEBUG [cloud.network.NetworkManagerImpl] (DirectAgent-160:) Changing active number of nics for network id=204 on -1
DEBUG [cloud.vm.VirtualMachineManagerImpl] (DirectAgent-160:) Successfully released network resources for the vm VM[User|vmwareiso1]
DEBUG [cloud.vm.VirtualMachineManagerImpl] (DirectAgent-160:) Successfully released storage resources for the vm VM[User|vmwareiso1]
DEBUG [cloud.network.NetworkModelImpl] (DirectAgent-160:) Service SecurityGroup is not supported in the network id=204
DEBUG [cloud.api.ApiServlet] (catalina-exec-19:) ===START=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086938629
DEBUG [cloud.network.NetworkModelImpl] (DirectAgent-160:) Service SecurityGroup is not supported in the network id=204
DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-19:) Async job-77 = [ 1219fffc-fcd4-481d-8393-bc57e052cc52 ] completed
DEBUG [cloud.api.ApiServlet] (catalina-exec-19:) ===END=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086938629
DEBUG [cloud.capacity.CapacityManagerImpl] (DirectAgent-160:) VM state transitted from :Stopping to Stopped with event: OperationSucceededvm's original host id: 2 new host id: null host id before state transition: 2
DEBUG [cloud.capacity.CapacityManagerImpl] (DirectAgent-160:) Hosts's actual total CPU: 47880 and CPU after applying overprovisioning: 47880
DEBUG [cloud.capacity.CapacityManagerImpl] (DirectAgent-160:) Hosts's actual total RAM: 12842033152 and RAM after applying overprovisioning: 12842033152
DEBUG [cloud.capacity.CapacityManagerImpl] (DirectAgent-160:) release cpu from host: 2, old used: 2500,reserved: 0, actual total: 47880, total with overprovisioning: 47880; new used: 2000,reserved:500; movedfromreserved: false,moveToReserveredtrue
DEBUG [cloud.capacity.CapacityManagerImpl] (DirectAgent-160:) release mem from host: 2, old used: 3623878656,reserved: 0, total: 12842033152; new used: 2550136832,reserved:1073741824; movedfromreserved: false,moveToReserveredtrue
INFO [cloud.ha.HighAvailabilityManagerImpl] (DirectAgent-160:) Skip HA for VMware VM i-2-14-VM
DEBUG [agent.transport.Request] (DirectAgent-160:) Seq 2-700518436: Sending { Cmd , MgmtId: 90520735180840, via: 2, Ver: v1, Flags: 100101, [{"com.cloud.agent.api.StopCommand":{"isProxy":false,"executeInSequence":true,"vmName":"i-2-14-VM","wait":0}}] }
DEBUG [agent.transport.Request] (DirectAgent-160:) Seq 2-700518436: Executing: { Cmd , MgmtId: 90520735180840, via: 2, Ver: v1, Flags: 100101, [{"com.cloud.agent.api.StopCommand":{"isProxy":false,"executeInSequence":true,"vmName":"i-2-14-VM","wait":0}}] }
DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-20:) Seq 2-700518436: Executing request
INFO [vmware.resource.VmwareResource] (DirectAgent-20:192.168.10.8) Executing resource StopCommand: {"isProxy":false,"executeInSequence":true,"vmName":"i-2-14-VM","wait":0}
DEBUG [vmware.mo.HostMO] (DirectAgent-20:192.168.10.8) find VM i-2-14-VM on host
INFO [vmware.mo.HostMO] (DirectAgent-20:192.168.10.8) VM i-2-14-VM not found in host cache
DEBUG [vmware.mo.HostMO] (DirectAgent-20:192.168.10.8) load VM cache on host
INFO [vmware.resource.VmwareResource] (DirectAgent-20:192.168.10.8) VM i-2-14-VM is already in stopped state
DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-20:) Seq 2-700518436: Response Received:
DEBUG [agent.transport.Request] (DirectAgent-20:) Seq 2-700518436: Processing: { Ans: , MgmtId: 90520735180840, via: 2, Ver: v1, Flags: 100, [{"com.cloud.agent.api.StopAnswer":{"result":true,"details":"VM i-2-14-VM is already in stopped state","wait":0}}] }
DEBUG [agent.manager.AgentAttache] (DirectAgent-20:) Seq 2-700518436: No more commands found
DEBUG [cloud.api.ApiServlet] (catalina-exec-9:) ===START=== 192.168.0.241 -- GET command=listVolumes&id=659d27b4-a71e-40c4-bd2d-3a71126b441f&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086939856
DEBUG [agent.manager.AgentManagerImpl] (AgentManager-Handler-7:) SeqA 3-22506: Processing Seq 3-22506: { Cmd , MgmtId: -1, via: 3, Ver: v1, Flags: 11, [{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":2,"_loadInfo":"{\n \"connections\": []\n}","wait":0}}] }
DEBUG [cloud.api.ApiServlet] (catalina-exec-9:) ===END=== 192.168.0.241 -- GET command=listVolumes&id=659d27b4-a71e-40c4-bd2d-3a71126b441f&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086939856
DEBUG [cloud.api.ApiServlet] (catalina-exec-3:) ===START=== 192.168.0.241 -- GET command=listTags&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&resourceId=659d27b4-a71e-40c4-bd2d-3a71126b441f&resourceType=Volume&listAll=true&_=1394086940031
DEBUG [cloud.api.ApiServlet] (catalina-exec-3:) ===END=== 192.168.0.241 -- GET command=listTags&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&resourceId=659d27b4-a71e-40c4-bd2d-3a71126b441f&resourceType=Volume&listAll=true&_=1394086940031
DEBUG [agent.manager.AgentManagerImpl] (AgentManager-Handler-7:) SeqA 3-22506: Sending Seq 3-22506: { Ans: , MgmtId: 90520735180840, via: 3, Ver: v1, Flags: 100010, [{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}] }
DEBUG [cloud.api.ApiServlet] (catalina-exec-2:) ===START=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086941628
DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-2:) Async job-77 = [ 1219fffc-fcd4-481d-8393-bc57e052cc52 ] completed
DEBUG [cloud.api.ApiServlet] (catalina-exec-2:) ===END=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086941628
DEBUG [cloud.api.ApiServlet] (catalina-exec-12:) ===START=== 192.168.0.241 -- GET command=listVolumes&id=659d27b4-a71e-40c4-bd2d-3a71126b441f&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086942409
DEBUG [cloud.api.ApiServlet] (catalina-exec-12:) ===END=== 192.168.0.241 -- GET command=listVolumes&id=659d27b4-a71e-40c4-bd2d-3a71126b441f&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086942409
DEBUG [cloud.api.ApiServlet] (catalina-exec-11:) ===START=== 192.168.0.241 -- GET command=listTags&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&resourceId=659d27b4-a71e-40c4-bd2d-3a71126b441f&resourceType=Volume&listAll=true&_=1394086942471
DEBUG [cloud.api.ApiServlet] (catalina-exec-11:) ===END=== 192.168.0.241 -- GET command=listTags&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&resourceId=659d27b4-a71e-40c4-bd2d-3a71126b441f&resourceType=Volume&listAll=true&_=1394086942471
DEBUG [cloud.api.ApiServlet] (catalina-exec-1:) ===START=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086944632
DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-1:) Async job-77 = [ 1219fffc-fcd4-481d-8393-bc57e052cc52 ] completed
DEBUG [cloud.api.ApiServlet] (catalina-exec-1:) ===END=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086944632
DEBUG [cloud.api.ApiServlet] (catalina-exec-16:) ===START=== 192.168.0.241 -- GET command=listVolumes&id=6f077b38-0fd4-40f8-9926-b2e91c2a388e&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086946685
DEBUG [cloud.api.ApiServlet] (catalina-exec-16:) ===END=== 192.168.0.241 -- GET command=listVolumes&id=6f077b38-0fd4-40f8-9926-b2e91c2a388e&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086946685
DEBUG [cloud.api.ApiServlet] (catalina-exec-8:) ===START=== 192.168.0.241 -- GET command=listTags&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&resourceId=6f077b38-0fd4-40f8-9926-b2e91c2a388e&resourceType=Volume&listAll=true&_=1394086946765
DEBUG [cloud.api.ApiServlet] (catalina-exec-8:) ===END=== 192.168.0.241 -- GET command=listTags&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&resourceId=6f077b38-0fd4-40f8-9926-b2e91c2a388e&resourceType=Volume&listAll=true&_=1394086946765
DEBUG [cloud.api.ApiServlet] (catalina-exec-18:) ===START=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086947631
DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-18:) Async job-77 = [ 1219fffc-fcd4-481d-8393-bc57e052cc52 ] completed
DEBUG [cloud.api.ApiServlet] (catalina-exec-18:) ===END=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086947631
DEBUG [cloud.server.StatsCollector] (StatsCollector-3:) HostStatsCollector is running...
DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-256:) Seq 1-1589709774: Executing request
DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-256:) Seq 1-1589709774: Response Received:
DEBUG [agent.transport.Request] (StatsCollector-3:) Seq 1-1589709774: Received: { Ans: , MgmtId: 90520735180840, via: 1, Ver: v1, Flags: 10, { GetHostStatsAnswer } }
DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-140:) Seq 2-700518437: Executing request
DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-140:) Seq 2-700518437: Response Received:
DEBUG [agent.transport.Request] (StatsCollector-3:) Seq 2-700518437: Received: { Ans: , MgmtId: 90520735180840, via: 2, Ver: v1, Flags: 10, { GetHostStatsAnswer } }
DEBUG [agent.manager.AgentManagerImpl] (AgentManager-Handler-13:) SeqA 3-22507: Processing Seq 3-22507: { Cmd , MgmtId: -1, via: 3, Ver: v1, Flags: 11, [{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":2,"_loadInfo":"{\n \"connections\": []\n}","wait":0}}] }
DEBUG [agent.manager.AgentManagerImpl] (AgentManager-Handler-13:) SeqA 3-22507: Sending Seq 3-22507: { Ans: , MgmtId: 90520735180840, via: 3, Ver: v1, Flags: 100010, [{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}] }
DEBUG [cloud.api.ApiServlet] (catalina-exec-7:) ===START=== 192.168.0.241 -- GET command=listVolumes&id=5ed14ef0-7f90-4555-aef4-76badafa351b&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086950276
DEBUG [cloud.api.ApiServlet] (catalina-exec-7:) ===END=== 192.168.0.241 -- GET command=listVolumes&id=5ed14ef0-7f90-4555-aef4-76badafa351b&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086950276
DEBUG [cloud.api.ApiServlet] (catalina-exec-21:) ===START=== 192.168.0.241 -- GET command=listTags&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&resourceId=5ed14ef0-7f90-4555-aef4-76badafa351b&resourceType=Volume&listAll=true&_=1394086950346
DEBUG [cloud.api.ApiServlet] (catalina-exec-21:) ===END=== 192.168.0.241 -- GET command=listTags&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&resourceId=5ed14ef0-7f90-4555-aef4-76badafa351b&resourceType=Volume&listAll=true&_=1394086950346
DEBUG [cloud.api.ApiServlet] (catalina-exec-17:) ===START=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086950627
DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-17:) Async job-77 = [ 1219fffc-fcd4-481d-8393-bc57e052cc52 ] completed
DEBUG [cloud.api.ApiServlet] (catalina-exec-17:) ===END=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086950627
DEBUG [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:) Zone 1 is ready to launch secondary storage VM
DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] (consoleproxy-1:) Zone 1 is ready to launch console proxy
DEBUG [cloud.server.StatsCollector] (StatsCollector-1:) VmStatsCollector is running...
DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-45:) Seq 1-1589709775: Executing request
DEBUG [vmware.mo.HostMO] (DirectAgent-45:192.168.10.7) find VM i-2-10-VM on host
INFO [vmware.mo.HostMO] (DirectAgent-45:192.168.10.7) VM i-2-10-VM not found in host cache
DEBUG [vmware.mo.HostMO] (DirectAgent-45:192.168.10.7) load VM cache on host
DEBUG [vmware.mo.HostMO] (DirectAgent-45:192.168.10.7) find VM i-2-17-VM on host
DEBUG [vmware.mo.HostMO] (DirectAgent-45:192.168.10.7) VM i-2-17-VM found in host cache
DEBUG [vmware.mo.HostMO] (DirectAgent-45:192.168.10.7) find VM i-2-7-VM on host
DEBUG [vmware.mo.HostMO] (DirectAgent-45:192.168.10.7) VM i-2-7-VM found in host cache
DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-45:) Seq 1-1589709775: Response Received:
DEBUG [agent.transport.Request] (StatsCollector-1:) Seq 1-1589709775: Received: { Ans: , MgmtId: 90520735180840, via: 1, Ver: v1, Flags: 10, { GetVmStatsAnswer } }
DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-160:) Seq 2-700518438: Executing request
DEBUG [vmware.mo.HostMO] (DirectAgent-160:192.168.10.8) find VM i-2-16-VM on host
INFO [vmware.mo.HostMO] (DirectAgent-160:192.168.10.8) VM i-2-16-VM not found in host cache
DEBUG [vmware.mo.HostMO] (DirectAgent-160:192.168.10.8) load VM cache on host
DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-160:) Seq 2-700518438: Response Received:
DEBUG [agent.transport.Request] (StatsCollector-1:) Seq 2-700518438: Received: { Ans: , MgmtId: 90520735180840, via: 2, Ver: v1, Flags: 10, { GetVmStatsAnswer } }
DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (RouterStatusMonitor-1:) Found 1 routers to update status.
DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (RouterStatusMonitor-1:) Found 0 networks to update RvR status.
DEBUG [cloud.api.ApiServlet] (catalina-exec-14:) ===START=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086953631
DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-14:) Async job-77 = [ 1219fffc-fcd4-481d-8393-bc57e052cc52 ] completed
DEBUG [cloud.api.ApiServlet] (catalina-exec-14:) ===END=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086953631
DEBUG [cloud.api.ApiServlet] (catalina-exec-6:) ===START=== 192.168.0.241 -- GET command=findStoragePoolsForMigration&id=5ed14ef0-7f90-4555-aef4-76badafa351b&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086954021
INFO [cloud.server.ManagementServerImpl] (catalina-exec-6:) Volume Vol[10|vm=7|ROOT] is attached to any running vm. Looking for storage pools in the cluster to which this volumes can be migrated.
DEBUG [storage.allocator.LocalStoragePoolAllocator] (catalina-exec-6:) LocalStoragePoolAllocator trying to find storage pool to fit the vm
DEBUG [storage.allocator.ClusterScopeStoragePoolAllocator] (catalina-exec-6:) ClusterScopeStoragePoolAllocator looking for storage pool
DEBUG [storage.allocator.ClusterScopeStoragePoolAllocator] (catalina-exec-6:) Looking for pools in dc: 1 pod:1 cluster:1
DEBUG [storage.allocator.AbstractStoragePoolAllocator] (catalina-exec-6:) Checking if storage pool is suitable, name: null ,poolId: 2
DEBUG [cloud.storage.StorageManagerImpl] (catalina-exec-6:) Checking pool 2 for storage, totalSize: 845791174656, usedBytes: 348392570880, usedPct: 0.4119132255331207, disable threshold: 0.85
DEBUG [cloud.storage.StorageManagerImpl] (catalina-exec-6:) Checking pool: 2 for volume allocation [Vol[10|vm=7|ROOT]], maxSize : 1691582349312, totalAllocatedSize : 5368709120, askingSize : 0, allocated disable threshold: 0.85
DEBUG [storage.allocator.AbstractStoragePoolAllocator] (catalina-exec-6:) Checking if storage pool is suitable, name: null ,poolId: 3
DEBUG [storage.allocator.AbstractStoragePoolAllocator] (catalina-exec-6:) StoragePool is in avoid set, skipping this pool
DEBUG [storage.allocator.ClusterScopeStoragePoolAllocator] (catalina-exec-6:) ClusterScopeStoragePoolAllocator returning 1 suitable storage pools
DEBUG [cloud.api.ApiServlet] (catalina-exec-6:) ===END=== 192.168.0.241 -- GET command=findStoragePoolsForMigration&id=5ed14ef0-7f90-4555-aef4-76badafa351b&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086954021
DEBUG [cloud.api.ApiServlet] (catalina-exec-24:) ===START=== 192.168.0.190 -- GET command=listVirtualMachines&response=json&sessionkey=ncY21jzJ0AUPl%2BUx0nDz8YiTZHQ%3D&listAll=true&page=1&pagesize=20&_=1394086962195
DEBUG [cloud.api.ApiServlet] (catalina-exec-24:) ===END=== 192.168.0.190 -- GET command=listVirtualMachines&response=json&sessionkey=ncY21jzJ0AUPl%2BUx0nDz8YiTZHQ%3D&listAll=true&page=1&pagesize=20&_=1394086962195
DEBUG [cloud.api.ApiServlet] (catalina-exec-13:) ===START=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086956632
DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-13:) Async job-77 = [ 1219fffc-fcd4-481d-8393-bc57e052cc52 ] completed
DEBUG [cloud.api.ApiServlet] (catalina-exec-13:) ===END=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086956632
DEBUG [host.dao.HostDaoImpl] (ClusteredAgentManager Timer:) Resetting hosts suitable for reconnect
DEBUG [host.dao.HostDaoImpl] (ClusteredAgentManager Timer:) Completed resetting hosts suitable for reconnect
DEBUG [host.dao.HostDaoImpl] (ClusteredAgentManager Timer:) Acquiring hosts for clusters already owned by this management server
DEBUG [host.dao.HostDaoImpl] (ClusteredAgentManager Timer:) Completed acquiring hosts for clusters already owned by this management server
DEBUG [host.dao.HostDaoImpl] (ClusteredAgentManager Timer:) Acquiring hosts for clusters not owned by any management server
DEBUG [host.dao.HostDaoImpl] (ClusteredAgentManager Timer:) Completed acquiring hosts for clusters not owned by any management server
DEBUG [cloud.api.ApiServlet] (catalina-exec-5:) ===START=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086959632
DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-5:) Async job-77 = [ 1219fffc-fcd4-481d-8393-bc57e052cc52 ] completed
DEBUG [cloud.api.ApiServlet] (catalina-exec-5:) ===END=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086959632
DEBUG [cloud.api.ApiServlet] (catalina-exec-10:) ===START=== 192.168.0.241 -- GET command=listVolumes&id=cfe65306-b6d1-457a-a8c3-9b23914db546&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086959917
DEBUG [cloud.api.ApiServlet] (catalina-exec-10:) ===END=== 192.168.0.241 -- GET command=listVolumes&id=cfe65306-b6d1-457a-a8c3-9b23914db546&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086959917
DEBUG [agent.manager.AgentManagerImpl] (AgentManager-Handler-11:) SeqA 3-22508: Processing Seq 3-22508: { Cmd , MgmtId: -1, via: 3, Ver: v1, Flags: 11, [{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":2,"_loadInfo":"{\n \"connections\": []\n}","wait":0}}] }
DEBUG [cloud.api.ApiServlet] (catalina-exec-23:) ===START=== 192.168.0.241 -- GET command=listTags&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&resourceId=cfe65306-b6d1-457a-a8c3-9b23914db546&resourceType=Volume&listAll=true&_=1394086959998
DEBUG [cloud.api.ApiServlet] (catalina-exec-23:) ===END=== 192.168.0.241 -- GET command=listTags&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&resourceId=cfe65306-b6d1-457a-a8c3-9b23914db546&resourceType=Volume&listAll=true&_=1394086959998
DEBUG [agent.manager.AgentManagerImpl] (AgentManager-Handler-11:) SeqA 3-22508: Sending Seq 3-22508: { Ans: , MgmtId: 90520735180840, via: 3, Ver: v1, Flags: 100010, [{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}] }
DEBUG [cloud.api.ApiServlet] (catalina-exec-22:) ===START=== 192.168.0.241 -- GET command=listVolumes&id=5ed14ef0-7f90-4555-aef4-76badafa351b&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086961474
DEBUG [cloud.api.ApiServlet] (catalina-exec-22:) ===END=== 192.168.0.241 -- GET command=listVolumes&id=5ed14ef0-7f90-4555-aef4-76badafa351b&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086961474
DEBUG [cloud.api.ApiServlet] (catalina-exec-4:) ===START=== 192.168.0.241 -- GET command=listTags&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&resourceId=5ed14ef0-7f90-4555-aef4-76badafa351b&resourceType=Volume&listAll=true&_=1394086961561
DEBUG [cloud.api.ApiServlet] (catalina-exec-4:) ===END=== 192.168.0.241 -- GET command=listTags&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&resourceId=5ed14ef0-7f90-4555-aef4-76badafa351b&resourceType=Volume&listAll=true&_=1394086961561
DEBUG [cloud.api.ApiServlet] (catalina-exec-20:) ===START=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086962637
DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-20:) Async job-77 = [ 1219fffc-fcd4-481d-8393-bc57e052cc52 ] completed
DEBUG [cloud.api.ApiServlet] (catalina-exec-20:) ===END=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086962637
DEBUG [cloud.api.ApiServlet] (catalina-exec-15:) ===START=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086965633
DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-15:) Async job-77 = [ 1219fffc-fcd4-481d-8393-bc57e052cc52 ] completed
DEBUG [cloud.api.ApiServlet] (catalina-exec-15:) ===END=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086965633
DEBUG [cloud.api.ApiServlet] (catalina-exec-25:) ===START=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086968629
DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-25:) Async job-77 = [ 1219fffc-fcd4-481d-8393-bc57e052cc52 ] completed
DEBUG [cloud.api.ApiServlet] (catalina-exec-25:) ===END=== 192.168.0.241 -- GET command=queryAsyncJobResult&jobId=1219fffc-fcd4-481d-8393-bc57e052cc52&response=json&sessionkey=Uwo37DqYhp0CFWuYJbFDjAZ935g%3D&_=1394086968629
DEBUG [agent.manager.AgentManagerImpl] (AgentManager-Handler-10:) SeqA 3-22509: Processing Seq 3-22509: { Cmd , MgmtId: -1, via: 3, Ver: v1, Flags: 11, [{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":2,"_loadInfo":"{\n \"connections\": []\n}","wait":0}}] }
DEBUG [agent.manager.AgentManagerImpl] (AgentManager-Handler-10:) SeqA 3-22509: Sending Seq 3-22509: { Ans: , MgmtId: 90520735180840, via: 3, Ver: v1, Flags: 100010, [{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}] }
2014-03-06
toudsf
发件人："linuxbqj@gmail.com" <li...@gmail.com>
发送时间：2014-03-06 14:11
主题：Re: Re: 4.2.1版本中，vmha功能无效
收件人："users-cn"<us...@cloudstack.apache.org>
抄送：
你在关闭VM之后，系统有哪些日志？
在 2014年3月6日 下午2:08，toudsf <18...@163.com> 写道：
> 到后台看了一下。没有再启动的相关日志。
>
> 2014-03-06
>
>
>
> toudsf
>
>
>
> 发件人："linuxbqj@gmail.com" <li...@gmail.com>
> 发送时间：2014-03-06 12:23
> 主题：Re: 4.2.1版本中，vmha功能无效
> 收件人："users-cn"<us...@cloudstack.apache.org>
> 抄送：
>
> 有相关的日志吗？建议提供一些日志信息
>
> 在 2014年3月6日 上午10:44，toudsf <18...@163.com> 写道：
>> 虚拟化平台使用VMWARE
>> 1、设置了全局设置中的ha.tag
>> 2、设置了主机的host的主机标签
>> 3、在服务器中增加计算方案，启用高可用性和设置主机标签
>> 4、创建虚拟机选择HA的计算方案
>> 5、关闭虚拟机后，没有新的虚拟机启动起来。
>>
>> 以前测试过4.1是好的，请各位大侠指教！
>>
>> 2014-03-06
>>
>>
>>
>> toudsf
>
>
>
> --
> 白清杰 (Born Bai)
>
> 北京开源愿景信息技术有限公司
>
> Mail: linuxbqj@gmail.com
--
白清杰 (Born Bai)
北京开源愿景信息技术有限公司
Mail: linuxbqj@gmail.com
Re: Re: Re: Re: 4.2.1版本中，vmha功能无效
Posted by Wei ZHOU <us...@gmail.com>.
我的理解是，vmware自身有针对vm的ha机制，所以cloudstack把这块交给vmware自己来做了。
在 2014年3月6日 上午8:09，toudsf <18...@163.com>写道：
> 我有2台物理服务器，另外一台1个虚拟机也没有。
> 我现在创建新的虚拟机也是可以的。应该不是容量问题。
>
> 2014-03-06
>
>
>
> toudsf
>
>
>
> 发件人："linuxbqj@gmail.com" <li...@gmail.com>
> 发送时间：2014-03-06 14:59
> 主题：Re: Re: Re: 4.2.1版本中，vmha功能无效
> 收件人："users-cn"<us...@cloudstack.apache.org>
> 抄送：
>
> DEBUG [cloud.capacity.CapacityManagerImpl] (DirectAgent-160:) VM state
> transitted from :Stopping to Stopped with event:
> OperationSucceededvm's original host id: 2 new host id: null host id
> before state transition: 2
> DEBUG [cloud.capacity.CapacityManagerImpl] (DirectAgent-160:) Hosts's
> actual total CPU: 47880 and CPU after applying overprovisioning: 47880
> DEBUG [cloud.capacity.CapacityManagerImpl] (DirectAgent-160:) Hosts's
> actual total RAM: 12842033152 and RAM after applying overprovisioning:
> 12842033152
>
> 你的VM的资源请求是不是超过了主机可以提供的范围？
>
> 在 2014年3月6日 下午2:55，toudsf <18...@163.com> 写道：
> >
> 刚才在/cloud-server/src/com/cloud/ha/HighAvailabilityManagerImpl.java文件中发现348-351行
> > 有以下语句
> >
> > if(vm.getHypervisorType() == HypervisorType.VMware) {
> > s_logger.info("Skip HA for VMware VM " +
> vm.getInstanceName());
> > return;
> > }
> >
> >
> > 难道现在不支持虚拟化平台时vmare的vm ha功能了？
> >
> >
> >
> > 2014-03-06
> >
> >
> >
> > toudsf
> >
> >
> >
> > 发件人："linuxbqj@gmail.com" <li...@gmail.com>
> > 发送时间：2014-03-06 14:11
> > 主题：Re: Re: 4.2.1版本中，vmha功能无效
> > 收件人："users-cn"<us...@cloudstack.apache.org>
> > 抄送：
> >
> > 你在关闭VM之后，系统有哪些日志？
> >
> >
> > 在 2014年3月6日 下午2:08，toudsf <18...@163.com> 写道：
> >> 到后台看了一下。没有再启动的相关日志。
> >>
> >> 2014-03-06
> >>
> >>
> >>
> >> toudsf
> >>
> >>
> >>
> >> 发件人："linuxbqj@gmail.com" <li...@gmail.com>
> >> 发送时间：2014-03-06 12:23
> >> 主题：Re: 4.2.1版本中，vmha功能无效
> >> 收件人："users-cn"<us...@cloudstack.apache.org>
> >> 抄送：
> >>
> >> 有相关的日志吗？建议提供一些日志信息
> >>
> >> 在 2014年3月6日 上午10:44，toudsf <18...@163.com> 写道：
> >>> 虚拟化平台使用VMWARE
> >>> 1、设置了全局设置中的ha.tag
> >>> 2、设置了主机的host的主机标签
> >>> 3、在服务器中增加计算方案，启用高可用性和设置主机标签
> >>> 4、创建虚拟机选择HA的计算方案
> >>> 5、关闭虚拟机后，没有新的虚拟机启动起来。
> >>>
> >>> 以前测试过4.1是好的，请各位大侠指教！
> >>>
> >>> 2014-03-06
> >>>
> >>>
> >>>
> >>> toudsf
> >>
> >>
> >>
> >> --
> >> 白清杰 (Born Bai)
> >>
> >> 北京开源愿景信息技术有限公司
> >>
> >> Mail: linuxbqj@gmail.com
> >
> >
> >
> > --
> > 白清杰 (Born Bai)
> >
> > 北京开源愿景信息技术有限公司
> >
> > Mail: linuxbqj@gmail.com
>
>
>
> --
> 白清杰 (Born Bai)
>
> 北京开源愿景信息技术有限公司
>
> Mail: linuxbqj@gmail.com
>
回复: Re: Re: Re: 4.2.1版本中，vmha功能无效
Posted by toudsf <18...@163.com>.
我有2台物理服务器，另外一台1个虚拟机也没有。
我现在创建新的虚拟机也是可以的。应该不是容量问题。
2014-03-06
toudsf
发件人："linuxbqj@gmail.com" <li...@gmail.com>
发送时间：2014-03-06 14:59
主题：Re: Re: Re: 4.2.1版本中，vmha功能无效
收件人："users-cn"<us...@cloudstack.apache.org>
抄送：
DEBUG [cloud.capacity.CapacityManagerImpl] (DirectAgent-160:) VM state
transitted from :Stopping to Stopped with event:
OperationSucceededvm's original host id: 2 new host id: null host id
before state transition: 2
DEBUG [cloud.capacity.CapacityManagerImpl] (DirectAgent-160:) Hosts's
actual total CPU: 47880 and CPU after applying overprovisioning: 47880
DEBUG [cloud.capacity.CapacityManagerImpl] (DirectAgent-160:) Hosts's
actual total RAM: 12842033152 and RAM after applying overprovisioning:
12842033152
你的VM的资源请求是不是超过了主机可以提供的范围？
在 2014年3月6日 下午2:55，toudsf <18...@163.com> 写道：
> 刚才在/cloud-server/src/com/cloud/ha/HighAvailabilityManagerImpl.java文件中发现348-351行
> 有以下语句
>
> if(vm.getHypervisorType() == HypervisorType.VMware) {
> s_logger.info("Skip HA for VMware VM " + vm.getInstanceName());
> return;
> }
>
>
> 难道现在不支持虚拟化平台时vmare的vm ha功能了？
>
>
>
> 2014-03-06
>
>
>
> toudsf
>
>
>
> 发件人："linuxbqj@gmail.com" <li...@gmail.com>
> 发送时间：2014-03-06 14:11
> 主题：Re: Re: 4.2.1版本中，vmha功能无效
> 收件人："users-cn"<us...@cloudstack.apache.org>
> 抄送：
>
> 你在关闭VM之后，系统有哪些日志？
>
>
> 在 2014年3月6日 下午2:08，toudsf <18...@163.com> 写道：
>> 到后台看了一下。没有再启动的相关日志。
>>
>> 2014-03-06
>>
>>
>>
>> toudsf
>>
>>
>>
>> 发件人："linuxbqj@gmail.com" <li...@gmail.com>
>> 发送时间：2014-03-06 12:23
>> 主题：Re: 4.2.1版本中，vmha功能无效
>> 收件人："users-cn"<us...@cloudstack.apache.org>
>> 抄送：
>>
>> 有相关的日志吗？建议提供一些日志信息
>>
>> 在 2014年3月6日 上午10:44，toudsf <18...@163.com> 写道：
>>> 虚拟化平台使用VMWARE
>>> 1、设置了全局设置中的ha.tag
>>> 2、设置了主机的host的主机标签
>>> 3、在服务器中增加计算方案，启用高可用性和设置主机标签
>>> 4、创建虚拟机选择HA的计算方案
>>> 5、关闭虚拟机后，没有新的虚拟机启动起来。
>>>
>>> 以前测试过4.1是好的，请各位大侠指教！
>>>
>>> 2014-03-06
>>>
>>>
>>>
>>> toudsf
>>
>>
>>
>> --
>> 白清杰 (Born Bai)
>>
>> 北京开源愿景信息技术有限公司
>>
>> Mail: linuxbqj@gmail.com
>
>
>
> --
> 白清杰 (Born Bai)
>
> 北京开源愿景信息技术有限公司
>
> Mail: linuxbqj@gmail.com
--
白清杰 (Born Bai)
北京开源愿景信息技术有限公司
Mail: linuxbqj@gmail.com
Re: Re: Re: 4.2.1版本中，vmha功能无效
Posted by "linuxbqj@gmail.com" <li...@gmail.com>.
DEBUG [cloud.capacity.CapacityManagerImpl] (DirectAgent-160:) VM state
transitted from :Stopping to Stopped with event:
OperationSucceededvm's original host id: 2 new host id: null host id
before state transition: 2
DEBUG [cloud.capacity.CapacityManagerImpl] (DirectAgent-160:) Hosts's
actual total CPU: 47880 and CPU after applying overprovisioning: 47880
DEBUG [cloud.capacity.CapacityManagerImpl] (DirectAgent-160:) Hosts's
actual total RAM: 12842033152 and RAM after applying overprovisioning:
12842033152
你的VM的资源请求是不是超过了主机可以提供的范围？
在 2014年3月6日 下午2:55，toudsf <18...@163.com> 写道：
> 刚才在/cloud-server/src/com/cloud/ha/HighAvailabilityManagerImpl.java文件中发现348-351行
> 有以下语句
>
> if(vm.getHypervisorType() == HypervisorType.VMware) {
> s_logger.info("Skip HA for VMware VM " + vm.getInstanceName());
> return;
> }
>
>
> 难道现在不支持虚拟化平台时vmare的vm ha功能了？
>
>
>
> 2014-03-06
>
>
>
> toudsf
>
>
>
> 发件人："linuxbqj@gmail.com" <li...@gmail.com>
> 发送时间：2014-03-06 14:11
> 主题：Re: Re: 4.2.1版本中，vmha功能无效
> 收件人："users-cn"<us...@cloudstack.apache.org>
> 抄送：
>
> 你在关闭VM之后，系统有哪些日志？
>
>
> 在 2014年3月6日 下午2:08，toudsf <18...@163.com> 写道：
>> 到后台看了一下。没有再启动的相关日志。
>>
>> 2014-03-06
>>
>>
>>
>> toudsf
>>
>>
>>
>> 发件人："linuxbqj@gmail.com" <li...@gmail.com>
>> 发送时间：2014-03-06 12:23
>> 主题：Re: 4.2.1版本中，vmha功能无效
>> 收件人："users-cn"<us...@cloudstack.apache.org>
>> 抄送：
>>
>> 有相关的日志吗？建议提供一些日志信息
>>
>> 在 2014年3月6日 上午10:44，toudsf <18...@163.com> 写道：
>>> 虚拟化平台使用VMWARE
>>> 1、设置了全局设置中的ha.tag
>>> 2、设置了主机的host的主机标签
>>> 3、在服务器中增加计算方案，启用高可用性和设置主机标签
>>> 4、创建虚拟机选择HA的计算方案
>>> 5、关闭虚拟机后，没有新的虚拟机启动起来。
>>>
>>> 以前测试过4.1是好的，请各位大侠指教！
>>>
>>> 2014-03-06
>>>
>>>
>>>
>>> toudsf
>>
>>
>>
>> --
>> 白清杰 (Born Bai)
>>
>> 北京开源愿景信息技术有限公司
>>
>> Mail: linuxbqj@gmail.com
>
>
>
> --
> 白清杰 (Born Bai)
>
> 北京开源愿景信息技术有限公司
>
> Mail: linuxbqj@gmail.com
--
白清杰 (Born Bai)
北京开源愿景信息技术有限公司
Mail: linuxbqj@gmail.com
回复: Re: Re: 4.2.1版本中，vmha功能无效
Posted by toudsf <18...@163.com>.
刚才在/cloud-server/src/com/cloud/ha/HighAvailabilityManagerImpl.java文件中发现348-351行
有以下语句
if(vm.getHypervisorType() == HypervisorType.VMware) {
s_logger.info("Skip HA for VMware VM " + vm.getInstanceName());
return;
}
难道现在不支持虚拟化平台时vmare的vm ha功能了？
2014-03-06
toudsf
发件人："linuxbqj@gmail.com" <li...@gmail.com>
发送时间：2014-03-06 14:11
主题：Re: Re: 4.2.1版本中，vmha功能无效
收件人："users-cn"<us...@cloudstack.apache.org>
抄送：
你在关闭VM之后，系统有哪些日志？
在 2014年3月6日 下午2:08，toudsf <18...@163.com> 写道：
> 到后台看了一下。没有再启动的相关日志。
>
> 2014-03-06
>
>
>
> toudsf
>
>
>
> 发件人："linuxbqj@gmail.com" <li...@gmail.com>
> 发送时间：2014-03-06 12:23
> 主题：Re: 4.2.1版本中，vmha功能无效
> 收件人："users-cn"<us...@cloudstack.apache.org>
> 抄送：
>
> 有相关的日志吗？建议提供一些日志信息
>
> 在 2014年3月6日 上午10:44，toudsf <18...@163.com> 写道：
>> 虚拟化平台使用VMWARE
>> 1、设置了全局设置中的ha.tag
>> 2、设置了主机的host的主机标签
>> 3、在服务器中增加计算方案，启用高可用性和设置主机标签
>> 4、创建虚拟机选择HA的计算方案
>> 5、关闭虚拟机后，没有新的虚拟机启动起来。
>>
>> 以前测试过4.1是好的，请各位大侠指教！
>>
>> 2014-03-06
>>
>>
>>
>> toudsf
>
>
>
> --
> 白清杰 (Born Bai)
>
> 北京开源愿景信息技术有限公司
>
> Mail: linuxbqj@gmail.com
--
白清杰 (Born Bai)
北京开源愿景信息技术有限公司
Mail: linuxbqj@gmail.com
Re: Re: 4.2.1版本中，vmha功能无效
Posted by "linuxbqj@gmail.com" <li...@gmail.com>.
你在关闭VM之后，系统有哪些日志？
在 2014年3月6日 下午2:08，toudsf <18...@163.com> 写道：
> 到后台看了一下。没有再启动的相关日志。
>
> 2014-03-06
>
>
>
> toudsf
>
>
>
> 发件人："linuxbqj@gmail.com" <li...@gmail.com>
> 发送时间：2014-03-06 12:23
> 主题：Re: 4.2.1版本中，vmha功能无效
> 收件人："users-cn"<us...@cloudstack.apache.org>
> 抄送：
>
> 有相关的日志吗？建议提供一些日志信息
>
> 在 2014年3月6日 上午10:44，toudsf <18...@163.com> 写道：
>> 虚拟化平台使用VMWARE
>> 1、设置了全局设置中的ha.tag
>> 2、设置了主机的host的主机标签
>> 3、在服务器中增加计算方案，启用高可用性和设置主机标签
>> 4、创建虚拟机选择HA的计算方案
>> 5、关闭虚拟机后，没有新的虚拟机启动起来。
>>
>> 以前测试过4.1是好的，请各位大侠指教！
>>
>> 2014-03-06
>>
>>
>>
>> toudsf
>
>
>
> --
> 白清杰 (Born Bai)
>
> 北京开源愿景信息技术有限公司
>
> Mail: linuxbqj@gmail.com
--
白清杰 (Born Bai)
北京开源愿景信息技术有限公司
Mail: linuxbqj@gmail.com