IBM Cloud Docs
FAQ

FAQ

What is IBM® Power® Virtual Server?

IBM Power Virtual Server is a hosted infrastructure offering that allows you to quickly integrate with the Internet for on-demand provisioning. This offering provides a secure and scalable server virtualization environment that is built upon the advanced RAS features and leading performance of the Power Systems™ platform. The IBM Power Virtual Servers are located in IBM data centers and distinct from the IBM Cloud servers with separate networks and direct-attached storage.

What versions of AIX, IBM i, and Linux are supported?

The supported AIX, IBM i, and Linux® operating system versions depend on the IBM Power Systems hardware that you select for the Power Virtual Server: S922 (9009-22A), E980 (9080-M9S) or S1022 (9105-22A). To view a list of the supported AIX, IBM i, and Linux operating system technology levels, see the following system software maps:

AIX - The Power Virtual Server offering supports AIX 7.1, or later on the S922 (9009-22A) and E980 (9080-M9S).

Power Systems S1022 (9105-22A) supports AIX 7.1 TL 5 and later.

When you view the system software maps, refer to the AIX 7.1, AIX 7.2, and AIX 7.3 information. If you use an unsupported version, it is subject to outages during planned maintenance windows with no advanced notification given.

For information on end of service pack support (EoSPS) dates, see AIX support lifecycle.

AIX stock images currently available when you create a VM are:

  • AIX 7.3 TL2
  • AIX 7.2 TL5 SP7

IBM i - Power Virtual Server supports IBM i 7.1, or later. Clients running IBM i 6.1 must first upgrade the OS to a current support level before migrating to the Power Virtual Server. IBM i 7.2 supports direct upgrades from IBM i 6.1 or 7.1 (N-2).

IBM i stock images currently available when you create a VM are:

  • IBM i COR [1]
  • IBM i 7.5 TR3
  • IBM i 7.4 TR9
  • IBM i 7.3 TR13
  • IBM i 7.2 TR9
  • IBM i 7.1 TR11 [2]

Linux - Power Virtual Server supports Red Hat Enterprise Linux (RHEL) and SUSE Linux Enterprise (SLES) distributions. The following Linux stock images are currently available when you select Full Linux Subscription (learn more about Full Linux Subscription):

Red Hat

  • RHEL 9.2 general purpose (RHEL9-SP2) new
  • RHEL 9.2 for Sap HANA (RHEL9-SP2-SAP) new
  • RHEL 9.2 for SAP NetWeaver (RHEL9-SP2-SAP-NETWEAVER) new
  • RHEL 8.8 general purpose (RHEL8-SP8) new
  • RHEL 8.8 for SAP HANA (RHEL8-SP8-SAP) new
  • RHEL 8.8 for SAP NetWeaver (RHEL8-SP8-SAP-NETWEAVER) new
  • RHEL 8.6 general purpose (RHEL8-SP6)
  • RHEL 8.6 for SAP HANA (RHEL8-SP6-SAP)
  • RHEL 8.6 for SAP NetWeaver (RHEL8-SP6-SAP-NETWEAVER)
  • RHEL 8.4 for SAP HANA (RHEL8-SP4-SAP)
  • RHEL 8.4 for SAP NetWeaver (RHEL8-SP4-SAP-NETWEAVER)

SUSE

  • SLES 15 SP5 general purpose (SLES15-SP5)
  • SLES 15 SP5 for SAP HANA (SLES15-SP5-SAP) [3]
  • SLES 15 SP5 for SAP NetWeaver (SLES15-SP5-SAP-NETWEAVER) [4]
  • SLES 15 SP4 general purpose (SLES15-SP4)
  • SLES 15 SP4 for SAP HANA (SLES15-SP4-SAP)
  • SLES 15 SP4 for SAP NetWeaver (SLES15-SP4-SAP-NETWEAVER)
  • SLES 15 SP3 for SAP HANA (SLES15-SP3-SAP)
  • SLES 15 SP3 for SAP NetWeaver (SLES15-SP3-SAP-NETWEAVER)
  • SLES 15 SP2 for SAP HANA (SLES15-SP2-SAP)
  • SLES 15 SP2 for SAP NetWeaver (SLES15-SP2-SAP-NETWEAVER)

The S1022 systems supports RHEL 8.4 (and later) and SLES 15 SP3 (and later) versions. SAP Netweaver is not certified for use with S1022 systems, making them suitable exclusively for non-production workloads.

