IBM Cloud Docs
Assigning an IBM i software tier to an IBM i Power Virtual Server instance

Assigning an IBM i software tier to an IBM i Power Virtual Server instance


IBM Power Virtual Server in IBM data center

IBM Power Virtual Server Private Cloud in Client location


Starting with IBM Power10 systems and later, you can assign an IBM i software tier to a virtual server instance (VSI). The IBM i software tier limits the size of the VSI. But, you can select any physical system that supports the selected IBM i software tier. For example, a virtual server that is assigned to a P10 tier can run on either an S1022 or an E1080 server. The tier restricts the resource allocation for the VSI, not its hardware compatibility.

The IBM i software tier determines the pricing tier for the IBM i operating system and licensed program products (LPPs). It also defines the limits for the following resources:

  • Maximum number of virtual processors
  • Maximum memory size

You can dynamically adjust the number of CPUs and the memory size if the numbers are within the IBM i software tier limits. To expand the size beyond the limit of the current IBM i software tier, you must follow these steps:

  1. Power off the VSI.
  2. Change the IBM i software tier to a tier that aligns with your resource requirements.

For more information, see Supported resource limits by the IBM i software tier.

When you change the software tier, the billing for the IBM i software tier automatically changes to reflect the selected tier.

You can generate an estimate of Power Virtual Server resources with an IBM i software tier before you deploy the resources. For more information, see Estimating a virtual server instance.

You must complete the following prerequisites to assign an IBM i software tier to a Power Virtual Server instance:

  • Select an IBM i image with version 7.3 or later from the Image list under the Boot image section.
  • Select an IBM Power10 or later server type from the Machine type list.
  • Complete the following steps to assign a VSN to the instance:
    • Edit the Virtual serial number (VSN) field.
    • The Virtual serial number (VSN) summary pane appears.
    • Select either Auto-assign or Select from retained VSNs option to assign a VSN.

The supported IBM i software tiers are displayed in the IBM i software tier list based on the machine type that you select. The recommended IBM i software tier is displayed in the IBM i software tier field based on the number of cores and the memory size. You can select the IBM i software tier that is displayed in the IBM i software tier field or other options from the list.

For more information, see Configuring a Power Virtual Server instance.

Supported resource limits by the IBM i software tier

For each IBM i software tier, the supported limits for resources are defined. These limits help align resource usage with software licensing costs. You must understand the supported limits of resources for planning your VSI size and ensure compliance with IBM i licensing models.

The following table provides the details of the maximum number of virtual processors and memory size allowed on each IBM i software tier.

Maximum virtual processors and memory size for each IBM i software tier
IBM i software tiers Maximum virtual processors Maximum memory size
P05 1 64 GB
P10 4 1 TB
P20 12 1 TB
P30 No limit No limit

Supported IBM i software tiers on Power Virtual Server

All IBM i software tiers are not supported on all the Power Virtual Server system types. The following table shows which IBM i software tiers are compatible with each system type.

Supported IBM i software tiers on Power Virtual Servers
System types Supported IBM i software tiers
P05 P10 P20 P30
S1022 Yes Yes Yes No
S1122 Yes Yes Yes No
E1080 No Yes Yes Yes
E1180 No Yes Yes Yes

IBM i is not supported on IBM E1050 and E1150 system types.

If you deploy multiple IBM i virtual server instances (VSIs) simultaneously on the IBM S1022 hosts using the P20 IBM i software tiers, the deployment might fail when the IBM data center is being upgraded. However, the deployment of a single VSI is supported.