Table 4.6 Virtual Machine Maximums
Item | Maximum | Notes |
|---|---|---|
Virtual CPUs (X7-2) | 48 | Equals the maximum number of CPU threads for a single Oracle Server X7-2 CPU socket. |
Virtual CPUs (X6-2) | 44 | Equals the maximum number of CPU threads for a single Oracle Server X6-2 CPU socket. |
Virtual CPUs (X5-2) | 36 | Equals the maximum number of CPU threads for a single Oracle Server X5-2 CPU socket. |
Virtual CPUs (X4-2) | 16 | Equals the maximum number of CPU threads for a single Sun Server X4-2 CPU socket. |
Virtual CPUs (X3-2) | 16 | Equals the maximum number of CPU threads for a single Sun Server X3-2 CPU socket. |
Virtual RAM (32-bit guest) | 63GB | |
Virtual RAM (64-bit guest) | 1000GB | The maximum is for a HVM guest. If more memory is assigned, performance could be adversely affected, and live migration is no longer possible.
A PVHVM guest can use the installed amount of physical
RAM minus a safe margin of 32GB for use by
Windows guests with PV drivers are limited to 256GB virtual RAM. |
Virtual NICs (paravirtualized guest) | 31 | |
Virtual NICs (hardware virtualized guest) | 8 | |
Virtual Disks (paravirtualized guest) | PVM: 104 PVHVM: 107 | |
Disks: virtual and other (hardware virtualized guest) | 4 | In the case of hardware virtualized guests, "disks" refers to virtual disks as well as IDE and SCSI hard drives, and cd-rom drives. |
These maximums do not account for CPUs allocated to any other domains, such as the control domain. The hypervisor can allocate subsets of the overall CPU, memory, and I/O resources of a server to any given logical domain.
Virtual Machine maximums assume a single virtual machine using all available resources.
The virtual CPU numbers are recommended maximums for best performance. Since each compute node has two CPU sockets, the hard limit, which must never be exceeded, is twice the recommended maximum. However, when a large VM requires more virtual CPU threads than a single socket can provide, its performance is likely to be reduced.
Table 4.7 Oracle VM Server Maximums
Item | Maximum | Notes |
|---|---|---|
CPUs (X7-2) | 48 | The Oracle Server X7-2 contains two 24-core CPUs with hyperthreading enabled. |
CPUs (X6-2) | 44 | The Oracle Server X6-2 contains two 22-core CPUs with hyperthreading enabled. |
CPUs (X5-2) | 36 | The Oracle Server X5-2 contains two 18-core CPUs with hyperthreading enabled. |
CPUs (X4-2, X3-2) | 16 | The Sun Server X4-2 and Sun Server X3-2 contain two 8-core CPUs with hyperthreading enabled. |
RAM (X7-2) | 1.5TB | This is the maximum installed amount of RAM in the Oracle Server X7-2. |
RAM (X6-2, X5-2) | 768GB | This is the maximum installed amount of RAM in the Oracle Server X6-2 and Oracle Server X5-2. |
RAM (X4-2, X3-2) | 256GB | This is the maximum installed amount of RAM in the Sun Server X4-2 and Sun Server X3-2. |
Virtual Machines | 128 |
A limited amount of RAM is required by the hypervisor.
Table 4.8 Server Pool and Cluster Maximums
Item | Maximum | Notes |
|---|---|---|
Oracle VM Servers in a clustered server pool | default: 25 custom: 24 | In a base rack configuration, the maximum number of installed compute nodes is 25. All compute nodes may be a member of the default server pool. However, the default server pool cannot be empty, so any server pool associated with a custom tenant group can contain up to 24 compute nodes. |
Clusters per Oracle Private Cloud Appliance | 8 | This maximum includes the default server pool. |
Table 4.9 Storage Maximums
Item | Maximum | Notes |
|---|---|---|
iSCSI LUNs and paths per Compute Node | 1000 LUNs 2000 paths | The limit is the total number of paths. In this regard, each identical LUN connected as a single multipath device must be considered as a separate path. Examples of supported configurations are: 1000 LUNs with 2 paths each, 500 LUNs with 4 paths each, or 250 LUNs with 8 paths each. |
vHBAs per Compute Node | 8 | This number is based on the 4 default vHBAs plus 4 optional customer-defined vHBAs. |
| Targets per vHBA | 64 | This number is based on the configuration of the Oracle Fabric Interconnect F1-15. |
FC LUNs per Compute Node | 256 | This number is the recommended and supported maximum for Fibre Channel. Verify compliance with this guideline by using this formula: (number of vHBAs) * (targets per vHBA) * (LUNs per target) <= 256. For example: (4 vHBAs) * (4 targets) * (16 LUNs) = 256. |
OCFS2 volume size | 64TB | |
Files per OCFS2 volume | 30,000 | |
Virtual Disk size | 10TB | The maximum is determined by the hardware capacity. |
Virtual IDE drives per device | 4 | |
|
LUNs and paths per Oracle Server X8-2 compute nodes with fibre channel cards |
1000 LUNs 4000 paths |
Examples of supported configurations are: 500 LUNs with 8 paths each, or 1000 LUNs with 4 paths each. |
Table 4.10 Networking Maximums
Item | Maximum | Notes |
|---|---|---|
NICs per Bond | 2 | The limit is 255 per bond or aggregate. |
Custom networks per rack | internal: 12 external: 7 total combined max: 16 | Oracle Private Cloud Appliance accepts a maximum of 12 internal networks and 7 external networks (7 port pair across base ports 4,5,10,11). This maximum includes the default internal network and the default external network. |
| Custom networks per compute node | internal: 5 external: 9 | This maximum includes the 2 default internal networks and the 2 default external networks. |
Bonds per Compute Node | 10 | This maximum applies to custom networks. It does not include the default network configuration, which consists of 5 bonds and 1 GbE connection. Oracle Private Cloud Appliance accepts a maximum of 3 custom internal networks and 7 custom external networks per tenant group or per compute node. |
VLANs per Server Pool | 256 | If the number of VLANs is larger than 256 the boot times of the servers are severely impacted. The maximum applies to any given tenant group or compute node. |
Packet Size (MTU) | Ethernet: 9000 IPoIB: 64000 | The default maximum transmission unit for Ethernet bonds/ports is 9000 bytes. IPoIB traffic on the storage network is configured at a default MTU of 64000 bytes. |