On 3/4/14 2:33 AM, "Abhinandan Prateek"
wrote:
>Is the initial list of supported os coming from Hypervisor
Yes. More specifically, for now the list is coming from :
KVM : http://bit.ly/1kY6msQ
Xen : http://bit.ly/1mUei3f
VMW : http://bit.ly/MMsAlF
Hi,
Responses inline.
Thanks,
Amogh
On 3/4/14 12:00 AM, "Daan Hoogland" wrote:
>+1 for the feature,
>
>Did you consider systemvms? Or the default vm-template? Or are those
>marked as undeletable or even hardcoded in case the table gets editted
>outside of ACS?
[Amogh] Sorry, I don't think I get
+1 for the feature, but usually I just go for “other paravirtualized (64 bit)”
(paraphrasing, mistakes mine) nowadays. What would be more useful, IMHO, is to
better document the what the selection OS type selection choice means for a VM.
For KVM, it’s a hell of a lot more than SCSI vs IDE root d
On 04/03/14 2:14 am, "Amogh Vasekar" wrote:
>Hi,
>
>CloudStack currently does not allow an easy way to add new guest OS types,
>for example, a standard way to add say, CentOS 6.5 even though a
>hypervisor may support it.
>Part of the reason is since the OS to hypervisor-specific platform
>mapping
+1 for the feature,
Did you consider systemvms? Or the default vm-template? Or are those
marked as undeletable or even hardcoded in case the table gets editted
outside of ACS?
The delete feature is vital. You marked it as open for discussion but
I don't agree. The admin should delete when he make
Hi,
CloudStack currently does not allow an easy way to add new guest OS types,
for example, a standard way to add say, CentOS 6.5 even though a
hypervisor may support it.
Part of the reason is since the OS to hypervisor-specific platform
mappings are currently hard-coded into the code-base [1][2]