If you opt for a Linux subscription directly from Red Hat or SUSE, you will need to bring your own image. Power Virtual Server supports custom images for following Linux distributions:

General purpose:

  • SLES 12 SP4 or later and SLES 15 SP1 or later
  • RHEL 8.4 or later

For SAP workloads:

  • SLES 12 SP4 or later and SLES 15 SP1 or later
  • RHEL 8.1 or later

To view the certification details in the Red Hat catalog, see IBM Power System E980 (9080-M9S) and IBM Power System S922 (9009-22A). For additional support, refer to the distribution (distro). For instructions, see Installing and configuring cloud-init on Linux.

Can I use my own AIX, IBM i, or Linux image?

Yes. This function is known as bring your own image. For more information, see Deploying a custom image within a Power Virtual Server.

What versions of stock images are available?

For each major version (example: Technology Level) of the operating system (OS) that is enabled through the offering, Power Virtual Server provides a single stock image. PowerVS typically provides stock images for the last three major versions of the supported OS. Any update to the OS stock image is planned only when the image level is certified for PowerVM™ environment.

When are stock images removed from the catalog?

Any unsupported and older stock images are periodically removed from the offering. You will be notified three weeks before the images are removed.

What happens to VMs deployed using stock images that are being removed?

VMs deployed by using stock images that are being removed can continue to operate without any issues. You are recommended to follow operating system vendor’s guidelines to update the OS as needed.

What formats should I use when uploading a custom image?

Currently, you can import a custom image in the following formats: .ova, .ova.gz, .tar, .tar.gz and .tgz.

What are the available storage types in the storage area network (SAN)?

Each volume has a storage tier, which defines how many I/O operations per second (IOPS) can be started against that volume. These tiers can scale according to the size of the volume.

The following tiers are supported:

  • Tier 0 (25 IOPS/GB)
  • Tier 1 (10 IOPS per GB)
  • Tier 3 (3 IOPS per GB)
  • Fixed 5000 IOPS

If you find the storage tiers are over or under-provisioned, you can change the storage tier of an existing volume. For more information, see Storage tiers.

How do I extend my AIX rootvg?

By default, the system deploys 20 GBs for the AIX rootvg. You can extend the AIX rootvg by using the extendvg command to add a physical volume.

What's the difference between capped and uncapped shared processor performance? How do they compare to dedicated processor performance?

When deploying a VM, customers can choose between dedicated, capped shared, or uncapped shared processors for their virtual CPUs (vCPUs). The following list provides a simplified breakdown of their differences:

  • Dedicated: resources are allocated for a specific client (used for specific third-party considerations)
  • Uncapped shared: shared among other clients
  • Capped shared: shared, but resources do not expand beyond those that are requested (used mostly for licensing)

There is a core-to-vCPU ratio of 1:1. For shared processors, fractional cores round up to the nearest whole number. For example, 1.25 cores equals 2 vCPUs. For more information, see How does shared processor performance compare to dedicated processors and Processor pricing.

Table 1. Dedicated processors
Dedicated processors
The hypervisor makes a 1:1 binding of a partition’s processor to a physical processor core. Once a VM is activated, the 1:1 binding is static in that a given operating system (OS) logical thread will always run on that same physical hardware. With a dedicated processor partition, you need to size the wanted number of cores to meet the peak demand of the partition. For example, if during a typical workday the CPU consumption is around four cores, but it peaks around eight cores, you need to configure the partition with eight cores. Otherwise, you might encounter queuing delays in dispatching applications because there are not enough cores to handle the peak demand.
Table 2. Shared processors
Shared processors
For shared processors, there are two sharing modes: capped or uncapped. For a capped partition, the amount of CPU time is capped to the value specified for the entitlement. For example, the partition might consume at most 30 seconds of CPU time every minute for a capped partition with processing units set to 0.5. For an uncapped partition, the number of virtual processors defines the upper limit of CPU consumption and not the value that is specified for processing units. For example, if virtual processors are set to 3, the partition might consume 180 seconds of CPU time every minute (three virtual processors each running at 100% utilization would be three physical cores worth of CPU time). There must be unused capacity available on the server for a partition to consume more than its configured processing units.

How does my current environment compare to what's available through the Power Virtual Server?

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

How do I migrate my VM from one data center to another (WDC04 to DAL13)?

