So I checked for similar issues on the mailing list, and found that someone was told to reinstall libvirt, and I've done so, but that didn't help.
Here's my scenario. I've decided to go with a flat network as I'm testing Cloudstack, and don't have the VLAN infrastructure in place. I have a bridged network cloudbr0 on my Hypervisor's NIC card with the IP address of 192.168.100.240 that I'm trying to add as a host. My Management server and Hypervisor can reach each other over the network. I've got the zones and such all set up, but when I go to add a KVM host, it fails. Here's what the log shows on the Management console: 2013-02-20 13:38:00,979 DEBUG [cloud.api.ApiServlet] (catalina-exec-7:null) ===START=== 192.168.100.108 -- GET command=addHost&zoneid=e446d507-630e-4f8a-9aca-da34bf35d537&podid=0a4fefe4-5f78-4da8-99af-1c9049de49b0&clusterid=97a0779b-1820-42f1-a0ed-7afdc3cb195b&hypervisor=KVM&clustertype=CloudManaged&hosttags=&username=root&url=http%3A%2F%2F192.168.100.240&response=json&sessionkey=BQHnR%2BbzdBBgrzXKV3ODzVopzFI%3D&_=1361385474368 2013-02-20 13:38:00,988 INFO [cloud.resource.ResourceManagerImpl] (catalina-exec-7:null) Trying to add a new host at http://192.168.100.240 in data center 2 2013-02-20 13:38:01,111 DEBUG [utils.ssh.SSHCmdHelper] (catalina-exec-7:null) Executing cmd: lsmod|grep kvm 2013-02-20 13:38:02,126 DEBUG [utils.ssh.SSHCmdHelper] (catalina-exec-7:null) lsmod|grep kvm output:kvm_intel 52762 0 kvm 312405 1 kvm_intel 2013-02-20 13:38:03,133 DEBUG [utils.ssh.SSHCmdHelper] (catalina-exec-7:null) Executing cmd: cloud-setup-agent -m 192.168.100.237 -z 2 -p 2 -c 2 -g f4558f1d-a1f4-33c7-9eac-1ceca8892676 -a --pubNic=cloudbr0 --prvNic=cloudbr0 --guestNic=cloudbr0 2013-02-20 13:38:07,049 DEBUG [agent.transport.Request] (AgentManager-Handler-2:null) Seq -1--1: Processing the first command { Cmd , MgmtId: -1, via: -1, Ver: v1, Flags: 111, [{"ShutdownCommand":{"reason":"sig.kill","wait":0}}] } 2013-02-20 13:38:07,049 WARN [agent.manager.AgentManagerImpl] (AgentManager-Handler-2:null) Throwing away a request because it came through as the first command on a connect: Seq -1--1: { Cmd , MgmtId: -1, via: -1, Ver: v1, Flags: 111, [{"ShutdownCommand":{"reason":"sig.kill","wait":0}}] } 2013-02-20 13:38:08,034 INFO [agent.manager.AgentManagerImpl] (AgentManager-Handler-3:null) Connection from /192.168.100.240 closed but no cleanup was done. 2013-02-20 13:43:43,962 DEBUG [kvm.discoverer.KvmServerDiscoverer] (catalina-exec-7:null) Timeout, to wait for the host connecting to mgt svr, assuming it is failed 2013-02-20 13:43:43,965 WARN [cloud.resource.ResourceManagerImpl] (catalina-exec-7:null) Unable to find the server resources at http://192.168.100.240 2013-02-20 13:43:43,967 WARN [api.commands.AddHostCmd] (catalina-exec-7:null) Exception: com.cloud.exception.DiscoveryException: Unable to add the host at com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:737) at com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:544) at com.cloud.api.commands.AddHostCmd.execute(AddHostCmd.java:140) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:138) at com.cloud.api.ApiServer.queueCommand(ApiServer.java:544) at com.cloud.api.ApiServer.handleRequest(ApiServer.java:423) at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:312) at com.cloud.api.ApiServlet.doGet(ApiServlet.java:64) at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) at org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889) at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2268) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) 2013-02-20 13:43:43,968 WARN [cloud.api.ApiDispatcher] (catalina-exec-7:null) class com.cloud.api.ServerApiException : Unable to add the host 2013-02-20 13:43:43,969 DEBUG [cloud.api.ApiServlet] (catalina-exec-7:null) ===END=== 192.168.100.108 -- GET command=addHost&zoneid=e446d507-630e-4f8a-9aca-da34bf35d537&podid=0a4fefe4-5f78-4da8-99af-1c9049de49b0&clusterid=97a0779b-1820-42f1-a0ed-7afdc3cb195b&hypervisor=KVM&clustertype=CloudManaged&hosttags=&username=root&url=http%3A%2F%2F192.168.100.240&response=json&sessionkey=BQHnR%2BbzdBBgrzXKV3ODzVopzFI%3D&_=1361385474368 And here's what the host running the KVM hypervisor is reporting, each time I try to add a host: Feb 20 13:38:04 H2L-VS2 CGRE[1497]: Stopped CGroup Rules Engine Daemon at Wed Feb 20 13:38:04 2013 Feb 20 13:38:05 H2L-VS2 CGRE[3640]: Started the CGroup Rules Engine Daemon. Feb 20 13:38:05 H2L-VS2 rpcbind: rpcbind terminating on signal. Restart with "rpcbind -w" Feb 20 13:38:05 H2L-VS2 kernel: lo: Disabled Privacy Extensions Feb 20 13:38:06 H2L-VS2 kernel: nfsd: last server has exited, flushing export cache Feb 20 13:38:06 H2L-VS2 rpc.mountd[1881]: Caught signal 15, un-registering and exiting. Feb 20 13:38:06 H2L-VS2 rpc.mountd[4126]: Version 1.2.3 starting Feb 20 13:38:06 H2L-VS2 kernel: NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory Feb 20 13:38:06 H2L-VS2 kernel: NFSD: starting 90-second grace period It looks like there's a signal being terminated, but I have no idea why? Any thoughts? Thanks, Jeremy
