sureshanaparti commented on a change in pull request #240:
URL: 
https://github.com/apache/cloudstack-documentation/pull/240#discussion_r711005470



##########
File path: source/adminguide/hosts.rst
##########
@@ -207,6 +207,22 @@ any system that is not up to date with patches.
 
<http://docs.cloudstack.org/Knowledge_Base/Possible_VM_corruption_if_XenServer_Hotfix_is_not_Applied/Highly_Recommended_Hotfixes_for_XenServer_5.6_SP2>`_.
 
 
+Hypervisor Capabilities
+-----------------------
+For different hypervisors and their versions, various capabilities such as 
maximum number of guest VMs per host, maximum number of volumes per VM, 
security group support, etc are considered by CloudStack. These capabilities 
are stored in the **cloud.hypervisor_capabilities** table in the database. If a 
specific hypervisor version is not available in the database, values against 
the *default* version for the hypervisor will be used.
+
+Following hypervisor-specific documentations can be referred for different 
maximums for a particular hypervisor host:
+
+- VMware: `VMware Configuration Maximum tool 
<https://configmax.vmware.com/guest?vmwareproduct=vSphere&release=vSphere%207.0&categories=1-0,2-0>`_.
+
+- Citrix Hypervisor/Xenserver/XCP-ng: `Configuration limits | Citrix 
Hypervisor 8.2 
<https://docs.citrix.com/en-us/citrix-hypervisor/system-requirements/configuration-limits.html>`_.
+
+
+.. note::
+   Guest VM limit check is not done while deploying a VM on a KVM hypervisor 
host.
+

Review comment:
       The number of guest VMs can be updated using 
_updateHypervisorCapabilities_ API. @shwstppr  Do you mentioned it, and about 
other APIs for hypervisor capabilities (_listHypervisorCapabilities_, 
_updateHypervisorCapabilities_).




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Reply via email to