Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1542
@rhtyd @jburwell @rafaelweingartner @koushik-das 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. Does it make sense or everyone prefers that setting on VM level
overrides global one?
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
