IBM Cloud Pak System - Red Hat Virtualization

IBM Contents

IBM Cloud Pak System - Red Hat Virtualization documentation...... 1 Introduction to Red Hat Virtualization on IBM Cloud Pak System...... 1

Administering the system for Red Hat Virtualization...... 2 Administering users and security...... 2 Console overview for Red Hat Virtualization...... 2 Administering compute nodes and cloud resources for Red Hat Virtualization...... 2 Administering hardware resources for Red Hat Virtualization...... 3 Managing instances for Red Hat Virtualization...... 4 Configuring the system for Red Hat Virtualization...... 4 Configuring the virtual manager external IP address for Red Hat Virtualization...... 4 External Applications for Red Hat Virtualization...... 5 Managing auditing for Red Hat Virtualization...... 7 Backup and restore for Red Hat Virtualization...... 7 Cloud Pak System Software Administrative Interface for Red Hat Virtualization...... 7 Manage machine type models (MTMs) for Red Hat Virtualization...... 7 Verify system initialization after power-on for Red Hat Virtualization...... 8

Working with virtual patterns for Red Hat Virtualization...... 8

Working with IBM Cloud Pak System user interface for Red Hat Virtualization...... 8

Monitoring hardware resources for Red Hat Virtualization...... 8

Command line reference for Red Hat Virtualization...... 8

REST API reference for Red Hat Virtualization...... 8

Troubleshooting and support for Red Hat Virtualization...... 9 Features not supported on IBM Cloud Pak System - Red Hat Virtualization...... 9 Collecting logs from Red Hat Virtualization...... 9 Known issues and limitations for Red Hat Virtualization...... 10

ii IBM Cloud Pak System - Red Hat Virtualization documentation

Welcome to the IBM Cloud Pak System - Red Hat Virtualization documentation, where you can find information about how to administer, maintain, or use Red Hat Virtualization. This information applies to the Version 2.3.2.0 interim fix release. The content in the existing IBM Knowledge Center documentation applies to IBM Cloud Pak System that is based on VMware hypervisor for virtualization. This document highlights information about Red Hat Virtualization (RHV) hypervisor-based IBM Cloud Pak System. Other than virtualization, IBM Cloud Pak System operations on other components are common for both hypervisors, which are discussed in the IBM Knowledge Center documentation. Attention: Cloud Pak System Software is a mandatory prerequisite for IBM Cloud Pak System. Cloud Pak System Software is a system to help you manage resources in a cloud-computing environment. It can be placed in a data center to dispense applications and topologies into a pool or cloud of virtualized hardware, and to manage these resources. See the following sections or topics to find relevant information about Red Hat Virtualization.

Introduction to Red Hat Virtualization on IBM Cloud Pak System This documentation provides introduction information about Red Hat Virtualization on IBM Cloud Pak System and how to create and manage a modular private cloud by using Red Hat Virtualization based hypervisor on IBM Cloud Pak System. Version 2.3.2.0 interim fix of IBM Cloud Pak System supports the use of Red Hat Virtualization (RHV) as a hypervisor. Red Hat Virtualization is installed on the compute nodes and these nodes are managed by Red Hat Virtualization Manager, which is part of the Platform System Manager on IBM Cloud Pak System. With Version 2.3.2.0 interim fix, customers can order any of the following IBM Cloud Pak System models and have workload virtualization as Red Hat Virtualization - Bring your own license (BYOL): • W3500 • W3550 The new system with IBM Cloud Pak System comes preconfigured from the factory and is installed with the Version 2.3.2.0 interim fix for Red Hat Virtualization and Red Hat Virtualization Manager. Attention: Version 2.3.2.0 interim fix is not applicable for VMware versions of IBM Cloud Pak System. The subscription for these products is available only as Bring your own license (BYOL). You must have the subscription details available before the system can be configured and used. The subscriptions are configured as part of setting up IBM Cloud Pak System at customer premises. The following list is a summary of key features for this release: • Manage compute nodes, storage, and network. • Compute node up-sizing and lifecycle management. • Storage available through IBM Cloud Pak System SAN for virtual machines to use. • Network support for VLANs and IP pools. • Create, delete, or modify - Cloud groups, environment profiles. • Create, delete, modify, or manage the states for Red Hat Enterprise Linux® (RHEL) Version 7 based OS virtual machines.

