Including a row in hypervisor_capabilities table for 'Simulator' as
hypervisor type seems to have done the trick.
Thanks again!
On Tue, Sep 10, 2013 at 9:37 AM, David Grizzanti <
david.grizza...@sungard.com> wrote:
> All,
>
> Thanks for the suggestions and help. I'll try out what Prasanna sugg
All,
Thanks for the suggestions and help. I'll try out what Prasanna suggested
and let you know.
Thanks!
On Tue, Sep 10, 2013 at 12:55 AM, Prasanna Santhanam wrote:
> On Tue, Sep 10, 2013 at 12:08:11AM -0400, Chip Childers wrote:
> > On Mon, Sep 9, 2013 at 4:10 PM, Edison Su wrote:
> >
> >
On Tue, Sep 10, 2013 at 12:08:11AM -0400, Chip Childers wrote:
> On Mon, Sep 9, 2013 at 4:10 PM, Edison Su wrote:
>
> > The current implementation of simulator has its own limitation: the
> > simulator itself is a separate hypervisor type, thus a lot of condition
> > checks against hypervisor typ
On Mon, Sep 9, 2013 at 4:10 PM, Edison Su wrote:
> The current implementation of simulator has its own limitation: the
> simulator itself is a separate hypervisor type, thus a lot of condition
> checks against hypervisor type in mgt server will fail if simulator is used.
> For example, currently,
The current implementation of simulator has its own limitation: the simulator
itself is a separate hypervisor type, thus a lot of condition checks against
hypervisor type in mgt server will fail if simulator is used.
For example, currently, the zone wide primary storage only works for vmware and
