Hi Kirk,
Thanks for the response.
The options you have mentioned to not exist within 4.1.1.
Looking at the code they seem to of been introduced from 4.2 onwards.
Thanks,
Ian
On 11 September 2014 01:54, Kirk Kosinski wrote:
> >> start VM which goes to hypervisor hosts
> >
> > Not directly to
>> start VM which goes to hypervisor hosts
>
> Not directly to the hypervisors right? They go through vCenter if I
> understand correctly.
Right, the commands go through vCenter, similar to commands to XS hosts
going through the pool master. But the command sequences will be
host-specific, which
Hi Kirk,
> Did you figure this out?
No, we didn't look into it much more. Its not causing issues just yet and
is just a curiosity thing.
> start VM which goes to hypervisor hosts
Not directly to the hypervisors right? They go through vCenter if I
understand correctly.
> How many VMware hosts do
Hi, Ian. Did you figure this out? Template deployment in VMware is
done through the SSVM instead of hosts so the behavior may be different
than other commands, like start VM which goes to hypervisor hosts. How
many VMware hosts do you have? If you have few or just one VMware host,
the commands
Hi All,
I'm using Cloudstack 4.1.1 against vCenter 5.
If I create 5 instances on cloudstack. I see the 5 disks get created in
parallel but the power up and power down events do not.
Is this expected functionality? Or should power up and power down events
occur at the same time? If so is there so