IBM Cloud Pak System - Red Hat Virtualization documentation 1 Administering the system for Red Hat Virtualization

Administering the system for Red Hat Virtualization includes configuring settings, users and groups, scheduled tasks, and monitoring capabilities. For more information, see Administering the system. Attention: Before you administer the system for Red Hat Virtualization, see “Known issues and limitations for Red Hat Virtualization” on page 10.

Administering users and security for Red Hat Virtualization You can manage users, user groups, user credentials, access levels, and many other operations in the system for Red Hat Virtualization.

Before you begin For more information, see Administering users, user groups, and security.

Console overview for Red Hat Virtualization The console is a unified interface that provides system management and administration for integrated products in IBM Cloud Pak System for Red Hat Virtualization. For more information, see Console overview.

Administering compute nodes and cloud resources for Red Hat Virtualization In Red Hat Virtualization, you can administer compute nodes, cloud groups, environment profiles, IP groups, and others.

Adding compute nodes to a system New compute nodes can be added to IBM Cloud Pak System whenever you want additional compute nodes. The IBM Engineer does the operation of adding new compute nodes. When compute nodes are added to the system, it is registered to the Red Hat Virtualization Manager through the IBM Cloud Pak System Platform System Manager. Also, before the compute node is registered to Red Hat Virtualization Manager, all the data domain's LUNs are mapped to the compute node. This registration ensures accessibility of all the data domains under the datacenter.

Adding compute nodes to a cloud group To add a compute node, do these steps: 1. Access the console pane. Click Cloud > Cloud Groups. 2. From the list of available cloud groups, select the one to which you want to add the compute node. 3. Select a compute node from the Add more... list to add it to the cloud group. No compute nodes to add indicates that there are no available compute nodes to add to the cloud group.

Removing compute nodes from a cloud group To remove a compute node, do these steps: 1. Access the console pane. Click Hardware > Compute Nodes.

2 IBM Cloud Pak System - Red Hat Virtualization 2. Select the compute node, which you want to remove. 3. Put the compute node into Quiesce mode. 4. Put the compute node into maintenance mode. 5. Click Cloud > Cloud Groups. 6. From the list of available cloud groups, select the one from which you want to remove the compute node. 7. In the Compute nodes section, select the compute node that you moved to maintenance mode in step “4” on page 3. 8. Click the Delete icon to remove the compute node from the cloud group. Click OK to confirm that you want to remove the compute node. 9. Click Job Queue to open the Job Queue page for the compute node. For more information, see Removing compute nodes from cloud groups.

Reinitialize a compute node To reinitialize a compute node, do these steps: 1. Click Hardware > Compute Nodes. 2. Select the compute node that you want to initialize. 3. Put the compute node into Quiesce mode. 4. Put the compute node into maintenance mode. 5. Click the Initialize icon on the toolbar. For more information, see Initializing compute nodes.

Administering cloud groups You can add, view, edit, or remove cloud groups. Use the Cloud > Cloud Groups menu to administer cloud group resources. For more information, see Administering cloud groups.

Administering environment profiles You can add, edit, clone, or delete environment profiles. Use the console to administer environment profiles in the system. For more information, see Administering environment profiles.

Administering IP groups You can create, delete, or edit IP groups in the system. For more information, see Administering IP groups. Attention: Administering an IP group for a compute node is not supported. You cannot assign public IPv4 address to a compute node.

Administering hardware resources for Red Hat Virtualization Use this menu to administer the hardware resources in the system, including compute nodes, management nodes, storage devices, and network devices.

Before you begin Attention: Before you administer any hardware resources in the system, refer to the following points about Red Hat Virtualization: • The feature to increase the size for a datastore is not supported.

Administering the system for Red Hat Virtualization 3 • System-level HA is not supported. For more information, see Administering hardware resources.

Managing instances for Red Hat Virtualization You can use the console to manage virtual system instances that are deployed in your cloud.

Before you begin Attention: In Red Hat Virtualization, the Patterns > Virtual System Patterns option is supported from the Instance Dashboard of the IBM Cloud Pak System console. For more information, see Managing instances.

Configuring the system for Red Hat Virtualization You can configure auditing, settings, the job queue, events, troubleshooting, and product licenses.

Before you begin For more information, see Configuring the system.

Configuring the virtual manager external IP address for Red Hat Virtualization Configure this IP address to provide external access to the virtual manager for Red Hat Virtualization.

Before you begin Attention: Make a note of the user-configured IPv4 address to use it whenever you want to access the Red Hat Virtualization Manager. The configured information is lost when you return to the Virtual Manager external IP address page again. For more information, see Configuring the virtual manager external IP address before you configure this IP address.

Procedure 1. Click System > Network Configuration. 2. In the System Management IP section, verify that the IPv4 IP addresses are defined. 3. Under Optional, click Virtual Manager external IP address. 4. Select the Configure IPv4 addresses checkbox. The Netmask and Gateway fields are pre-defined with information that is obtained from the System Management IP section. 5. In the Virtual Manager FQDN field, type rhvm, which is the fully qualified domain name (FQDN) for the Red Hat Virtualization Manager.

Attention: In a Red Hat Virtualization-based IBM Cloud Pak System, changing the Virtual Manager FQDN is not supported in this release. The default hostname that is configured on the Red Hat Virtualization Manager virtual machine is rhvm. Use it as the FQDN when you assign an IP address to the Red Hat Virtualization Manager. 6. In the Virtual Manager IP address field, type the external IP address for the virtual manager. Specify an IP address that is in the same subnet as the ones provided in the System Management IP section. 7. Click Save. 8. Check the job from System > Job Queue and wait for the job to successfully complete.

4 IBM Cloud Pak System - Red Hat Virtualization Name: network configure Type: global_config

External Applications for Red Hat Virtualization External applications are groups of user account credentials that allow external access to the virtual manager, compute nodes, and storage controller of the system. Configuring access for external applications enables the following functions for a system with Red Hat Virtualization enabled: • Use the IBM Cloud Pak System console for operations to create, update, or delete resources (Datacenters, Clusters, Compute Nodes, Networks, Storage, Virtual Machines). Do not run any out of band management actions from Red Hat Virtualization Manager for these resources. • For any other operation that you want to do directly on the Red Hat Virtualization Manager, contact IBM Support for guidance. To allow access for these components, each one of them must be made available outside of the system with an external IP address (IP address that is not provided by IBM Cloud Pak System). Attention: In this release: • Only a single user with SuperUser privileges is pre-defined for use. The External Applications must use the same user to access the Red Hat Virtualization Manager web console or the Secure Shell. • A single user with SuperUser privileges works only until Red Hat Virtualization Manager is recreated. If Red Hat Virtualization Manager is recreated, the existing user cannot be used to ssh to Red Hat Virtualization Manager. Therefore, a new user must be created. For more information, see External Applications.

Accessing Red Hat Virtualization Manager Complete these steps to access Red Hat Virtualization Manager that is running on IBM Cloud Pak System.

Before you begin Note: Red Hat Virtualization does not support IBM® Tivoli® Monitoring.

About this task Attention: In this release, only a single user with SuperUser privileges is pre-defined for use. More than one user creation is not supported. The External Applications must use the same user to access the Red Hat Virtualization Manager web console or the Secure Shell. For more information, skip to “Viewing and regenerating passwords for external applications” on page 6.

Procedure 1. Set up an IP address to allow external access to Red Hat Virtualization Manager. For more information, see “Configuring the virtual manager external IP address for Red Hat Virtualization” on page 4. 2. Create a user ID that is used for external access to Red Hat Virtualization Manager. For more information, see “Configuring external application access for Red Hat Virtualization” on page 6. 3. Select the following options when you create the user. • Set the Access Scope to Everything. • For the Virtual Manager Privilege Set, select Default. After you create the user, click Show Details in the Actions column. Make a note of the Virtual Manager IP address, username, and the password. To view or regenerate the passwords, see “Viewing and regenerating passwords for external applications” on page 6.

Administering the system for Red Hat Virtualization 5 What to do next You can access Red Hat Virtualization Manager by using one of the following methods: Web console for Red Hat Virtualization Manager Open https://rhvm/ovirt-engine from a web browser to access the web console for Red Hat Virtualization Manager. Use the username and password from step “3” on page 5 to authenticate. SSH Access the Red Hat Virtualization Manager that is running on IBM Cloud Pak System through SSH by using the following command:

ssh @

Provide the password from step “3” on page 5 when indicated. External application Configure an external application to monitor the Red Hat Virtualization Manager that is running on IBM Cloud Pak System hostname rhvm (for API and web console) or Virtual Manager IP address (for SSH), username, and password. See step “3” on page 5 for those attribute values.

