Maurice, You should check the logs before this exception trace is logged, just follow the consoleproxy-1 thread to see what went wrong in the deployment process.
-Prachi -----Original Message----- From: Marcus Sorensen [mailto:shadow...@gmail.com] Sent: Wednesday, July 10, 2013 6:59 AM To: dev@cloudstack.apache.org Subject: Re: Error Message: Cloud Stack You can use NFS with a single server, but if you choose local storage instead, you need to go into the global options and tell system vms to use local storage. Parameter "system.vm.use.local.storage". I'm not sure that's the problem, but somewhere in the log it may lead you to why there is no server capacity, whether the agent isn't running (hence no hosts), or some other mismatch. On Tue, Jul 9, 2013 at 10:52 PM, Maurice Lawler <maurice.law...@me.com> wrote: > Thank you! > > This is being deployed on a single machine utilizing KVM as the hypervisor. > This is also my attempt at setting it up under Advanced Networking, with the > plans later to add additional servers; just wanted to toy with this server. > Should the storage not be NFS since its local? As there is an option at the > start of the set up. > > Marcus Sorensen <shadow...@gmail.com> wrote: > >>InsufficientServerCapacity = You didn't have enough resources to >>launch the VM. It can be due to out of memory on hosts, out of CPU, or >>not able to find storage. Sometimes this is just due to a mismatch in >>service offerings. For example, often in a dev environment you just >>set up a local primary storage, but all service offerings reference >>shared primary storage, therefore the system can not find a place >>matching it's requirements on which to run the VMs. >> >>On Tue, Jul 9, 2013 at 10:26 PM, Maurice Lawler <maurice.law...@me.com> wrote: >>> I have started my cloudstack in advanced mode, however, during the >>> process I am seeing this: >>> >>> >>> >>> 2013-07-09 23:23:55,920 DEBUG [cloud.capacity.CapacityManagerImpl] >>> (consoleproxy-1:null) release cpu from host: 1, old used: >>> 500,reserved: 0, actual total: 36256, total with overprovisioning: 36256; >>> new used: >>> 0,reserved:0; movedfromreserved: false,moveToReserveredfalse >>> 2013-07-09 23:23:55,920 DEBUG [cloud.capacity.CapacityManagerImpl] >>> (consoleproxy-1:null) release mem from host: 1, old used: >>> 1073741824,reserved: 0, total: 25186906112; new used: 0,reserved:0; >>> movedfromreserved: false,moveToReserveredfalse >>> 2013-07-09 23:23:55,922 WARN >>> [cloud.consoleproxy.ConsoleProxyManagerImpl] >>> (consoleproxy-1:null) Exception while trying to start console proxy >>> com.cloud.exception.InsufficientServerCapacityException: Unable to >>> create a deployment for VM[ConsoleProxy|v-2-VM]Scope=interface >>> com.cloud.dc.DataCenter; id=1 >>> at >>> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineMa >>> nagerImpl.java:728) >>> at >>> com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerIm >>> pl.java:471) >>> at >>> com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerIm >>> pl.java:464) >>> at >>> com.cloud.consoleproxy.ConsoleProxyManagerImpl.startProxy(ConsolePro >>> xyManagerImpl.java:632) >>> at >>> com.cloud.consoleproxy.ConsoleProxyManagerImpl.allocCapacity(Console >>> ProxyManagerImpl.java:1166) >>> at >>> com.cloud.consoleproxy.ConsoleProxyManagerImpl.expandPool(ConsolePro >>> xyManagerImpl.java:1989) >>> at >>> com.cloud.consoleproxy.ConsoleProxyManagerImpl.expandPool(ConsolePro >>> xyManagerImpl.java:175) at >>> com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:1 >>> 11) at >>> com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java >>> :33) at >>> com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.jav >>> a:81) at >>> com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:72) >>> at >>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:4 >>> 71) >>> at >>> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.jav >>> a: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(ThreadPoolExecuto >>> r.java:615) at java.lang.Thread.run(Thread.java:679) >>> 2013-07-09 23:23:58,720 DEBUG >>> [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) >>> Zone 1 is ready to launch secondary storage VM >>> >>> >>> What does this mean? >>> >>> - Maurice
