Which hypervisor are you working with? Have you seeded the secondary storage with the systemvm template for the hypervisor?
Regards, Devdeep > -----Original Message----- > From: Amin Pashapour [mailto:jol...@yahoo.com] > Sent: Tuesday, May 13, 2014 1:05 AM > To: users@cloudstack.apache.org > Subject: Re: Not able to create instances on CloudStack > > You can't really do much without ssvm. Do you see the VM's on your > hypervisor? Do you see the datastores on your hypervisor? > > I suggest you look at the log files while creating the primary and secondary > storage. It could be all sorts of things including network connections. > > Amin > > > > > ________________________________ > From: Harsh Verma <harsh.ve...@aricent.com> > To: "users@cloudstack.apache.org" <users@cloudstack.apache.org> > Sent: Thursday, May 8, 2014 5:58 AM > Subject: Not able to create instances on CloudStack > > > Hi, > > I have created a Zone, Pod and Cluster on CloudStack.I have also added a > host in the Cluster, added Primary Storage and Secondary Storage. But in > System VMs, nothing is listed. Also, in the logs a message "No running ssvm is > found, so command will be sent to LocalHostEndPoint" comes. > > Somehow I deduced that due to this, template is not being added and > consequently Instances can't be created as Instances use templates to add > OS in VMs. > > Can anybody please help to point out and sort the problem which may be the > cause here. > > Thanks, > Harsh > Aricent Group > > > "DISCLAIMER: This message is proprietary to Aricent and is intended solely > for the use of the individual to whom it is addressed. It may contain > privileged or confidential information and should not be circulated or used > for any purpose other than for what it is intended. If you have received this > message in error, please notify the originator immediately. If you are not the > intended recipient, you are notified that you are strictly prohibited from > using, copying, altering, or disclosing the contents of this message. Aricent > accepts no responsibility for loss or damage arising from the use of the > information transmitted by this email including damage from virus."
