i cannot access the console of SSVM ,
i ran a python ../marvin/marvin/deployDataCenter.py -i devcloud.cfg python
script to setup my basic zone.
but my virtual router shown 0 in the infrastructure even after restarting
my MS, any idea on why on getting my virtual router up ?? thanks.

regards,
punith s


On Thu, Oct 3, 2013 at 7:04 PM, Wei ZHOU <ustcweiz...@gmail.com> wrote:

> Can you run ssvm_check.sh in SSVM ?
> The template is in devcloud2, so it should because of an unknown
> misconfiguration.
>
>
> 2013/10/3 Punith s <punit...@cloudbyte.com>
>
> > yea i'm also finding issue with the sysvm in devcloud at host only mode.
> > the tiny linux template is not getting downloaded even though the
> secondary
> > storage sys vm is shown running in the UI , but i can't access its
> console.
> > i even tried ssh into 192.168.56.10(xenbr0) and looked into
> >  root@devcloud:/opt/storage/secondary/template/tmpl/1/5# ls
> > ce5b212e-215a-3461-94fb-814a635b2215.vhd  template.properties where the
> > .vhd is present.
> >
> > i think The Secondary Storage VM is failing to  retrieve templates and
> make
> > the ready to use.
> > i looked into vmops.log and
> > found com.cloud.storage.download.DownloadListener.java doing this job ,
> > perhaps need to debug to know who is calling this.
> >
> >
> >
> >
> > On Thu, Oct 3, 2013 at 6:38 PM, benoit lair <kurushi4...@gmail.com>
> wrote:
> >
> > > Okay, i changed the ip of the secondary storage server into the ip
> range
> > of
> > > the pod, it doesn't work better.
> > >
> > > I change now the network of the secondary storage server.
> > >
> > >
> > > 2013/10/3 benoit lair <kurushi4...@gmail.com>
> > >
> > > > I thought i could have my secondary storage nfs server into the mgmt
> > cidr
> > > > ? It were okay with a cs 4.0.0
> > > >
> > > > So i need to move my secondary storage nfs server to the 10.32.0.0
> > cidr ?
> > > >
> > > >
> > > > 2013/10/3 Wei ZHOU <ustcweiz...@gmail.com>
> > > >
> > > >> I guess the root cause could be that your nfs server ip is not in
> > > storage
> > > >> network.
> > > >>
> > > >
> > > >
> > >
> >
>

Reply via email to