• Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 4.2.0
    • Fix Version/s: 4.3.0
    • Component/s: Doc, KVM
    • Security Level: Public (Anyone can view this level - this is the default.)
    • Labels:
    • Environment:


      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.




            • Assignee:
              kishan Kishan Kavala
              dgarbus Dave Garbus
            • Votes:
              0 Vote for this issue
              6 Start watching this issue


              • Created: