Return-Path: X-Original-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 12623E7C1 for ; Thu, 17 Jan 2013 02:50:14 +0000 (UTC) Received: (qmail 3880 invoked by uid 500); 17 Jan 2013 02:50:13 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 3839 invoked by uid 500); 17 Jan 2013 02:50:13 -0000 Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-dev@incubator.apache.org Delivered-To: mailing list cloudstack-dev@incubator.apache.org Received: (qmail 3812 invoked by uid 99); 17 Jan 2013 02:50:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Jan 2013 02:50:12 +0000 Date: Thu, 17 Jan 2013 02:50:12 +0000 (UTC) From: "Sangeetha Hariharan (JIRA)" To: cloudstack-dev@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CLOUDSTACK-995) Not able to add the KVM host. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Sangeetha Hariharan created CLOUDSTACK-995: ---------------------------------------------- Summary: Not able to add the KVM host. Key: CLOUDSTACK-995 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-995 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the defa= ult.) Components: Management Server Affects Versions: 4.1.0 Environment: Build from network-refactor branch. Reporter: Sangeetha Hariharan Priority: Critical Fix For: 4.1.0 Set up: Installed management server. Tried to configure an advanced zone with KVM hypervisor - Centos 6.2. I am NOT able to add the KVM host successfully. =20 I get the following error in management server logs : =20 2013-01-16 21:02:32,794 INFO [cloud.resource.ResourceManagerImpl] (catalin= a-exec-7:null) Trying to add a new host at http://10.223.59.4 in data cente= r 1 2013-01-16 21:02:33,038 DEBUG [utils.ssh.SSHCmdHelper] (catalina-exec-7:nul= l) Executing cmd: lsmod|grep kvm 2013-01-16 21:02:34,168 DEBUG [utils.ssh.SSHCmdHelper] (catalina-exec-7:nul= l) lsmod|grep kvm output:kvm_intel 50380 0 kvm 305081 1 kvm_intel =20 =E2=80=A6.. 2013-01-16 21:02:35,176 DEBUG [utils.ssh.SSHCmdHelper] (catalina-exec-7:nul= l) Executing cmd: cloud-setup-agent -m 10.223.59.3 -z 1 -p 1 -c 1 -g 01481= 220-7c8d-3d22-aa72-80d909038f98 -a --pubNic=3Dcloudbr0 --prvNic=3Dcloudbr0 = --guestNic=3Dcloudbr0 2013-01-16 21:02:58,319 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] = (consoleproxy-1:null) Skip capacity scan due to there is no Primary Storage= UPintenance mode 2013-01-16 21:02:58,726 DEBUG [network.router.VirtualNetworkApplianceManage= rImpl] (RouterStatusMonitor-1:null) Found 0 routers. 2013-01-16 21:03:13,078 DEBUG [cloud.server.StatsCollector] (StatsCollector= -2:null) HostStatsCollector is running... 2013-01-16 21:03:13,078 DEBUG [cloud.server.StatsCollector] (StatsCollector= -1:null) VmStatsCollector is running... 2013-01-16 21:03:13,175 DEBUG [cloud.server.StatsCollector] (StatsCollector= -2:null) StorageCollector is running... 2013-01-16 21:03:28,319 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] = (consoleproxy-1:null) Skip capacity scan due to there is no Primary Storage= UPintenance mode 2013-01-16 21:03:28,727 DEBUG [network.router.VirtualNetworkApplianceManage= rImpl] (RouterStatusMonitor-1:null) Found 0 routers. 2013-01-16 21:03:41,434 DEBUG [utils.ssh.SSHCmdHelper] (catalina-exec-7:nul= l) cloud-setup-agent -m 10.223.59.3 -z 1 -p 1 -c 1 -g 01481220-7c8d-3d22-a= a72-80d909038f98 -a --pubNic=3Dcloudbr0 --prvNic=3Dcloudbr0 --guestNic=3Dcl= oudbr0 output:[Failed] ibvirt ... bvirt Try to restore your system: Restore SElinux ... =20 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrato= rs For more information on JIRA, see: http://www.atlassian.com/software/jira