cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "kelcey damage (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-4826) System VMs fail to start
Date Tue, 08 Oct 2013 18:28:48 GMT


kelcey damage commented on CLOUDSTACK-4826:

still no success, on the host I get the following errors trying to create a new system VM:

2013-10-08 11:09:27,767 WARN  [kvm.resource.LibvirtComputingResource] (Script-1:null) Interrupting
2013-10-08 11:09:27,768 WARN  [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-4:null)
Timed out: /usr/share/cloudstack-common/
scripts/vm/hypervisor/kvm/ -n s-138-VM -p %template=domP%type=secstorage%host=
.  Output is:

2013-10-08 11:10:24,032 WARN  [cloud.agent.Agent] (agentRequest-Handler-1:null) Caught:
        at java.util.concurrent.ThreadPoolExecutor.runWorker(
        at java.util.concurrent.ThreadPoolExecutor$

> System VMs fail to start
> ------------------------
>                 Key: CLOUDSTACK-4826
>                 URL:
>             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-
> Cloudstack installed from RPM repo listed in docs
>            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/ -n
s-111-VM -p
.  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

View raw message