Hi,
please once check the secondary storage path for download vm is right or
nor?
Thanks,Prapul Sriram
On Thursday, 1 January 2015 2:03 PM, Mohamed Infaz
wrote:
Hi Somesh,
Yes i was successful in stopping both the system vm's and starting them
back i also could access them through the console that cloudstack provides.
May be the reason for that code snippet is that i didn't register the
template but i ran this script to install the system vm's.
1.
/usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt
\
2. -m /srv/images/secondary \
3. -u
http://download.cloud.com/templates/4.3/systemvm64template-2014-01-14-master-kvm.qcow2.bz2
\
4. -h kvm \
5. -F
this was on the docs. How about upgrading my cloudstack version to 4.4.
This whole thing happened in 4.3.
Thank you.
On 1 January 2015 at 01:39, Somesh Naidu wrote:
> You mean the system VMs for Zone 1 are running? Are they showing as
> connected in the DB?
>
> If they are, can you stop these VMs and see if they start okay.
>
> From: Mohamed Infaz [infaz...@cse.mrt.ac.lk]
> Sent: Tuesday, December 30, 2014 21:26
> To: us...@cloudstack.apache.org
> Cc: dev@cloudstack.apache.org
> Subject: Re: Unable to start VM due to concurrent operation
>
> systemvm64template-2014-01-14-master-kvm.qcow2.bz2 This is the template i
> used.
>
>
> On 31 December 2014 at 07:49, Mohamed Infaz
> wrote:
>
> > Hi Somesh,
> >
> > Thank you for the reply. Well both of my system vm's are running and it
> is
> > downloading the iso image. And i was able to ping them. The system vm
> > template i am using is for the version 4.3 cloudstack.
> >
> > Thank you.
> >
> > On 30 December 2014 at 23:59, Somesh Naidu
> > wrote:
> >
> >> Mohamed,
> >>
> >> The log snippet you have shared doesn't seem to be relevant to the
> >> concurrent operation exception (can't see that exception stack).
> >>
> >> The message that did catch my attention though is,
> >> -
> >> 2014-12-31 05:25:07,972 DEBUG [c.c.s.s.SecondaryStorageManagerImpl]
> >> (secstorage-1:ctx-463d2f57) System vm template is not ready at data
> center
> >> 1, wait until it is ready to launch secondary storage vm
> >> 2014-12-31 05:25:07,972 DEBUG [c.c.s.s.SecondaryStorageManagerImpl]
> >> (secstorage-1:ctx-463d2f57) Zone 1 is not ready to launch secondary
> storage
> >> VM yet
> >> -
> >>
> >> That's pointing to missing system VM template. Please verify that you
> >> have correctly provisioned the secondary storage with the correct
> system VM
> >> template (as per the docs).
> >>
> >> -Somesh
> >>
> >> -Original Message-
> >> From: Mohamed Infaz [mailto:infaz...@cse.mrt.ac.lk]
> >> Sent: Tuesday, December 30, 2014 11:03 AM
> >> To: us...@cloudstack.apache.org
> >> Cc: dev@cloudstack.apache.org
> >> Subject: Unable to start VM due to concurrent operation
> >>
> >> Hi All,
> >>
> >> I have successfully deployed cloudstack 4.3 with two hosts and the setup
> >> runs the management server on another physical host. I had issues with
> >> downloading an ISO but finally i was able to download an ISO image.
> When i
> >> want to create an instance i get the following error message saying
> >> "Unable
> >> to start VM due to concurrent operation" i did some searching on the
> topic
> >> and it said version 4.3 system template solved the issue. These are some
> >> of
> >> the MS logs that i collected what could be the issue?
> >>
> >> 2014-12-31 05:25:07,972 DEBUG [c.c.s.s.SecondaryStorageManagerImpl]
> >> (secstorage-1:ctx-463d2f57) System vm template is not ready at data
> center
> >> 1, wait until it is ready to launch secondary storage vm
> >> 2014-12-31 05:25:07,972 DEBUG [c.c.s.s.SecondaryStorageManagerImpl]
> >> (secstorage-1:ctx-463d2f57) Zone 1 is not ready to launch secondary
> >> storage
> >> VM yet
> >> 2014-12-31 05:25:12,425 DEBUG [c.c.a.m.AgentManagerImpl]
> >> (AgentManager-Handler-9:null) Ping from 4
> >> 2014-12-31 05:25:12,834 DEBUG [c.c.a.m.AgentManagerImpl]
> >> (AgentManager-Handler-5:null) SeqA 3-91695: Processing Seq 3-91695: {
> Cmd
> >> , MgmtId: -1, via: 3, Ver: v1, Flags: 11,
> >>
> >>
> [{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":1,"_loadInfo":"{\n
> >>
