@rhtyd The rationale to have vmware.nested.virtualization.perVM was that
advanced vm_details and template details are user controlled. With
https://issues.apache.org/jira/browse/CLOUDSTACK-9457
‘Allow retrieval and modification of VM and template details via API and UI’
users will be able to change any advanced details in UI and API.
If admin wants to preserve that nested virtualization is controlled in
centralized fashion they can do so by setting
vmware.nested.virtualization.perVM to ‘false’. Idea was to allow organizations
that currently have nested virtualization disabled to have it so after upgrade.
On 8/16/16, 10:21 AM, "rhtyd" <g...@git.apache.org> wrote:
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1542
@nvazquez @serg38 how about we remove
vmware.nested.virtualization.perVM and instead if the user vm detail exists and
is true, it overrides the global setting?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
