IBM Cloud Docs
What is a Power Virtual Server?

What is a Power Virtual Server?

IBM® Power® Virtual Server is a Power Systems offering. The Power Virtual Server are located in the IBM data centers, distinct from the IBM Cloud servers with separate networks and direct-attached storage. The environment is in its own pod and the internal networks are fenced but offer connectivity options to meet customer requirements. This infrastructure design enables Power Virtual Server to maintain key enterprise software certification and support as the Power Virtual Server architecture is identical to certified on-premises infrastructure. The virtual servers, also known as logical partitions (LPAR), run on IBM Power Systems hardware with the PowerVM hypervisor.

With the Power Virtual Server, you can quickly create and deploy one or more virtual servers (that are running either the AIX, IBM i, or Linux operating systems). After you provision the Power Virtual Server, you get access to infrastructure and physical computing resources without the need to manage or operate them. However, you must manage the operating system and the software applications and data. The following graphic represents a responsibility assignment (RACI) matrix for Power Virtual Servers:

Power Virtual Server responsibility assignment matrix
Figure 1. Power Virtual Server responsibility assignment matrix

Key features

The following are some of the key features for the Power Virtual Server.

Straightforward billing

Power Virtual Server uses a monthly billing rate that includes the licenses for the AIX and IBM i operating systems. The monthly billing rate is pro-rated by the hour based on the resources that are deployed to the Power Virtual Server instance for the month. When you create the Power Virtual Server instance, you can see the total cost for your configuration based on the options that you specify. You can quickly identify what configuration options provide you with the best value for your business needs. For more information, see Pricing.

Infrastructure customization

You can configure and customize the following options when you create a Power Virtual Server:

  • Number of virtual server instances
  • Number of cores
  • Amount of memory
  • Data volume size and type
  • Network interfaces

Bring your own image

IBM provides you with stock AIX and IBM i images when you create a Power Virtual Server. However, you can always bring your own custom AIX, IBM i, or Linux image that you have tested and deployed.

Support for SAP NetWeaver or SAP HANA applications

When you provision a Power Virtual Server instance to support SAP NetWeaver applications, select a version of the IBM-provided AIX or Linux stock operating system image. When you provision a Power Virtual Server instance to support the SAP HANA applications, select a version of the IBM provided Linux® stock image. IBM i operating system and custom AIX and Linux images are not supported for SAP workloads. For information about the supported operating system versions, see FAQ. For more information, see Deploying your infrastructure.

When provisioning a Power Virtual Server to support SAP NetWeaver applications, select a version of the IBM-provided AIX operating system stock image. IBM i and operating system custom images are not supported for SAP workloads currently.

Support for deploying a Red Hat OpenShift Cluster

When you provision a Red Hat OpenShift Cluster on Power Virtual Server, it is easier to use the IBM™ provided automation to create the entire cluster of servers and install Red Hat OpenShift rather than individually provisioning Power Virtual Server instances. For instructions to deploy a Red Hat OpenShift Cluster on Power Virtual Server, including preparation of the required Operation System images for the cluster, see Deploying Red Hat OpenShift Container Platform 4.x on IBM Power Virtual Servers.

Hardware specifications

The following IBM Power Systems can host a Power Virtual Server:

  • IBM Power System S922 (9009-22A)
  • IBM Power System S922 (9009-22G)
  • IBM Power System E980 (9080-M9S)
  • IBM Power System S1022 (9105-22A) For more information about these systems and how they're used inside the Power Virtual Server, see their data sheets and the hardware overview table.

If you'd like to compare your current environment's performance to what's available through the Power Virtual Server, see the IBM Power Systems performance report.

Data sheets

Table 1. Hardware overview (Washington, D.C.)
Compute Storage Network
  • Power S922 (9009-22A)
  • Power S922 (9009-22G)
  • Power E980 (9080-MHE)
  • Power S1022 (9105-22A) (WDC07 only) [1]
  • Flash Storage from IBM FS9000 series devices
  • V7000 SSD (no new VMs) (WDC04 only)
  • 32 GB SAN infrastructure
  • Cisco Nexus 9000 93180YC-EX (10G)
  • Cisco Nexus 9000 C9348GC-FXP (1G)
  • Avocent ACS8048
Table 2. Hardware overview (Dallas, TX)
Compute Storage Network
  • Power S922 (9009-22A)
  • Flash Storage from IBM FS9000 series devices
  • V7000 SSD (no new VMs)
  • 32 GB SAN
  • Cisco Nexus 9000 C9336PQ (Spine 10G)
  • Cisco Nexus 9000 C93180YC (10G)
  • Cisco Nexus 9000 C93108TC-EX (1G)
  • Cisco UCS - APIC controller
  • Cisco ASR1001-HX Router
  • Avocent ACS8016
Table 3. Hardware overview (Non-US)
Compute Storage Network
  • Power E980 (9080-M9S)
  • Power S922 (9009-22A)
  • Flash Storage from IBM FS9000 series devices
  • 32 Gb SAN infrastructure
  • Cisco Nexus 9000 N9K-C9364C (Spine 10G)
  • Cisco Nexus 9000 9348GC-FXP (Leaf 1G)
  • Cisco Nexus 9000 93180YC-FX (Leaf 25G)
  • Cisco UCS - APIC controller
  • Cisco ASR1001-HX Router
  • Avocent ACS8032DAC-400

For a complete list of supported data centers, see Creating a Power Virtual Server workspace.

Storage tiers

