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 23FD010629 for ; Tue, 23 Jul 2013 15:20:53 +0000 (UTC) Received: (qmail 61643 invoked by uid 500); 23 Jul 2013 15:20:51 -0000 Delivered-To: apmail-cloudstack-users-archive@cloudstack.apache.org Received: (qmail 60878 invoked by uid 500); 23 Jul 2013 15:20:49 -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 60650 invoked by uid 99); 23 Jul 2013 15:20:48 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Jul 2013 15:20:48 +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 (nike.apache.org: domain of kirk.jantzer@gmail.com designates 209.85.219.43 as permitted sender) Received: from [209.85.219.43] (HELO mail-oa0-f43.google.com) (209.85.219.43) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Jul 2013 15:20:42 +0000 Received: by mail-oa0-f43.google.com with SMTP id i7so11598918oag.16 for ; Tue, 23 Jul 2013 08:20:21 -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=rjYzC3UuKLJhCVIQOlOMLTFn//3xlz/H4txIpHUSMis=; b=PzKzTiKe1BeV3DKPSeRTKECVx6kbpUK6rhF4keYh2gk9zJtj7S4Membe1j/tLkZ7Pu j379uqqRCD0wAv3TEHHTa1vscFxtwYOH2F+Zy6oZqatgV1L1PT03/E5AWYkOYab/2Deh hVVD0QflMEvWLRY09DIA74RZqiQfg+wsbEce9DPt7KUkxdLIJOQ+wNxpeZIQcaRrNVpQ VKuiCvnG+gx/GXP1ttgFRu4SvrwJshHPv7ygLC/kBZ0IDLz+9DryT2hrePnfVMAjIuAl Y6G1bxJzRZH4ZqSOXz2Ci33aEyxU5+wrEKBVSWvHrPx/nV6j4RLHxnoZEkTo/1RAJdIZ uyeQ== MIME-Version: 1.0 X-Received: by 10.43.51.68 with SMTP id vh4mr19395399icb.52.1374592821639; Tue, 23 Jul 2013 08:20:21 -0700 (PDT) Received: by 10.64.251.34 with HTTP; Tue, 23 Jul 2013 08:20:21 -0700 (PDT) In-Reply-To: <1740531509.2060633.1374592252998.JavaMail.root@inria.fr> References: <1740531509.2060633.1374592252998.JavaMail.root@inria.fr> Date: Tue, 23 Jul 2013 11:20:21 -0400 Message-ID: Subject: Re: Cloudstack can't deploy new vm From: Kirk Jantzer To: Cloudstack users mailing list Content-Type: multipart/alternative; boundary=bcaec529a0fbd8465e04e22f544b X-Virus-Checked: Checked by ClamAV on apache.org --bcaec529a0fbd8465e04e22f544b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Please paste the contents of /var/log/cloudstack/management/management-server.log to PasteBin so that we can analyze that. On Tue, Jul 23, 2013 at 11:10 AM, Pierre Benard wro= te: > Hi, > > Thank you for your answer. > > Our virtual router vm was used @50% of CPU and the network traffic it was > amazing. > We had some system scripts who send DNS request storm on virtual router. > Now, we have corrected this and now the usage of cpu is under 1% and > network traffic is "normal". > > But, this operation don't be resolving our problems of new instance > deployment :-( > > Somebody has an other idea ? > > Thanks in advance. > > Pierre > > ----- Mail original ----- > > De: "ramnivas indani" > > =C3=80: users@cloudstack.apache.org > > Envoy=C3=A9: Mardi 23 Juillet 2013 10:27:11 > > Objet: Re: Cloudstack can't deploy new vm > > > > We also face this kind of problem many times but in our case its > > because of > > router or storage instance are disconnected or down under vmware, i > > will > > suggest you to check their connectivity once not only from cloudstack > > but > > also from backend. > > > > > > On Tue, Jul 23, 2013 at 1:50 PM, Pierre Benard > > wrote: > > > > > Hi, > > > > > > > > > > > > We have a problem with our CloudStack. > > > We can't deploying new instance. When we try to deploy new vm we > > > have a > > > short error message on the CloudStack interface : "Unable to create > > > a > > > deployment for VM[User|i-3-2764-VM]" . We have the same error when > > > we > > > deploy new instance from iso or template. > > > In the event page on CS, we have : > > > > > > VM.CREATE Error while starting Vm. Vm Id: 2764 > > > pierre.benard@inria.fr 22 Jul 2013 13:15:47 > > > VM.CREATE Starting job for starting Vm. Vm Id: 2764 > > > pierre.benard@inria.fr 22 Jul 2013 13:15:47 > > > VM.CREATE Scheduled async job for starting Vm. Vm Id: 2764 > > > pierre.benard@inria.fr 22 Jul 2013 13:15:46 > > > VM.CREATE Successfully created entity for deploying Vm. Vm > > > Id: 2764 > > > pierre.benard@inria.fr 22 Jul 2013 13:15:46 > > > > > > Isn't really verbose ... > > > > > > > > > All the other instance are continuous to running correctly, we can > > > stop/start it. > > > There is no significant error in the log files of CloudStack server > > > and on > > > each we sufficient resources to deploy many instances. > > > The SSVM and primary storage are available. > > > > > > > > > Our CloudStack environment : > > > * CloudStack v3 > > > * 1 pod of 4 clusters KVM, each cluster has 4 KVM hypervisor > > > > > > > > > Please Suggest. > > > > > > > > > Thank you. > > > > > > > > > Pierre B=C3=A9nard > > > System engineer > > > > > > > > > Inria Rennes - Bretagne Atlantique > > > > > > Campus universitaire de Beaulieu > > > 35042 Rennes Cedex > > > T=C3=A9l. +33 2 99 84 71 00 > > > Fax +33 2 99 84 71 71 > > > www.inria.fr > > > > > > Suivez=E2=80=90nous sur : > > > Twitter twitter.com/inria > > > YouTube youtube.com/inriachannel > > > > > > > > > > > > --=20 Regards, Kirk Jantzer c: (678) 561-5475 http://about.met/kirkjantzer --bcaec529a0fbd8465e04e22f544b--