Configuring external application access for Red Hat Virtualization Use external application access settings to gain access to internal components such as the virtual manager, and storage controllers.

Before you begin You must be assigned the Hardware administration role with permission to Manage hardware resources (Full permission) to perform these steps.

About this task An external application represents a set of users that grant access to internal components such as the virtual manager and storage controllers. You can use the console, the command line interface, or the REST API to complete this task. For the command line and REST API information, see the Related information section.

Procedure 1. Click System > System Settings. 2. Expand External Application Access Settings. 3. To create an external application, click Create. This action opens a dialog box for creating the external application. a) Specify the Name to uniquely identify the external application. b) Select Everything from the Access Scope list. All Virtual Manager resources such as compute nodes and hosts are included in this scope selection. In this release, Cloud Groups Access Scope is not supported. c) Select Default from the Virtual Manager Privilege Set list to grant a set of privileges for Virtual Manager resources. The Default privilege set grants SuperUser privileges to the user. d) Select Grant Storage Access to indicate whether external users are created for access to storage controllers.

Attention: Grant Compute Nodes Access is not supported in this release.

4. To delete an external application access, click Delete in the Actions column. 5. To view the list of external users, click Show details in the Actions column.

Viewing and regenerating passwords for external applications View and regenerate passwords for external applications from the console.

6 IBM Cloud Pak System - Red Hat Virtualization Before you begin Complete the steps in “Configuring external application access for Red Hat Virtualization” on page 6.

About this task Complete the steps in this task to retrieve or regenerate the password for those user accounts.

Procedure 1. Click System > System Settings. 2. Expand External Application Access Settings. 3. Click Show details in the Actions column. 4. Click Show passwords to view the passwords, or click Regenerate passwords to create new passwords.

Managing auditing for Red Hat Virtualization You can use the auditing function to record activity about administrative and security-related events that occur on the system.

Before you begin For more information, see Managing auditing.

Backup and restore for Red Hat Virtualization You can back up and restore the Platform System Manager's system configuration data in the IBM Cloud Pak System environment. You can run scheduled backups or run backups on demand, and restore backed up data as needed. Daily Red Hat Virtual Management database backups are available only on that Platform System Manager on which it was backed up. It is important when a Platform System Manager failover occurs. The local Red Hat Virtual Management database backups are not available on the new leader Platform System Manager and must be manually copied from the other Platform System Manager if a restore is to be done. The Red Hat Virtual Management database backups are saved at /data/hdd-files/backup/daily/ rhvmdb/rhvmdb.bac.gz. This path is not saved on a shared/ mapped disk. Therefore, the local Red Hat Virtual Management database backups are available on a specific Platform System Manager only. For more information, see Managing backup and restore.

Cloud Pak System Software Administrative Interface for Red Hat Virtualization The Cloud Pak System Software Administrative Interface provides command-line utilities for managing and troubleshooting the Platform System Managers. For more information, see Cloud Pak System Software Administrative Interface.

Manage machine type models (MTMs) for Red Hat Virtualization Power off or power on machine type models (MTMs) based on your requirements for Red Hat Virtualization.

Administering the system for Red Hat Virtualization 7 For more information, see these topics: • Powering off W3550 MTMs • Powering on W3550 MTMs

Verify system initialization after power-on for Red Hat Virtualization Verify system initialization after you power-on IBM Cloud Pak System for Red Hat Virtualization. For more information, see Verifying system initialization after power-on.

Working with virtual patterns for Red Hat Virtualization

Virtual patterns enable efficient and repeatable deployments of systems that include one or more virtual machine instances, and the applications that run on them. For more information, see Working with virtual patterns.

Working with IBM Cloud Pak System user interface for Red Hat Virtualization

You must use the IBM Cloud Pak System Administration console for your requirements. For more information, see Console overview.

Monitoring hardware resources for Red Hat Virtualization

Monitor various hardware devices included in the system. For more information, see Monitoring hardware resources.

Command line reference for Red Hat Virtualization

Use the command-line interface to perform administrative functions. Download the command-line interface from the Welcome page in the console to your local computer. You can then run the command-line interface from your local machine to connect to IBM Cloud Pak System and run commands remotely. For more information, see Command line reference.

REST API reference for Red Hat Virtualization

