Stopping and storing classic virtual system instances

You can stop and optionally store a classic virtual system instance without removing it from the system. If you stop a classic virtual system instance from running, the system still manages its associated resources, and you can redeploy the classic virtual system instance at a later time.

Before you begin

Note: The Virtual System Patterns (Classic) is not supported in IBM Cloud Pak System Software version 2.3.5 and later.

You must be granted access to the classic virtual system instance or have the Workload resources administration with full permissions to complete this task.

About this task

When you stop a classic virtual system instance, the system resources are not released. A stopped classic virtual system instance still affects placement decisions even though it is not actively running on the hypervisor. The system resources assigned to this classic virtual system instance are maintained to ensure that the resources are available when you redeploy the classic virtual system instance into the cloud.

Procedure

  1. Click Patterns > Virtual System Instances (Classic).
  2. Select the virtual system instance that you want to stop or store.
  3. From the Virtual Systems pane, click Stop in the toolbar to stop your classic virtual system instance.
    Stopping the classic virtual system instance does not happen immediately. Wait until the state of the classic virtual system instance is Stopped, and then you can optionally store it.

    All virtual machines are stopped when a classic virtual system instance is stopped. If you must stop only certain virtual machines, use the associated virtual machine actions.

    Stopping a classic virtual system instance does not release the associated resources. When a classic virtual system instance is stopped, click Start in the toolbar to restart the classic virtual system instance using the reserved resources.

  4. Optional: Click Store in the toolbar to store your classic virtual system instance.
    By storing a classic virtual system instance, you release CPU and memory hypervisor resources. Licenses that were used by the instance are also released. Storage and assigned IP addresses are not released. The classic virtual system instance is still managed by the system.

    You can redeploy a stored classic virtual system instance into the cloud by restarting it. Deployment succeeds only if adequate resources and necessary licenses are available.

Results

Your classic virtual system instance is no longer running, but remains available for redeployment in the future.

What to do next

Create a classic virtual system instance by deploying a pattern, or access a different classic virtual system instance that is started. For more information, see the related links.