Return-Path: X-Original-To: apmail-cloudstack-issues-archive@www.apache.org Delivered-To: apmail-cloudstack-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id F107410890 for ; Tue, 8 Oct 2013 19:12:51 +0000 (UTC) Received: (qmail 71223 invoked by uid 500); 8 Oct 2013 19:12:48 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 71131 invoked by uid 500); 8 Oct 2013 19:12:46 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 71110 invoked by uid 500); 8 Oct 2013 19:12:45 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 71058 invoked by uid 99); 8 Oct 2013 19:12:45 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Oct 2013 19:12:45 +0000 Date: Tue, 8 Oct 2013 19:12:44 +0000 (UTC) From: "kelcey damage (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CLOUDSTACK-4826) System VMs fail to start MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CLOUDSTACK-4826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kelcey damage updated CLOUDSTACK-4826: -------------------------------------- Environment: CentOS 6.4 qemu-kvm-0.12.1.2-2.355.0.1.el6_4.9.x86_64 Cloudstack installed from RPM repo listed in docs AND: libvirt-client-0.10.2-18.el6_4.14.x86_64 libvirt-0.10.2-18.el6_4.14.x86_64 qemu-kvm-0.12.1.2-2.355.0.1.el6.centos.7.x86_64 CloudStack 4.2 upgraded based on 4.2 release guide steps was: CentOS 6.4 qemu-kvm-0.12.1.2-2.355.0.1.el6_4.9.x86_64 Cloudstack installed from RPM repo listed in docs > System VMs fail to start > ------------------------ > > Key: CLOUDSTACK-4826 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4826 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the default.) > Components: KVM > Affects Versions: 4.2.0 > Environment: CentOS 6.4 > qemu-kvm-0.12.1.2-2.355.0.1.el6_4.9.x86_64 > Cloudstack installed from RPM repo listed in docs > AND: > libvirt-client-0.10.2-18.el6_4.14.x86_64 > libvirt-0.10.2-18.el6_4.14.x86_64 > qemu-kvm-0.12.1.2-2.355.0.1.el6.centos.7.x86_64 > CloudStack 4.2 upgraded based on 4.2 release guide steps > Reporter: Dave Garbus > Priority: Critical > > After upgrading from 4.1.1 to 4.2, system VMs did not restart properly when running cloudstack-sysvmadm. Since we do not rely heavily on them at this point, I removed them figuring they would simply be recreated (this has worked in the past). > When CloudStack attempts to recreate the VMs, provisioning fails: > agent.log (IPs are obscured): > ======================== > Timed out: /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/patchviasocket.pl -n s-111-VM -p %template=domP%type=secstorage%host=XXXX.com%port=8250%name=s-111-VM%zone=1%pod=1%guid=s-111-VM%resource=com.cloud.storage.resource.PremiumSecondaryStorageResource%instance=SecStorage%sslcopy=true%role=templateProcessor%mtu=1500%eth2ip=XX.XX.XX.XX%eth2mask=255.255.255.0%gateway=XX.XX.XX.XX%public.network.device=eth2%eth0ip=169.254.0.47%eth0mask=255.255.0.0%eth1ip=XX.XX.XX.XX%eth1mask=255.255.255.0%mgmtcidr=XX.XX.XX.0/29%localgw=XX.XX.XX.XX%private.network.device=eth1%eth3ip=XX.XX.XX.XX%eth3mask=255.255.255.0%storageip=XX.XX.XX.XX%storagenetmask=255.255.255.0%storagegateway=XX.XX.XX.XX%internaldns1=XX.XX.XX.XX%internaldns2=XX.XX.XX.XX%dns1=XX.XX.XX.XX%dns2=XX.XX.XX.XX . Output is: > I gained access to the VM using the root password, and this is what I found: > root@systemvm:~# cat /etc/cloudstack-release > Cloudstack Release 3.0 Mon Feb 6 15:10:04 PST 2012 > root@systemvm:~# uname -a > Linux systemvm 2.6.32-5-686-bigmem #1 SMP Mon Jan 16 16:42:05 UTC 2012 i686 GNU/Linux > root@systemvm:~# /etc/init.d/cloud- > cloud-early-config cloud-passwd-srvr > root@systemvm:~# /etc/init.d/cloud-early-config start > Executing cloud-early-config...Executing cloud-early-config...Detected that we are running inside kvm guest.../dev/vport0p1 not loaded, perhaps guest kernel is too old....root@systemvm:~# > I have the system vm template systemvmtemplate-2013-06-12-master-kvm.qcow2.bz2, which is the latest (to my knowledge), on my secondary storage NFS mount, however, the SSVM is not able to be started, so I'm not sure this helps. > Please let me know if more information is needed. -- This message was sent by Atlassian JIRA (v6.1#6144)