2. juli 2014 10:07 skrev "Elliot Berg" <elliot.b...@avcosystems.com> følgende: > > Hi, > > I've been putting together a cloudstack set-up for experimentation purposes - right now we're just trying to compare different platforms for private cloud infrastructure before we start getting too in depth with any of them. > > I've added the cloudstack 4.2 apt repository, and I'm running on Ubuntu 12.04 LTS, and I believe I've followed all the installation guides correctly at the various stages. > > We've set up a management server, which is also an NFS server, however we're interested in using local storage for the majority of things, and have also set up a single KVM host which I believe is all configured correctly to use local storage. If I look at the dashboard, I'm told I have more than enough resource in every section to create an instance the size I want to - which is a small offering I've created with just 1.0GHz and 1GB of RAM, with local storage. The host's not very powerful, but according to the dashboard I am using 1.50GHz/5.87GHz, 1.38GB/7.80GB, 3.55GB/285.95GB Secondary Storage, 1.03GB/450.99GB Local Storage and 0.00KB/571.90GB Primary Storage (I'm assuming that's meant to be a combination of the NFS server's primary storage offering and the local storage on the host, though the numbers don't quite make sense at first glance). > > However, when I try to add an instance, I receive an InsufficientServerCapacityException and I'm struggling to work out why. I can't add an instance using a small shared storage offering either, but if I'm not mistaken that's expected because the zone and host are configured to use local storage. The only thing I can think of is that the local storage isn't properly configured, but when I've looked it seems to be. > > Any pointers for how I can further diagnose this would be great - thanks in advance! >
Something that occasionally bites me when deploying on old or deprecated hardware is that the CPU cores have a lower CPU frequency than the compute offering. For instance the offering might be 2GHz while the actual hardware core only is 1.99GHz. Also check the logs for pointers, put them on pastebin if you want help to interpret them. Erik