To migrate your VM from one data center to another, you must capture and export your VM to Cloud Object Storage (COS). After you successfully capture and export your VM, copy it to the COS in the destination region, then perform an import followed by a deploy.

What does VM pinning do?

You can choose to soft pin or hard pin a VM to the host where it is running. When you soft pin a VM for high availability, PowerVC automatically migrates the VM back to the original host once the host is back to its operating state. If the VM has a licensing restriction with the host, the hard pin option restricts the movement of the VM during remote restart, automated remote restart, DRO, and live partition migration. The default pinning policy is none.

What does it mean to set an affinity or anti-affinity rule?

You can apply affinity and anti-affinity policies to both VMs and volumes.

VM affinity and anti-affinity policy allows you to spread a group of VMs across different hosts or keep them on a specific host.

Volume affinity and anti-affinity policy allow you to control the placement of a new volume based on an existing PVM instance (VM) or volume. When you set an affinity policy for a new storage volume, the volume is created within the same storage provider as an existing PVM instance or volume. With an anti-affinity policy, the new volume is created in a different storage provider other than the storage provider the existing PVM instance or volume is located in.

The use of volume affinity policy (affinity or anti-affinity) requires the availability of multiple storage providers. You might experience the following errors when you use a volume affinity policy:

  • If an additional storage provider is not available to fulfill the requested policy, you might receive an error that indicates the inability to locate a storage provider to create a volume by using the requested volume affinity policy.

  • If additional storage providers exist but the storage providers do not have sufficient space to fulfill the requested policy, you might receive an error that indicates the inability to locate a storage provider with enough free capacity to satisfy the requested volume size.

How to set a PVM instance to allow attaching mixed storage?

You can now attach storage volumes to a PVM instance from different storage tiers and pools, other than the storage pool the PVM instance's root (boot) volume is deployed in. To accomplish this you must modify the PVM instance and set the new PVM instance storagePoolAffinity property to false. The PVM instance storagePoolAffinity property is set to true by default when the PVM instance is deployed and can be changed only by using the modify PVM instance API. For more information about modifying a PVM instance API, see Modify PVM Instance. Attaching mixed storage to a PVM instance has implications on the PVM instance capture, clone, and snapshot features. See Modify PVM Instance API for more details.

Does IBM provide maintenance for the AIX, IBM i or Linux operating systems?

No. It is the customer's responsibility to maintain, update, and manage the AIX, IBM i or Linux operating system.

How does licensing work for the AIX, IBM i, or Linux operating systems?

The license for the AIX and IBM i operating systems is part of the overall cost for the workspace. You cannot use an existing license that you already purchased. Refer to the AIX section to learn how to create an AIX VM.

You can use the movable IBM i (IBM i MOL) to move your existing on premises entitlements to Power Virtual Server. Contact support to know more about the IBM i MOL, see Getting help and support.

Power Virtual Server supports multiple levels of RHEL and SLES. You can either use IBM provided stock Linux images with IBM Full Linux Subscription or bring your own custom Linux image with vendor-provided subscription.

See the various versions of OSs that Power Virtual Server supports.

How does third-party licensing work?

Clients are responsible for third-party licensing.

What are the hardware specifications?

For more information, see Hardware specifications.

Do Power Virtual Servers run in a multi-tenant environment?

Yes, Power Virtual Server run in a multi-tenant environment.

Are there bare-metal options?

There are no bare-metal options. The Power Virtual Server offering focuses on virtual instances.

Can you tell me more about the snapshotting, cloning, and restoring capabilities?

Power Virtual Server provides the capability to capture full, point-in-time copies of entire logical volumes or data sets. Using IBM's FlashCopy feature, the Power Virtual Server API lets you create delta snapshots, volume clones, and restore your disks. To learn more, see Snapshotting, cloning, and restoring.

What are the key differences between a snapshot and clone?

The key differences are as follows:

Context Snapshot Clone
Definion A snapshot is a thin-provisioned group of volumes that cannot be attached to a host or accessed/manipulated. A clone is created from a snapshot and results in independent volumes which surface in the GUI and can be attached to hosts.
Primary function Revert or restore the source disks to a desired state Create a complete volume clone
Ease of creation Easy and quick process Three-step process and takes long time
Pricing Charged 30% of the regular storage rate target volume storage plus the GRS costs

See Snapshots, cloning, and restoring for more detailed information.

