Return-Path: X-Original-To: apmail-cloudstack-users-archive@www.apache.org Delivered-To: apmail-cloudstack-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CD778118EC for ; Tue, 17 Jun 2014 06:25:37 +0000 (UTC) Received: (qmail 5072 invoked by uid 500); 17 Jun 2014 06:25:37 -0000 Delivered-To: apmail-cloudstack-users-archive@cloudstack.apache.org Received: (qmail 5020 invoked by uid 500); 17 Jun 2014 06:25:37 -0000 Mailing-List: contact users-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@cloudstack.apache.org Delivered-To: mailing list users@cloudstack.apache.org Received: (qmail 5008 invoked by uid 500); 17 Jun 2014 06:25:36 -0000 Delivered-To: apmail-incubator-cloudstack-users@incubator.apache.org Received: (qmail 5005 invoked by uid 99); 17 Jun 2014 06:25:36 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Jun 2014 06:25:36 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ivanoch@gmail.com designates 209.85.160.181 as permitted sender) Received: from [209.85.160.181] (HELO mail-yk0-f181.google.com) (209.85.160.181) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Jun 2014 06:25:31 +0000 Received: by mail-yk0-f181.google.com with SMTP id 9so4927317ykp.26 for ; Mon, 16 Jun 2014 23:25:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=hWAqrfP5skzoCZzO23t0wTmCSNVRHe9zZse/ZnhzELA=; b=b3cM2H4TKbYw8RLHc3wRwG9o25QiJGOrUrBiNL8f0Un6hmWQoYjuOdMz8UrDLQcISs K0pbLx84973wYE8pkICZX+4VPaOhwccL+GKoi+9NqGsf3kQYbg5sJ5dxKnwefqjSsxNs oJN2Oig/KIAJpHLlPd3ym+8Nnmqpd0+BKTQi+oza872tdQVhmtvbqzlqklJCW8+4pSDy ZUP/+H6Rcay/8F06Ad3NliIMbzRm6NUWHeHukb6H1SJJ0aJoTD7x5vubqmn2aQ2PSGkR fCkX/afmFVCGGm0yae3PuD186tdknX8kki/DMwYSBjHRBji0tvP+ukq3shtfx1vP+1HL LrpA== MIME-Version: 1.0 X-Received: by 10.236.192.73 with SMTP id h49mr40959196yhn.6.1402986310190; Mon, 16 Jun 2014 23:25:10 -0700 (PDT) Received: by 10.170.75.197 with HTTP; Mon, 16 Jun 2014 23:25:10 -0700 (PDT) In-Reply-To: References: Date: Tue, 17 Jun 2014 16:25:10 +1000 Message-ID: Subject: Re: Cloudstack 4.3 KVM CPU overprovisioning From: Ivan Rodriguez To: cloudstack-users@incubator.apache.org Content-Type: multipart/alternative; boundary=bcaec508f476a4cbf404fc0234f5 X-Virus-Checked: Checked by ClamAV on apache.org --bcaec508f476a4cbf404fc0234f5 Content-Type: text/plain; charset=UTF-8 More information from my previous post, On this particular blade I only have 9 vm's running Total CPU24 x 2.79 GHzCPU Utilized3.9%CPU Allocated for VMs 97%Memory Total126.02 GBMemory Allocated53.50 GB Memory Used36.74 MBNetwork Read35.99 GBNetwork Write [root@cs2-chas1-bl03 ~]# virsh list Id Name State ---------------------------------------------------- 9 i-8-70-VM running 11 i-8-75-VM running 14 r-93-VM running 15 i-8-72-VM running 16 r-95-VM running 17 i-3-84-VM running 18 i-3-73-VM running 19 i-3-91-VM running 28 i-4-110-VM running 29 i-9-112-VM running 30 i-3-128-VM running My service offering is # of CPU Cores4CPU (in MHz)2.00 GHz Where the number of CPU cores varies, I'm wondering if my service offering is incorrect because on the # of cores in my understanding is the number of vcpu's and the speed is lower than the real speed 2,000 Mhz Any ideas will be really appreciate it Below is the virs vcpuinfo VCPU: 0 CPU: 12 State: running CPU time: 11802.8s CPU Affinity: yyyyyyyyyyyyyyyyyyyyyyyy VCPU: 1 CPU: 12 State: running CPU time: 11317.7s CPU Affinity: yyyyyyyyyyyyyyyyyyyyyyyy VCPU: 0 CPU: 2 State: running CPU time: 115618.7s CPU Affinity: yyyyyyyyyyyyyyyyyyyyyyyy VCPU: 1 CPU: 2 State: running CPU time: 113330.9s CPU Affinity: yyyyyyyyyyyyyyyyyyyyyyyy VCPU: 0 CPU: 4 State: running CPU time: 3928.5s CPU Affinity: yyyyyyyyyyyyyyyyyyyyyyyy VCPU: 1 CPU: 0 State: running CPU time: 3459.6s CPU Affinity: yyyyyyyyyyyyyyyyyyyyyyyy VCPU: 2 CPU: 14 State: running CPU time: 3429.3s CPU Affinity: yyyyyyyyyyyyyyyyyyyyyyyy VCPU: 3 CPU: 12 State: running CPU time: 3808.8s CPU Affinity: yyyyyyyyyyyyyyyyyyyyyyyy VCPU: 4 CPU: 0 State: running CPU time: 3506.9s CPU Affinity: yyyyyyyyyyyyyyyyyyyyyyyy VCPU: 5 CPU: 2 State: running CPU time: 3695.5s CPU Affinity: yyyyyyyyyyyyyyyyyyyyyyyy VCPU: 6 CPU: 21 State: running CPU time: 4199.5s CPU Affinity: yyyyyyyyyyyyyyyyyyyyyyyy VCPU: 7 CPU: 0 State: running CPU time: 3633.2s CPU Affinity: yyyyyyyyyyyyyyyyyyyyyyyy VCPU: 0 CPU: 2 State: running CPU time: 650355.2s CPU Affinity: yyyyyyyyyyyyyyyyyyyyyyyy VCPU: 1 CPU: 14 State: running CPU time: 652099.4s CPU Affinity: yyyyyyyyyyyyyyyyyyyyyyyy VCPU: 2 CPU: 6 State: running CPU time: 644120.8s CPU Affinity: yyyyyyyyyyyyyyyyyyyyyyyy VCPU: 3 CPU: 1 State: running CPU time: 648950.4s CPU Affinity: yyyyyyyyyyyyyyyyyyyyyyyy VCPU: 0 CPU: 12 State: running CPU time: 10297.6s CPU Affinity: yyyyyyyyyyyyyyyyyyyyyyyy VCPU: 1 CPU: 0 State: running CPU time: 10297.3s CPU Affinity: yyyyyyyyyyyyyyyyyyyyyyyy VCPU: 0 CPU: 1 State: running CPU time: 1815.1s CPU Affinity: yyyyyyyyyyyyyyyyyyyyyyyy VCPU: 1 CPU: 1 State: running CPU time: 3389.8s CPU Affinity: yyyyyyyyyyyyyyyyyyyyyyyy VCPU: 0 CPU: 1 State: running CPU time: 409.7s CPU Affinity: yyyyyyyyyyyyyyyyyyyyyyyy VCPU: 1 CPU: 2 State: running CPU time: 463.9s CPU Affinity: yyyyyyyyyyyyyyyyyyyyyyyy VCPU: 2 CPU: 14 State: running CPU time: 602.6s CPU Affinity: yyyyyyyyyyyyyyyyyyyyyyyy VCPU: 3 CPU: 14 State: running CPU time: 429.9s CPU Affinity: yyyyyyyyyyyyyyyyyyyyyyyy VCPU: 0 CPU: 4 State: running CPU time: 10406.0s CPU Affinity: yyyyyyyyyyyyyyyyyyyyyyyy VCPU: 1 CPU: 2 State: running CPU time: 8263.1s CPU Affinity: yyyyyyyyyyyyyyyyyyyyyyyy VCPU: 2 CPU: 0 State: running CPU time: 8247.2s CPU Affinity: yyyyyyyyyyyyyyyyyyyyyyyy VCPU: 3 CPU: 0 State: running CPU time: 6616.0s CPU Affinity: yyyyyyyyyyyyyyyyyyyyyyyy VCPU: 0 CPU: 0 State: running CPU time: 33693.2s CPU Affinity: yyyyyyyyyyyyyyyyyyyyyyyy VCPU: 1 CPU: 16 State: running CPU time: 36008.6s CPU Affinity: yyyyyyyyyyyyyyyyyyyyyyyy VCPU: 2 CPU: 4 State: running CPU time: 36107.1s CPU Affinity: yyyyyyyyyyyyyyyyyyyyyyyy VCPU: 3 CPU: 16 State: running CPU time: 36210.2s CPU Affinity: yyyyyyyyyyyyyyyyyyyyyyyy On Tue, Jun 17, 2014 at 3:20 PM, Ivan Rodriguez wrote: > Dear Cloudstack users, > > Our current setup is using dell blades with 24 cpus on KVM, > currently we have 5 servers like that(120 cpus) , and 28 Vm's currently > running all of them linux centos > with virtio modules the majority of the vm's have 2 vcpus per VM > so that would be around 56 vcpus > > According to my Cloudstach Dashboard I'm already in 56 % usage of CPU's, > it seems > that CPU overprovision is not working on KVM, I've setup cloudstack in > global preferences to have a 100 guests per hosts as the limit if I my > understanding is correct > then I should be able to provision around 500 vms on those 120 cpu's if I > wanted to > using cpu overprovision. > > How can I confirm if CPU overprovision is working as far as I can see > cloudstack is detecting the right numper of cpu's per physical host > > > Total CPU24 x 2.79 GHzCPU Utilized3.9%CPU Allocated for VMs 97%Memory > Total126.02 GBMemory Allocated53.50 GB Memory Used36.74 MBNetwork Read35.99 > GBNetwork Write > Any help would be really appreciate it > > thanks > > > --bcaec508f476a4cbf404fc0234f5--