Skip to Main Content
Cloud Management and AIOps

This is an IBM Automation portal for Cloud Management and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Workspace IBM Turbonomic ARM
Created by Guest
Created on Dec 6, 2022

Scaling powered off VMs

There are numerous scenarios where a VM is powered off and can/should be scaled. Once a workload is powered off though, the action goes away. I think it's important to allow these resources to be resized before they're powered on and requiring another interruption:

1. Public cloud: VMs that are suspended also can be scaled. A user should be able to execute the scaling action while the VM is powered off.

2. Horizon VDI: Especially in vGPU enabled VDI environments, user desktops are powered off quickly after the user disconnects in order to free up the GPU license for a different powered on VM. The GPU license is claimed at VM power on, not user logon, so the goal is to keep unused VMs powered off as much as possible. This becomes an issue when attempting to scale users of persistent desktops, where changing a user's entitlement isn't the method for scaling the user experience. Additionally, with vGPU enabled, CPU Hot Add is disabled, increasing the need to get the scaling action complete at the soonest opportunity.

Idea priority High
  • Admin
    Jeremy Hazlett
    Dec 6, 2022

    Additional scenario:

    DR pairs where the cold/warm site is powered off, and consistent sizing is required.