--- name: power-iaas-configuring-custom-image title: Deploying a custom image within IBM Power Virtual Server description: You can bring your own customized AIX or IBM i operating system (OS) image to deploy within an IBM® Power® Virtual Server. last-updated: 2026-08-11 --- > ## Documentation Index > The table of contents for this documentation set is at https://cloud.ibm.com/docs/power-iaas?format=markdown > The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt > Use these files to discover more information as needed. # Deploying a custom image within IBM Power Virtual Server {: #deploy-custom-image} --- IBM Power Virtual Server in [IBM data center]{: tag-blue} IBM Power Virtual Server Private Cloud in [Client location]{: tag-red} --- You can bring your own customized AIX or IBM i operating system (OS) image to deploy within an IBM® Power® Virtual Server. {: shortdesc} You cannot transfer an OS license from a private cloud system to a Power Virtual Server. The license cost is factored into the overall hourly billing rate. {: note} The basic steps that are involved in deploying an instance by using a custom image are: 1. Create the custom image. 2. Store the image in your **Cloud Object Storage** account. 3. Point the Power Virtual Server console to the image in the **Cloud Object Storage** and deploy the Virtual Server instance. ## Before you begin {: #before-you-begin-deploy} Before you can use a custom image as the boot volume, review the following information: - You must have a basic understanding of [IBM Cloud Object Storage](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-about-cloud-object-storage&format=markdown){: external} concepts. - If you do not have an existing AIX or IBM i image, you can use IBM® PowerVC™ from your private cloud environment to capture and export an image for use with a Power Virtual Server. For more information, see [Capturing a virtual machine](https://www.ibm.com/docs/en/powervc/2.0.1?topic=images-capturing-virtual-machine){: external} and [Exporting images](https://www.ibm.com/docs/en/powervc/2.0.2?topic=init-installing-configuring-cloud-linux){: external}. To capture and export an image by using IBM PowerVC, the PowerVC private environment must contain N_Port ID Virtualization (NPIV) data volumes. The Power Virtual Server does not support captured images from environment with shared Storage Pools (SSP) vSCSI data volumes. - Alternatively, if you have deployed a virtual server instance, you can capture it and redeploy a new virtual server instance. To accomplish this, you can use the [IBM Cloud® CLI](https://cloud.ibm.com/docs/cli?topic=cli-getting-started&format=markdown){: external} to capture a virtual server instance. - You must verify that your AIX, IBM i, or Linux OS technology level is supported on the Power hardware that you selected in the **Machine Type** field. For complete tutorials on migrating your AIX and IBM i workloads to Power Virtual Server, see [Migration strategies for AIX](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-migration-aix&format=markdown) and [Migration strategies for IBM i](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-migration-strategies-power&format=markdown). The supported AIX and IBM i operating system versions depend on the IBM Power hardware that you select for the Power Virtual Server. If you are running AIX 6.1 or IBM i 6.1, or earlier, you must first upgrade the OS to the current support level before you migrate to the Power Virtual Server. {: important} To view a list of the supported AIX, IBM i, and Linux operating system technology levels, see the following information: ### AIX {: #aix-details} The Power Virtual Server offering supports the following versions of AIX operating system depending on the IBM Power server: [IBM data center]{: tag-blue} | Machine type | Supported AIX versions | | ---------------------------------------- | ----------------------------------------------------- | | * S922 (9009-22A) \n * E980 (9080-M9S) | AIX 7.1 or later | | * E1080 (9080-HEX) \n * S1022 (9105-22A) | AIX 7.1 TL5 or later | | * S1122 (9824-22A) | AIX 7.2 TL5 SP8 \n AIX 7.3 TL2 SP2 \n AIX 7.3 TL3 SP0 | {: caption="Supported AIX versions in IBM data center" caption-side="bottom"} [Client location]{: tag-red} | Machine type | Supported AIX versions | | -------------------------------------------------------------- | ----------------------------------------------------- | | * S1122 (9824-22A) \n * E1150 (9043-MRU) \n * E1180 (9080-HEU) | AIX 7.2 TL5 SP8 \n AIX 7.3 TL2 SP2 \n AIX 7.3 TL3 SP0 | {: caption="Supported AIX versions in client location" caption-side="bottom"} 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 more information about which versions of AIX are compatible with various Power Systems, see the [System to AIX maps](https://www.ibm.com/support/pages/node/6020074){: external}. For more information about end of service pack support (EoSPS) dates, see [AIX support lifecycle](https://www.ibm.com/support/pages/aix-support-lifecycle-information){: external}. {: note} ### IBM i {: #ibmi-details} If you are using an older version of IBM i, you must upgrade the OS to a current support level and then migrate to Power Virtual Server. For more information about upgrading the IBM i OS, see [Fast path for software installation, upgrade, and deletion tasks](https://www.ibm.com/docs/en/i/7.6.0?topic=software-fast-path-installation-upgrade-deletion-tasks){: external}. For more information about the supported IBM i OS levels, see [IBM i Release Support](https://www.ibm.com/support/pages/ibm-i-release-support){: external}. [IBM data center]{: tag-blue} | Machine type | Supported IBM i versions | | ---------------------------------------- | ------------------------ | | * E1022 (9105-22A) \n * E1080 (9080-HEX) | IBM i 7.3 or later | {: caption="Supported IBM i versions in IBM data center" caption-side="bottom"} [Client location]{: tag-red} | Machine type | Supported IBM i versions | | ---------------------------------------- | ------------------------ | | * S1122 (9824-22A) \n * E1180 (9080-HEU) | IBM i 7.4 or later | {: caption="Supported IBM i versions in client location" caption-side="bottom"} The IBM Power Virtual Server in Client location supports IBM i 7.4, or later and IBM i COR. {: note} For more information, see: - [S1022 (9105-22A) IBM i software map](https://www.ibm.com/support/pages/system-ibm-i-mapping){: external} - [E1080 (9080-HEX) IBM i software map](https://www.ibm.com/support/pages/system-ibm-i-mapping){: external} - [S1122 (9824-22A) IBM i software map](https://www.ibm.com/support/pages/system-ibm-i-mapping){: external} - [E1180 (9080-HEU) IBM i software map](https://www.ibm.com/support/pages/system-ibm-i-mapping){: external} Learn more about the [IBM i PTF minimum levels](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-minimum-levels&format=markdown) and [IBM i release lifecycle](https://www.ibm.com/support/pages/release-life-cycle){: external} IBM i 7.3, and later, supports up to 127 storage volumes per VM. IBM i 7.3 VSIs are at the end of support and are in service extension. Therefore, additional Service Extension fees apply. {: note} ### Linux {: #linux-details} SUSE Linux Enterprise (SLES) and Red Hat Enterprise Linux (RHEL) are supported by the appropriate IBM Cloud environment cloud-init packages. Download the appropriate cloud-init package and perform the following steps to configure it: - [Installing and configuring cloud-init on SLES](https://www.ibm.com/docs/en/powervc/2.1.0?topic=linux-installing-configuring-cloud-init-sles){: external}. - [Installing and configuring cloud-init on RHEL](https://www.ibm.com/docs/en/powervc/2.1.0?topic=linux-installing-configuring-cloud-init-rhel){: external}. Power server E1080 (9080-HEX) and S1022 (9105-22A) supports RHEL 8.4 or later and SLES 15 SP3 or later versions. For SAP applications, ensure that you use an IBM stock OS image for SAP. These images are certified for SAP application use. To learn more about SAP applications with PowerVS, see the [Must-Reads](https://cloud.ibm.com/docs/sap?topic=sap-powervs-set-up-power-instances&format=markdown#powervs-memory-sizing-and-subscription-concepts){: external} before you start deployment. {: note} ## Creating an IBM Cloud Object Storage bucket {: #cloud-storage-bucket} 1. Type **object storage** into the catalog's search box and select **Cloud Object Storage**. 2. Give the service a name, add tags (if wanted), select your pricing plan and click **Create**. 3. After you click **Create**, you are taken to the **Cloud Object Storage** landing page. Select **Create Bucket**. 4. From here, you are automatically redirected to the workspace where you can start creating buckets. Your Object Storage instances are listed under **Storage** in the **Resource List**. The terms *resource instance* and *workspace* refer to the same concept, and can be used interchangeably. 5. Choose a unique name. All buckets in all regions across the globe share a single namespace. Ensure that you have the correct permissions to create a bucket. When you create buckets or add objects, be sure to avoid the use of Personally Identifiable Information (PII). PII is information that can identify any user (natural person) by name, location, or any other means. {: note} 6. Select **Regional resiliency** and then choose the location where you want your data to be physically stored. The **Regional resiliency** option distributes the data across multiple devices within a single metropolitan area. Currently, Power Virtual Server supports regional resiliency and one single data center, which is **che01**. The Cross Region resiliency option is not supported. 7. Choose the *storage class* of the bucket, which is a reflection of how often you expect to read the stored data and determines billing details. Follow the **Create** link to create and access your new bucket. Buckets are a way to organize your data, but they are not the only way. Object names (often referred to as object keys) can use one or more forward slashes for a directory-like organizational system. You then use the portion of the object name before a delimiter to form an object prefix, which is used to list related objects in a single bucket through the API. {: tip} Objects are limited to 200 MB when uploaded through the console unless you use the Aspera High-Speed Transfer plug-in. Larger objects (up to 10 TB of uncompressed image) can also be split into parts and uploaded in parallel using the API. Object keys can be up to 1024 characters in length, and avoid any characters that might be problematic in a web address. These special characters (*?*, *=*, *<*, and so on) might cause unwanted behavior if not URL-encoded. For more information, see the [Cloud Object Storage tutorial](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-getting-started-cloud-object-storage&format=markdown). ## Generating secret and access keys with Hash-based Message Authentication Code (HMAC) {: #access-keys} 1. You can generate secret and access keys when you create the service credentials for the IBM Cloud Object Storage. To create the service credentials, you must have `Writer` access for the **Object Storage** bucket. 2. Select **New credential** under **Service credentials** in the **Cloud Object Storage** page. 3. Complete all of the wanted fields for adding a credential. Remember to check **Include HMAC Credential** for obtaining a **Hash-based Message Authentication Code (HMAC)** credential. 4. Find your new service credential in the service credentials table. To view your credential information, such as your secret and access keys, click the arrow that is next to the **View credentials** field. For more information, see [Service credentials](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-service-credentials&format=markdown){: external} and [Bucket permissions](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-iam-bucket-permissions&interface=ui&format=markdown){: external}. ## Using a custom boot image to provision a new instance {: #upload-custom-boot} {: help} {: support} Complete the following steps to provision a new instance by using a custom boot image. For more information about importing a custom boot image by using the Power Virtual Server CLI, see [Importing a boot image](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-importing-boot-image&format=markdown#cli-import-image). Large boot images take time to successfully import. You might experience a delay before you receive a confirmation message. 1. Before you create a new Power Virtual Server instance, go to **Boot images** and click **Import**. 2. After you click **Import**, refer to the following table to complete the **Import boot image** fields: The **Image file name** field supports the following formats: *.ova*, *.ova.gz*, *.tar*, *.tar.gz* and *.tgz*. {: important} | Field | Description | | ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Catalog image name | Enter the name that you want displayed in your catalog. | | Storage type | Select whether you want **Tier 1** or **Tier 3** for the storage type. A VM cannot have disks from both **Tier 1** and **Tier 3** storage types. For more information, see [Storage tiers](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-on-cloud-architecture&format=markdown#storage-tiers). | | Region | Select the region from the drop-down list. | | Image file name | Enter the file name of the image. The image file name must not contain spaces. Supported file formats are *tar* and *ova*. You can compress image files by using *gzip*. The supported file name extensions are *.ova*, *.ova.gz*, *.tar*, *.tar.gz* and *.tgz*. You must use the private endpoint domain. For example, `Aix_7200-03-02-1846_cldrdy_112018.gz`. | | Bucket name | Sub folders can be used and specified as *bucketName/optional/folders*. Optional folders are created automatically if they don’t exist. Optional folders can be added during an [export image](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-capturing-exporting-vm&format=markdown#console-capture-export) operation to Cloud Object Storage. To identity your bucket name, select **Menu icon ![Menu icon](../icons/icon_hamburger.svg "Menu icon") > Resource list > Storage > Cloud Object Storage name > Buckets**. | | Cloud Object Storage access key | To identify your access key, select **Menu icon ![Menu icon](../icons/icon_hamburger.svg "Menu icon") > Resource list > Storage > Cloud Object Storage name > Service credentials > View credentials**. Copy the `access_key_id` value and past it into this field. | | Cloud Object Storage secret key | To identify your secret key, select **Menu icon ![Menu icon](../icons/icon_hamburger.svg "Menu icon") > Resource list > Storage > Cloud Object Storage name > Service credentials > View credentials**. Copy the `secret_access_key` value and paste it into this field. | {: caption="Importing a boot image" caption-side="bottom"} 1. Return to **Virtual server instances** and provision a new Power Virtual Server instance. Click the arrow in the appropriate boot image tile to see your custom boot image. To download your image at a later point, go to the **Resource List** in the Power Virtual Server user interface. Once there, access your **Cloud Object Storage** workspace. In the bucket where your image is stored, select the image file that you want to download and select **Download objects**. See [Download an object](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-ic-cos-cli&format=markdown#download-an-object){: external} for the Cloud Object Storage CLI command. {: tip}