[
https://issues.apache.org/jira/browse/CLOUDSTACK-10297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16370063#comment-16370063
]
Rohit Yadav commented on CLOUDSTACK-10297:
------------------------------------------
Template details end up the vmx file of the VM, a partial-workaround is to set
virtualHW.version=10 (or lower version) as a template detail (using
updateTemplate API or in the user_vm_details table), however, it only works if
the template was created with the assigned value. A proper fix for CloudStack
would be to enforce virtualHW.version while deploying a VM, this could be a
cluster level setting to allow mixed ESXi hosts (with higher/lower versions
such as 5.5 and 6.5) to deploy a VM using a template created/exported from a
higher (say 6.5 ESXi) host.
> Provide a way to override VMware guest VM's hardware version using vm details
> -----------------------------------------------------------------------------
>
> Key: CLOUDSTACK-10297
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10297
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Rohit Yadav
> Priority: Major
> Fix For: Future
>
>
> Currently, CloudStack provide any mechanism to override hardware version
> (virtualHW.version) of a VMware VM using the user vm's details. A vm's config
> can add this details to extraConfig which will make its way to the vmx file.
> This can allow running VMs with explicit hardware version that may be
> compatible with say two version of esxis hosts in a mixed vmware env.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
