Secondary storage is zone wide not pod-specific. Pod2 probably has some problems (enough shared storage perhaps?). The MS logs should indicate the problem.
On 4/11/13 7:03 PM, "Jeronimo Garcia" <garciaj...@gmail.com> wrote: >just to clarify I'm using KVM. > >Thanks! > > >On Thu, Apr 11, 2013 at 1:26 PM, Jeronimo Garcia ><garciaj...@gmail.com>wrote: > >> Hi. >> >> Thanks for your answer . >> System vms images are normally in secondary storage , and currently i >> have 3 pods and one and only secondary storage nfs system, >> >> When i shut down all the servers on POD1 , the system vms refused to >> launch in pod2 , would it be cause Pod2 has to have it's own secondary >> storage. >> >> Thanks! >> >> >> On Thu, Apr 11, 2013 at 12:08 PM, Kelven Yang >><kelven.y...@citrix.com>wrote: >> >>> System VMs are tend to be running in stateless mode, instead of >>>fail-over >>> of same VM, we are launching new instance of them, this behave is done >>>for >>> storage and console proxy system VM, for virtual router system VM, >>>there >>> is a redundant configuration, automatic HA would make the redundant >>> configuration unstable. so in general, system VMs don't use HA offering >>> purposely. >>> >>> Kelven >>> >>> On 4/11/13 7:54 AM, "Jeronimo Garcia" <garciaj...@gmail.com> wrote: >>> >>> >Anyone ever bumped into this yet? >>> > >>> >Thanks! >>> > >>> > >>> >On Wed, Apr 10, 2013 at 11:27 AM, Jeronimo Garcia >>> ><garciaj...@gmail.com>wrote: >>> > >>> >> Hi List. >>> >> >>> >> Based on documentation and what I'm actually seeing now , system >>>vms >>> >>can >>> >> only failover to other hosts in the same cluster and therefore pod. >>> >> >>> >> I'm guessing this is because the system vm is using a management ip >>> >> assigned to that specific pod. >>> >> >>> >> Is there any HA offering that could make system VMs to failover to >>> >> different pods/clusters? >>> >> >>> >> Thanks! >>> >> >>> >>> >>
