In addition to my previous email, we configured a new management server only with KVM and its working no major dramas, do we need a separate primary storage/secondary storage/ console vm and storage vm per hypervisor ?
Thanks On Thu, Apr 10, 2014 at 11:33 AM, Ivan Rodriguez <[email protected]> wrote: > > Dear Cloudstack Users, > > We are having a problem with our cloudstack 4.3, > we can't provision vms on kvm hypervisor, our configuration > has 1 Xen cluster which is working fine and 1 KVM cluster > which is not working, cloudstack can see the kvm hosts > and as far as the status goes they are online. > > We tried to install the template for kvm 4.3 but there 3 different > versions out there > > systemvmtemplate-2014-04-09-master-kvm.qcow2.bz2 > systemvm64template-2014-01-14-master-kvm.qcow2.bz2 > systemvmtemplate-2013-06-12-master-kvm.qcow2.bz2 > > We are trying with the 2014, also when you have 2 clusters should we have > 4 system vms ??? > > > However as soon as we try to provision something cloudstack send the > following error: > > > > > 2014-04-10 11:12:44,042 WARN [c.c.s.s.SecondaryStorageManagerImpl] > (secstorage-1:ctx-754a9ede) Exception while trying to sta > rt secondary storage vm > com.cloud.exception.InsufficientServerCapacityException: Unable to create > a deployment for VM[SecondaryStorageVm|s-21-VM]Scope=interface > com.cloud.dc.DataCenter; id=1 > at > com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:921) > at > com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:761) > at > com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:745) > at > com.cloud.storage.secondary.SecondaryStorageManagerImpl.startSecStorageVm(SecondaryStorageManagerImpl.java:261) > at > com.cloud.storage.secondary.SecondaryStorageManagerImpl.allocCapacity(SecondaryStorageManagerImpl.java:694) > at > com.cloud.storage.secondary.SecondaryStorageManagerImpl.expandPool(SecondaryStorageManagerImpl.java:1278) > at > com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:123) > at > com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:50) > at > com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:111) > at > com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:35) > at > com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:88) > at > com.cloud.vm.SystemVmLoadScanner$1.runInContext(SystemVmLoadScanner.java:79) > at > org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) > at > org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at > java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351) > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267) > 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:701) > >
