Editing VM CPUs and RAM
Virtual machine hardware settings determine the amount of Metered RAM and CPU capacity that the VM consumes—larger VMs consume more Metered RAM and CPU capacity. For information about how Metered RAM and CPU capacity are calculated, see How usage is calculated.
To edit the VM CPU and RAM settings
- Make sure the VM is fully powered off (not running or suspended).
- Before making hardware changes to your VM, create a template of it. If any problems occur, you can restore your VM from this template.
Navigate to the VM Settings > Hardware page.
Show me how
- Navigate to the environment that contains the VM you want to edit.
If the Settings button is not visible, you do not have permission to edit the VM settings. Work with your instructor or Skytap administrator to edit these settings.
- The VM Settings page displays. Click the Hardware tab.
Next to CPUs, select the number of CPUs that the VM will use.
If an x86 VM is hardware version 10 or newer, click Advanced to see multi-core CPU options. By default, Skytap configures 1 CPU core per socket.
- The maximum number of CPUs for a single VM varies, depending on region. For a list of regional capabilities, see Skytap Cloud features by region.
- If an x86 VM is hardware version 9 or earlier, you can upgrade the VM hardware version to make advanced CPU configuration options available. For instructions, see Upgrading VM hardware versions.
- The number of cores per socket must be 1, 2, 4, or 8. Only valid CPU configuration options are displayed.
Next to RAM, enter The amount of RAM (in MB) that the VM will use.
- The amount of ram (in GB) must be equal to or greater than the number of CPUs.
- The maximum amount of RAM available for a single VM varies, depending on region.
- For x86 VMs – Increasing the amount of RAM, also increases the IOPS performance (up to 16 GB of RAM).
- For Power A CPU architecture that supports IBM i, AIX, and Linux (on Power) in Skytap Cloud. VMs – Increasing RAM enables higher Entitled capacity (effectively increasing CPU performance). For specific details, see the CPU Entitled capacity lookup table below.
- For Power A CPU architecture that supports IBM i, AIX, and Linux (on Power) in Skytap Cloud. VMs – The minimum supported RAM is 2048 MB (2 GB).
- Click Save.
Follow vendor recommendations for the operating system and the installed applications when setting the CPU and RAM values. Generally:
- Additional CPU cores permit more concurrent system and application processes, which improves system performance.
- Additional RAM allows more applications to be active and improves access speeds for data.
Some VMs may not support every configuration option that Skytap allows you to set. The guest OS type and hardware version number determine the amount of CPUs and RAM that a VM can use.
- Windows Server 2008 R2 Standard VMs support a maximum of 4 CPUs. If you select 8 CPUs, 4 of those CPUs are ignored by the guest OS.
- VM (x86 The most common CPU architecture. x86 CPUs support Windows and Linux VMs in Skytap Cloud. ) hardware versions 9 and earlier don’t support 12 CPUs or 256 GB of RAM. For example, if you select 12 CPUs for a VM on hardware version 7, you may see an error message when the VM runs.
RAM lookup table
These tables provide GB-to-MB conversion values for common RAM settings.
You can copy the MB value you want and paste it directly into the Hardware RAM (MB) field on the Hardware tab of the VM Settings page.
CPU Entitled capacity lookup table
For Power VMs, set Entitled capacity (and approximate IBM i CPW) by changing the amount of RAM and the number of CPUs.
The Entitled capacity (and approximate CPW) values in the table below are guaranteed when the corresponding RAM and CPUs are configured for the VM.
|RAM||Entitlement||CPW *||Entitlement||CPW *||Entitlement||CPW *||Entitlement||CPW *|
|≥ 224 GB||1.00||10,618||2.00||21,236||3.00||31,854||4.00||42,472|
|* CPW values are approximate.|
- Currently, a single IBM i VM supports a maximum of four CPU Cores (approximately 42,472 CPW).
- Existing active Power VMs will display calculated Entitled capacity (and approximate IBM i CPW) values but those values are not applied to the VM until it’s completely shut down, and then started again.