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 <[email protected]>wrote: > 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" <[email protected]> > > À: [email protected] > > Envoyé: 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 > > <[email protected]>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 > > > [email protected] 22 Jul 2013 13:15:47 > > > VM.CREATE Starting job for starting Vm. Vm Id: 2764 > > > [email protected] 22 Jul 2013 13:15:47 > > > VM.CREATE Scheduled async job for starting Vm. Vm Id: 2764 > > > [email protected] 22 Jul 2013 13:15:46 > > > VM.CREATE Successfully created entity for deploying Vm. Vm > > > Id: 2764 > > > [email protected] 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énard > > > System engineer > > > > > > > > > Inria Rennes - Bretagne Atlantique > > > > > > Campus universitaire de Beaulieu > > > 35042 Rennes Cedex > > > Tél. +33 2 99 84 71 00 > > > Fax +33 2 99 84 71 71 > > > www.inria.fr > > > > > > Suivez‐nous sur : > > > Twitter twitter.com/inria > > > YouTube youtube.com/inriachannel > > > > > > > > > > > > -- Regards, Kirk Jantzer c: (678) 561-5475 http://about.met/kirkjantzer