The representational state transfer (REST) application programming interface (API) is provided by the system. Each system exposes a REST API as there are no special configuration settings to enable or disable this interface. For more information, see REST API reference.

8 IBM Cloud Pak System - Red Hat Virtualization Troubleshooting and support for Red Hat Virtualization

Use troubleshooting information to isolate and resolve issues for Red Hat Virtualization. For more information, see Troubleshooting and support.

Features not supported on IBM Cloud Pak System - Red Hat Virtualization IBM Cloud Pak System - Red Hat Virtualization does not support some features as part of the Version 2.3.2.0 interim fix release. The features that are not supported are as follows: • System level High Availability (HA) • High Availability (HA) pool • Organization profiles • Storage volumes • Storage volume groups • Disaster recovery • Callhome • Fix pack upgrade • Pattern: Add-ons, component policies, script packages, import, export, lock • Instance store, snapshot, management inlet, upgrade or update, mark or unmark option, maintain, scale, manage, resume • Monitoring and operation under Manage tab • Virtual machine management, which includes virtual machine power-on, power-off, restart, and configure. • All shared services • Virtual image management – Images that are cloned cannot be used for deployment. – Images cannot be extended (and hence cannot be captured). • Actions under Manage • Virtual machine deployment by using SSH key access • Capabilities on Virtual System Instance > Instance Console page.

Collecting logs from Red Hat Virtualization Red Hat Virtualization provides a tool to collect logs and technical support data from the system. You must log in to Red Hat Virtualization Manager shell to collect all logs from the Red Hat Virtualization Manager and its attached hosts. For more information about how to log in to Red Hat Virtualization Manager shell, see ssh in “Accessing Red Hat Virtualization Manager” on page 5. To gather log files and technical support data, run the following command on Red Hat Virtualization Manager shell:

# sudo /usr/local/bin/collect-logs.sh

Specify the user password while it gathers logs from the attached hosts. Provide the same password, which you specified in “Accessing Red Hat Virtualization Manager” on page 5.

Troubleshooting and support for Red Hat Virtualization 9 The snippet of a sample command run is as follows:

[rhvm_user_3f8e189a@rhvm ~]$ sudo /usr/local/bin/collect-logs.sh This command will collect system configuration and diagnostic information from this system. The generated archive may contain data considered sensitive and its content should be reviewed by the originating organization before being passed to any third party. No changes will be made to system configuration. Please provide the REST API password for the %rhvm_user_3f8e189a@internal oVirt Engine user (CTRL+D to skip):

Note: • The collected logs are placed in an archive file under /tmp directory of Red Hat Virtualization Manager. Due to limited disk space, every time this script is run, it clears all the previously collected logs or reports. Copy the previously collected files to a backup location, if required.

Known issues and limitations for Red Hat Virtualization This documentation describes the known issues and limitations for Red Hat Virtualization.

Snapshot feature is not supported The Snapshot feature is not supported for Red Hat Virtualization. Therefore, it is not enabled from the IBM Cloud Pak System console.

Creating a volume is not supported The feature to create a volume is not supported from Cloud > Volumes on the IBM Cloud Pak System console for Red Hat Virtualization. Therefore, the Create New option is not enabled.

Importing volume data is not supported The feature to import volume data is not supported from Cloud > Volumes on the IBM Cloud Pak System console for Red Hat Virtualization. Therefore, the Import option is not enabled.

Virtual Manager Cloud Group (VMCG) is not supported VMCG is not supported for Red Hat Virtualization.

Workload category component types are not supported All the Workload category component types in the Component backup type list on the Backup Profiles - Create new configuration window of the Backup and Restore page are not supported for Red Hat Virtualization.

Unsupported components are listed for Virtual System Pattern Type on Pattern Types page From the Pattern Types page of the IBM Cloud Pak System console for Red Hat Virtualization, the Virtual System Pattern Type list displays components that are not supported. For example, some of them are as follows: • Allocate directories on the GPFS shared file server • GPFS Client Install for off-rack GPFS Server • GPFS Client Operations • IEM Client Windows And, more components. Use only the supported components from the Virtual System Pattern Type list that are applicable for Red Hat Virtualization.

10 IBM Cloud Pak System - Red Hat Virtualization RHEL Virtual System Pattern RHV is available With Red Hat Virtualization deployment, RHEL Virtual System Pattern RHV is available. It is the standard OS pattern for RHEL Version 7.7 with single node, which is similar to VMware RHEL Version 7.7.