Is there any UI to perform snapshot or clone operations?

None. You should use the API and CLI to perform snapshot or clone operations. Using the Power Virtual Server API and command line interface (CLI) you can create, restore, delete and attach the snap-shots and volume-clones.

APIs to create snapshot and clone

CLIs to create snapshot and clone

Are there any initial snapshot requirement in terms of storage?

None. The storage is allocated on demand.

Does the snapshot and volume clone supports any safeguard policy?

None. Power Virtual Server does not (currently) provide any options to safeguarded copy (such as cyber protection).

Can you tell me more about the backup process using the PowerHA Toolkit for IBM i?

The PowerHA Toolkit for IBM i provides the 5250 user interfaces and automation to use them for backups. In a nutshell, it does the following:

  • Automates the memory flush
  • Create the volumes-clone
  • Attach the clones to a host
  • Start the host
  • kicki-off the backups
  • Move the BRMS data back to the production VM before shutting down the backup VM
  • Remove the cloned volumes.

It also allows you to quickly create an intermediate snap-shot then a volumes-clone before entering the long-running volume detach or attach phase. You have the ability to pause the process immediately before attaching volumes.

How do you set up private networks between Intel® Virtual Servers (x86) and Power Virtual Servers?

See the tutorial on IBM Power Virtual Server integration with x86-based workloads.

How do you set up customer site access to a private network by using VPN?

For a complete tutorial on site-to-site Virtual Private Network (VPN) connectivity from an on-premise environment to Power Virtual Server, see IBM Power Virtual Server Virtual Private Network Connectivity. For more information on VPN, see Managing VPN connections.

What firewall options are there around VPN connectivity?

You must set your own firewall in your IBM Cloud account.

How do you connect a server instance between two data centers (DAL13 to WDC04)?

You can use IBM Cloud Connect to connect two data centersif they are located withing US. IBM Cloud Connect is a software-defined network interconnect service that brings secure connectivity to client locations around the world.

You can use Direct Link and Transit Gateway (local & global) for connecting two data centers.

How is network bandwidth billed?

IBM Cloud Classic environment: Inbound bandwidth is unlimited and not charged. Outbound bandwidth is charged per GB tier with bandwidth offered as an allotment for each month. As an example, for your compute instances, 250 GB is included with each monthly virtual server and 20 TB is included with each monthly bare metal server. Extra bandwidth can also be purchased per packages. For more information, see Bandwidth packages.

IBM Power Virtual Server environment: Inbound bandwidth is unlimited and not charged. Bandwidth is not charged when you use a public network. If you are using a private network with DirectLink Connect, you are charged IBM Cloud Classic environment rates.

What monitoring services are available?

IBM does not provide status and performance monitoring for the Power Virtual Server. Clients must use their own on-premises tools.

What performance and capacity planning services do you provide for IBM i?

IBM uses the same tools that are on an on-premises system.

IBM i and solution certification

You can find self-certification and listing information on the IBM Global Solutions Directory.

How do I delete a workspace?

To delete a workspace (and all its resources), use the left navigation to navigate the workspace page. Find the workspace to be deleted and click on the overflow menu on the top right corner of the tile. Click Delete and confirm the request from the pull-down menu by typing Delete in the text field. Finally, click the red Delete button to initiate the request.

How do I delete a single virtual server instance?

There are two methods to delete a virtual server instance. Both deletion methods are manual processes. There is no way to delete all VSIs without deleting the workspace or deleting a subset of the virtual server instance.

  • Delete a single virtual server instance from the Virtual server instances page. Click on the overflow menu (icon with 3 vertical dots) on the far right of each virtual server instance entry on the table. From the pull-down menu, click Delete to open the delete confirmation modal. Click Delete instance to initiate the deletion request. This action cannot be undone.

  • Delete a single virtual server instance from the its details page. Navigate to the virtual server instance's details page by clicking on the virtual server instance name on the table on the Virtual server instances page. Find and click on the trash icon on the top right of the screen. Confirm the request by clicking Delete instance. This action cannot be undone.

How do I open a support ticket for the Power Virtual Server workspace?

To open a support ticket, see Getting help and support.

What are the supported databases that I can run for SAP on Power Virtual Server?

On an AIX VM, the following databases are supported:

  • IBM Db2 for LUW (Linux, UNIX, and Windows) version 10.5, or later
  • Oracle Database version 12.1.0.2, or later
  • SAP Adaptive Server Enterprise version 16.0 SP03, or later

