我怎么看着好像是主机不可用的错误， 看一下HOST状态是不是up,另外确认一下主机的网络设置。
如果有两个网卡，那么需要一个对应为管理网络，一个对应Guest（需要配置【/etc/sysconfig/network-scripts/】下面的网络）。 或者试试【service network restart】看有没有错误。 下面是我这儿的计算节点（KVM）的设置： 1. [root@cs-share1 agent]# cat agent.properties #Storage #Mon Jan 19 11:09:04 CST 2015 guest.network.device=cloudguestbr workers=5 private.network.device=cloudbr0 port=8250 resource=com.cloud.hypervisor.kvm.resource.LibvirtComputingResource pod=1 zone=1 guid=e6fa3bcd-d869-3bef-b219-d47f6c886add hypervisor.type=kvm cluster=1 public.network.device=cloudguestbr local.storage.uuid=ed23496f-1039-4236-8dca-7b5106701edd domr.scripts.dir=scripts/network/domr/kvm host=192.168.10.2 LibvirtComputingResource.id=2 2.网卡（网上em1为接管理网络，网卡em2接Guest网络 ） [root@cs-share1 network-scripts]# cat ifcfg-cloudbr0 DEVICE=cloudbr0 HWADDR=C8:1F:66:C6:8F:37 NM_CONTROLLED=no ONBOOT=yes IPADDR=192.168.10.11 NETMASK=255.255.252.0 GATEWAY=192.168.10.1 DNS1=192.168.0.1 DNS2= TYPE=Bridge [root@cs-share1 network-scripts]# [root@cs-share1 network-scripts]# cat ifcfg-cloudguestbr DEVICE=cloudguestbr HWADDR=C8:1F:66:C6:8F:36 NM_CONTROLLED=no ONBOOT=yes IPADDR=192.168.0.85 NETMASK=255.255.252.0 GATEWAY=192.168.0.1 DNS1=192.168.0.1 TYPE=Bridge [root@cs-share1 network-scripts]# cat ifcfg-em1 DEVICE=em1 HWADDR=C8:1F:66:C6:8F:36 TYPE=Ethernet UUID=19b1057b-f850-43b4-8821-2abc27c7b350 ONBOOT=yes NM_CONTROLLED=no BOOTPROTO=none IPADDR=192.168.0.85 NETMASK=255.255.252.0 GATEWAY=192.168.0.1 DNS1=192.168.0.1 BRIDGE=cloudguestbr [root@cs-share1 network-scripts]# cat ifcfg-em2 DEVICE=em2 HWADDR=C8:1F:66:C6:8F:37 TYPE=Ethernet UUID=4cffc5da-4cd4-4d5c-b5ad-4818b442e215 ONBOOT=yes NM_CONTROLLED=no BOOTPROTO=none IPADDR=192.168.10.11 NETMASK=255.255.255.0 GATEWAY=192.168.10.1 DNS1=192.168.10.1 BRIDGE=cloudbr0 以上， >-----Original Message----- >From: 朱益萍 [mailto:874413...@qq.com] >Sent: Monday, February 02, 2015 4:06 PM >To: cloudstack >Subject: SSVM一直无法启动 > >添加二级存储的时候SSVM一直无法正常启动，具体日志如下： 2015-02-02 >15:39:01,181 ERROR [c.c.v.VmWorkJobHandlerProxy] >(Work-Job-Executor-4 :ctx-18583a6e job-2/job-13 ctx-b0a308f5) >Invocation exception, caused by: com.cl >oud.exception.AgentUnavailableException: Resource [Host:1] is >unreachable: Host >1: Unable to start instance due to Unable to acquire lock on >VMTemplateStoragePo >ol: 2 >2015-02-02 15:39:01,181 INFO [c.c.v.VmWorkJobHandlerProxy] >(Work-Job-Executor-4 :ctx-18583a6e job-2/job-13 ctx-b0a308f5) Rethrow >exception com.cloud.exception.A >gentUnavailableException: Resource [Host:1] is unreachable: Host 1: >Unable to st art instance due to Unable to acquire lock on >VMTemplateStoragePool: 2 >2015-02-02 15:39:01,182 DEBUG [c.c.v.VmWorkJobDispatcher] >(Work-Job-Executor-4:c tx-18583a6e job-2/job-13) Done with run of VM work >job: com.cloud.vm.VmWorkStart for VM 2, job origin: 2 >2015-02-02 15:39:01,182 ERROR [c.c.v.VmWorkJobDispatcher] >(Work-Job-Executor-4:c tx-18583a6e job-2/job-13) Unable to complete >AsyncJobVO {id:13, userId: 1, accou >ntId: 1, instanceType: null, instanceId: null, cmd: >com.cloud.vm.VmWorkStart, cm >dInfo: >rO0ABXNyABhjb20uY2xvdWQudm0uVm1Xb3JrU3RhcnR9cMGsvxz73gIAC0oABGRjSWRMA >AZhd >m9pZHN0ADBMY29tL2Nsb3VkL2RlcGxveS9EZXBsb3ltZW50UGxhbm5lciRFeGNsdWRlTG >lzdDtMAAljb >HVzdGVySWR0ABBMamF2YS9sYW5nL0xvbmc7TAAGaG9zdElkcQB-AAJMAAtqb3VybmFsTm >FtZXQAEkxqY >XZhL2xhbmcvU3RyaW5nO0wAEXBoeXNpY2FsTmV0d29ya0lkcQB-AAJMAAdwbGFubmVycQ >B-AANMAAVwb >2RJZHEAfgACTAAGcG9vbElkcQB-AAJMAAlyYXdQYXJhbXN0AA9MamF2YS91dGlsL01hcD >tMAA1yZXNlc >nZhdGlvbklkcQB-AAN4cgATY29tLmNsb3VkLnZtLlZtV29ya5-ZtlbwJWdrAgAESgAJYW >Njb3VudElkS Disclaimer: The contents of this e-mail, and its attachments, if any, are confidential and may be protected by law against any unauthorized use. If you have received this e-mail by mistake or have reason to believe that you are not the intended recipient, please notify the sender by reply e-mail as soon as possible and delete it from your computer system immediately thereafter. If you are not the intended recipient, you must not copy this e-mail or attachment or disclose the contents to any other person. While we have made every effort to keep our network virus free, we take no responsibility for any computer virus which might be transferred by way of this e-mail.