Dedicated cloud group types are supported Only Dedicated cloud group types are supported for Red Hat Virtualization.

IP group for a compute node is not supported Administering an IP group for a compute node is not supported for Red Hat Virtualization. You cannot assign public IPv4 address to a compute node.

Quiesce option does not work The Quiesce option on the Compute Nodes page of the IBM Cloud Pak System console does not work, as this operation is not applicable for Red Hat Virtualization.

Console icon does not work The Console icon in the toolbar does not work, as it is not applicable or supported for Red Hat Virtualization.

Mismatch volume placement is reported in Health check report Some mismatch volume is reported in the Health check information report for Red Hat Virtualization. The following error is displayed in the Volumes section of the IBM Cloud Pak System console:

Status: Failed Description: The number of mismatching volume placements Value: 1 Expected: 0

This issue is a known limitation. Contact IBM Support for guidance.

Instance deployment is triggered even if Virtual CPU limit exceeds If you set a Virtual CPU limit for an environment profile under Environment limits and deploy the instance, the instance deployment still gets triggered even if its Virtual CPU limit exceeds the Environment Profiles CPU limit. However, the deployment process fails later and the following message is displayed:

The environment profile will exceed the maximum CPU capacity.

This issue is a known limitation. Contact IBM Support for guidance.

Events not generated Events are not generated when the high availability management node unexpectedly switches the leadership to the other node or when the services (79,81) fail offline. If the state of the management node is not available for a long time, collect the management logs, and contact IBM Support.

Higher vCPU values might cause virtual machine errors If virtual machines with higher values of vCPU are deployed, the specified limit (16 CPU) on a given compute node might cause system errors when you start the virtual machine.

More pattern instance deployments might cause virtual machine errors The maximum number of pattern instance deployments (of a simple OS pattern with 1 CPU) in the Dedicated cloud group type that is supported is 10. Deploying more pattern instances than the supported

Troubleshooting and support for Red Hat Virtualization 11 range and starting the virtual machine might cause errors due to a known limitation. Contact IBM Support for guidance.

VMware or ESXi license keys listed on IBM Cloud Pak System console are not supported The values for vCenter key and ESXi key under Vmware licenses on the IBM Cloud Pak System console display as none or are empty. These keys are not applicable to Red Hat Virtualization and must be ignored.

Setting Password field value as password is not supported when you edit a pattern When you edit a pattern, do not set the user password as password. Setting this value results in an error with the following message:

The input value for property Password (root) is not valid and has been changed to the previous value

Set any other value for the Password field.

Collection of system logs for compute node and virtualization management is not supported From the IBM Cloud Pak System console, the System > System troubleshooting > System Logs option collects system logs of all the nodes in IBM Cloud Pak System. However, collection set of system logs does not include the hypervisor support logs from the compute node and from Red Hat Virtualization Manager. These logs can be collected manually. For more information about how to manually collect these logs, see “Collecting logs from Red Hat Virtualization” on page 9.

CPU and memory upgrade from Manage option for virtual machines in maintenance mode is not allowed Currently, CPU and memory update for Red Hat Virtualization instances or virtual machines in maintenance from the Manage option on the IBM Cloud Pak System console is not supported. The following error messages are displayed in the History section: For CPU upgrade

Failed to change CPU for virtual machine VM_NAME from Current number of cores to New number of cores

For memory upgrade

Failed to change memory for virtual machine VM_NAME from Current memory capacity to New memory capacity

This issue is a known limitation. Contact IBM Support for guidance.

Stopped virtual machines are not moved when the compute node is powered off When the compute node is powered off, it is shut down successfully. However, the stopped virtual machines are not moved to another compute node in the cloud group. Only those virtual machines that are in Running state are evacuated or moved. This issue is a known limitation. To address this issue, click Maintain on the Compute Node page to move the compute node to Maintenance mode. This action moves the stopped virtual machines out of the compute node.

Virtual machine deployment fails after a full system restore The virtual machine deployment fails if the virtual machine is deployed within 60 minutes after a successful system restore. The virtual instance is stuck in Launching status and the virtual machine remains in Starting status. The virtual machine deployment works after 60 minutes. This issue is a known limitation. Contact IBM Support for guidance.

12 IBM Cloud Pak System - Red Hat Virtualization

IBM®