On a Linux VM, the following database is supported:

  • SAP HANA Platform 2.0 SPS 04, or later

You can find an up-to-date list at SAP Apps on IBM Power Virtual Server.

How do I run Red Hat OpenShift Container Platform (OCP) on Power Virtual Servers?

You can find a complete tutorial at the IBM Developer site: Deploying Red Hat OpenShift Container Platform 4.x on IBM Power Virtual Servers.

What is the network latency over Direct Link?

Network latency over Direct link is less than 1 millisecond in every location. To know more about network latency, see Understanding latency.

Are we notified about any planned maintenance activities?

For planned maintenance and disruptive changes, the Power Virtual Server operations team sends you notifications at least 7 days in advance. Watch the Notifications space in the IBM Cloud dashboard for these alerts. You can receive a copy of these notifications directly in your inbox if your email is subscribed for notifications.

How do I convert existing volumes to replication enabled volumes?

You can retype the volume to toggle the replicationEnable flag of the volume using Perform an action on a Volume request. This is possible only when the volume pool of existing volume supports replication.

How can I check whether volume is already replication enabled?

You need to check the replicationEnabled attribute of the volume. A volume is replicationEnabled when it is true.

How can I check whether volume is master or auxiliary volume?

Volume is auxiliary when isAuxiliary field of volume is true. When replicationEnabled is true and isAuxiliary is false then volume is a master volume.

How can I check the serial number of my virtual server instance?

The serial number is available after you deploy your virtual server instance and you can choose to display the serial number system value.

You must pin the IBM i virtual server instances that use the IBM i licenses. If you do not pin the virtual server instances and request a migration to a different host, the serial numbers changes, and the IBM i license will not work.

What should I do If I do not see the latest information in the UI?

Consider the following if you do not see an update in the User Interface(UI):

  1. Power Virtual Server utilizes a new caching mechanism for some resources to ensure that UI refresh operations complete in a timely manner.
  2. In some scenarios out-dated information may be shown while the cache is updated, for approximately four minutes.
  3. You can refresh the page to trigger an update to the cached data, eventually leading to the updated information's display.
  4. When the DC has a heavy amount of traffic, and the cache has not been refreshed within the last four minutes, Power Virtual Server UI may display an error message. A subsequent page refresh will retrieve and display the updated information.

Why I cannot see the storage pool and tier of my boot images?

IBM improved the performance of copying a stock image into customers' accounts. As a result of this new feature, the newly copied stock image acts like an image reference, where volumes are not accessible to the user. The improved process now offers:

  1. Faster copy of stock image to your private project.
  2. The stock image cannot be exported. One can do VM capture and export on a deployed VM that uses the stock image.
  3. Storage pool and tier of a stock image shows "Empty" (API) or "Any" (UI) as VM can be deployed to any tier/pool by using the stock image.

Can I select a specific resource group when I create a cloud connection?

NO. When you create a cloud connection by using Power Virtual Server, the cloud connection is always created in the default resource group even if you choose a specific resource group.

What is the Maximum Transmission Unit (MTU) size supported in Power Virtual Server networks?

The Power Virtual Server supports a smaller MTU size of 1476 bytes for the public network interfaces and for the private network interfaces that are attached to a Power Virtual Server VPN.

Can I automate the Maximum Transmission Unit (MTU) configuration?

Yes, you can automate the network configurations such as the Maximum Transmission Unit (MTU).

To automate the MTU configuration, you need to customize your cloud-init network configuration. For more information, see the Cloud-init docs on network configuration.

Both AIX and IBM i supports custom cloud-init configurations at the time of Power Virtual Server instace (VM) deployment.

You can customize the cloud-init configurations only through the Power Virtual Server API. The custom cloud-init is specified by the userData request parameter. For more information, see Create a new Power VM Instance.


  1. IBM i Cloud Optical Repository (COR) is a virtual image that can be deployed and used as a Network File Server (NFS) to perform various IBM i tasks that require media. For more information on COR images, see Cloud Optical Repository. ↩︎

  2. Starting May 1, 2024, IBM i 7.1 is End of Life and no support will be made available. IBM i 7.1 stock images will also become unavailable from Power Virtual Server data centers. ↩︎

  3. Install insserv package as a prerequisite. ↩︎

  4. Install insserv package as a prerequisite. ↩︎