Github user jburwell commented on the issue:
https://github.com/apache/cloudstack/pull/1542
@rhtyd good idea to check the CPU flags. There is a part of me that would
like to see a VM actually spin up inside a VM, but there are also many things
that could go wrong that are not related to CloudStack. Plus, it would be
slow. Therefore, checking the CPU flags is an excellent compromise.
Another thing that I see in this PR is that nested virtualization seems
like a capability that should be more generally expressed and managed in
CloudStack's core abstractions. @rhtyd could you open a ticket to extract the
aspects of this enhancement that are common across all hypervisors that support
nested virtualization?
---
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.
---
