Starting virtual system instances
Virtual system instances managed by the system are not always running and in the Started state. When a virtual system instance is in either the Stopped state or the Stored state, you can restart the virtual system instance to redeploy the virtual system instance into the cloud.
Before you begin
These steps are only intended for starting a virtual system instance that is in the stopped state or the stored state. To create a virtual system instance, you must deploy a pattern into the cloud. For more information, see the Related tasks.
About this task
Stopped
state are not displayed under the
. Restart the
virtual machines to view the entire list.The virtual system instance still has an impact on placement decisions though it is not actively running. The resources assigned to this virtual system instance are maintained to ensure that resources are available when the virtual system instance is restarted.
If the virtual system instance has been stored, then other virtual system instances might have consumed the memory required to restart the virtual system instance. If this scenario occurs, then you can stop and then store other virtual system instances to release sufficient memory to ensure that the stored virtual system instance can be restarted.
Follow these steps to redeploy the virtual system instance into the cloud by restarting the virtual system instance.
Procedure
- Click .
- Select the virtual system instance that you want to start.
- Click the Start icon to deploy the virtual system instance.
Deployment does not happen instantly. The deployment time depends on the virtual system instance size and the system activity. The Start icon is displayed while the deployment process is in progress or all the virtual machines in a cluster have not yet started. When the state of the virtual system instance is The virtual system has been deployed and is ready to use, then the virtual system instance is running in the cloud and available for use. The Failed icon displays if the virtual system instance does not start successfully.