Changeset 36944 in vbox for trunk/src/VBox/VMM

Timestamp:

May 3, 2011 5:13:31 PM (14 years ago)

Author:

vboxsync

svn:sync-xref-src-repo-rev:

71531

Message:

VBox/param.h: Bumped the max RAM limit up to 2TB on 64-bit hosts (was 16GB). Docs

Location:

trunk/src/VBox/VMM

Files:

• VMMR0/GMMR0.cpp (modified) (1 diff)
• VMMR3/VMM.cpp (modified) (1 diff)

trunk/src/VBox/VMM/VMMR0/GMMR0.cpp

@@ -134 +134 @@
  *
  *
- * @section sec_gmm_numa  NUMA
+ * @section sec_gmm_numa        NUMA
  *
  * NUMA considerations will be designed and implemented a bit later.

trunk/src/VBox/VMM/VMMR3/VMM.cpp

@@ -44 +44 @@
  *
  * To be written.
+ *
+ *
+ * @sections sec_vmm_limits     VMM Limits
+ *
+ * There are various resource limits imposed by the VMM and it's
+ * sub-components.  We'll list some of them here.
+ *
+ * On 64-bit hosts:
+ *      - Max 1023 VMs.  Imposed by GVMM's handle allocation
+ *        (GVMM_MAX_HANDLES), can be increased up to 64K.
+ *      - Max 16TB - 64KB of the host memory can be used for backing VM RAM and
+ *        ROM pages.  The limit is imposed by the 32-bit page ID used by GMM.
+ *      - A VM can be assigned all the memory we can use (16TB), however, the
+ *        Main API will restrict this to 2TB (MM_RAM_MAX_IN_MB).
+ *      - Max 32 virtual CPUs (VMM_MAX_CPU_COUNT).
+ *
+ * On 32-bit hosts:
+ *      - Max 127 VMs.  Imposed by GMM's per page structure.
+ *      - Max 64GB - 64KB of the host memory can be used for backing VM RAM and
+ *        ROM pages.  The limit is imposed by the 28-bit page ID used
+ *        internally in GMM.  It is also limited by PAE.
+ *      - A VM can be assigned all the memory GMM can allocate, however, the
+ *        Main API will restrict this to 3584MB (MM_RAM_MAX_IN_MB).
+ *      - Max 32 virtual CPUs (VMM_MAX_CPU_COUNT).
  *
  */