IBM Power Virtual Server offers you the option to select an I/O operation per second (IOPS) based storage as per your requirement. Flexible IOPS is a tier-less storage offering that removes the notion of disk type and replace it with a storage pool. Each of the storage pools supports multiple storage tiers. The storage tiers are based on different IOPS levels.

Table 2 shows the supported storage tiers with corresponding IOPS.

Table 4. Tier and IOPS mapping
Tier level IOPS Performance
Tier 0 25 IOPS/GB A 100-GB volume receives 2500 IOPS.
This is 2.5x faster than tier 1 and 8.3x faster than tier 3.
Tier 1 10 IOPS/GB A 100-GB volume receives 1000 IOPS.
This is 3.3x faster than tier 3.
Tier 3 3 IOPS/GB A 100-GB volume receives 300 IOPS.
Fixed IOPS 5000 IOPS regardless of size A 100-GB volume receives 5000 IOPS.

The use of fixed IOPS is limited to volumes with a size of 200 GB or less, which is the break even size with Tier 0 (200 GB @ 25 IOPS/GB = 5000 IOPS).

Flexible IOPS is currently available in DAL10, DAL12, DAL13, FRA04, FRA05, LON04, LON06, MAD02, MAD04, MON01, SAO01, SAO04, SYD04, SYD05, OSA21, TOK04, WDC04, WDC06, and WDC07 data centers. Flexible IOPS will be deployed in other data centers over time.

Working with the APIs

Use the List of all supported storage tiers for this cloud instance API to see the supported IOPS levels available for your workspace.

The storage tier that you choose does not influence the determination of the storage pool where a volume gets created in. If the storage tier is not specified, then the storage tier is set to Tier 3, by default.

The storage pool selection is based on the use of storage pool or storage affinity parameters. Specifying a storage pool identifies the storage pool directly while storage affinity uses a policy (affinity or anti-affinity) along with an existing volume or virtual server. For flexible IOPS all storage pools, support any tier level. Additionally, the storage tier is not tied to the storage pool.

Benefits of flexible IOPS

Flexible IOPS offers multiple IOPS levels (tiers) of storage to choose from. Each IOPS level has its own pricing, performance, and capability.

With flexible IOPS you can:

  • Create a volume (or multiple volumes) and specify the IOPS level that you want.
  • Change the volume level of IOPS of existing volumes while staying within the same storage pool.
  • Clone one or more volumes to your choice of IOPS level. If any of the volumes is greater than 200 GB, then you cannot have a target tier as Fixed IOPS.
  • Deploy the boot volume of a virtual server instance in any of the supported IOPS levels. Additional data volumes that are attached to the new virtual server instance can have different IOPS levels from that of the boot volume of an instance.
  • Import an image from IBM Cloud Object Storage to any of the supported IOPS levels.

Best practice for an image import is to use the default IOPS level (Tier 3). While deploying the image you can choose the IOPS level for your boot volume during virtual server instance deployment, the boot volume's IOPS level does not need to match the IOPS level of the image.

Selecting a storage tier

Flexible IOPS allows you to select your desired tier for:

  • Boot volume
  • Data volume

Boot volume When you are creating a virtual server instance, you can define the boot volume by performing the following steps:

  • Select your desired Operating system.
  • Select or clear the Configure for Epic workloads indicator.
  • Select your desired Image.
  • Select from Tier 0, Tier 1, Tier 3, or Fixed IOPS.
  • For Storage pool, select from Auto-select pool, Affinity, Anti-affinity.
Table 5. Storage pool affinity setting
VM storage pool affinity setting Action
Auto-select pool Power Virtual Server determines the best storage pool available for you.
Affinity The storage pool must be similar to the storage pool of affinity object that you choose.
Anti-affinity Storage pool makes the storage pool of affinity object that you choose as an exception.

All volumes that are created during VM provisioning are created on the same storage pool as the boot volume irrespective of their tier selection.

Data volume To create a volume, complete the following steps:

  • Enter a unique name.
  • Enter the desired size of the volume.
  • Enter the quantity of volumes that you need.
  • Select from Tier 0, Tier 1, Tier 3, or Fixed IOPS.

During VM provisioning, if you create additional data volumes to attach to the new virtual server instances then these data volumes can be created on any of the supported storage tiers. All these additional data volumes reside in the same storage pool where the boot volume of the virtual server instance resides.

Limitations of flexible IOPS

Some of the limitations of flexible IOPS are as follows:

  • Snapshot data cannot be changed from one tier to another. All volumes of a snapshot must reside in the same storage pool.
  • Any volume that has a storage type of tier 0, tier 1, or tier 3 and the volume size is greater than 200 GB then the option to change to Fixed IOPS is not allowed.

Public and private networks

When you create a Power Virtual Server, you can select a private or public network interface.

Public network

  • Easy and quick method to connect to a Power Virtual Server instance.
  • IBM configures the network environment to enable a secure public network connection from the internet to the Power Virtual Server instance.
  • Connectivity is implemented by using an IBM Cloud Virtual Router Appliance (VRA) and a Direct Link Connect connection.
  • Protected by a firewall and supports the following secure network protocols:
    • SSH
    • HTTPS
    • Ping
    • IBM i 5250 terminal emulation with SSL (port 992)

Private network

  • Allows your Power Virtual Server instance to access existing IBM Cloud resources, such as IBM Cloud Bare Metal Servers, Kubernetes containers, and Cloud Object Storage.
  • Uses a Direct Link Connect connection to connect to your IBM Cloud account network and resources.
  • Required for communication between different Power Virtual Server instances.

For more information about the different options for configuring a private network, see Configure a private network.


  1. SAP Netweaver is not certified for S1022 systems and hence is limited to non-production workloads. ↩︎