Yeah, I guess I thought the end user wasn't generally concerned about hypervisors...that CloudStack typically handles that, but maybe CloudStack is more responsible for handling which cluster of the same hypervisor type to place a new VM on.
On Mon, Aug 12, 2013 at 8:58 PM, Marcus Sorensen <shadow...@gmail.com>wrote: > One reason is that unlike the hypervisor specific templates, there's no > such information predetermined. Consider a cloudstack zone with both xen > and KVM clusters. User needs to choose which hypervisor to deploy in. Its > also important since the resulting install from iso will be in the chosen > hypervisors format. > On Aug 12, 2013 8:29 PM, "Mike Tutkowski" <mike.tutkow...@solidfire.com> > wrote: > > > Hi, > > > > When you spin up a VM based on an ISO, you have to specify the > hypervisor. > > > > Just curious, but why does the user pick this? > > > > Thanks! > > > > -- > > *Mike Tutkowski* > > *Senior CloudStack Developer, SolidFire Inc.* > > e: mike.tutkow...@solidfire.com > > o: 303.746.7302 > > Advancing the way the world uses the > > cloud<http://solidfire.com/solution/overview/?video=play> > > *™* > > > -- *Mike Tutkowski* *Senior CloudStack Developer, SolidFire Inc.* e: mike.tutkow...@solidfire.com o: 303.746.7302 Advancing the way the world uses the cloud<http://solidfire.com/solution/overview/?video=play> *™*
