Skip to Main Content
IBM Power Ideas Portal


This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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 (https://ideas.ibm.com).


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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Submitted
Created by Guest
Created on Jul 31, 2026

HMC vCPU Target Assignment Should Always Reach the Requested Target Value

HMC vCPU Target Assignment Should Always Reach the Requested Target Value

Description

When modifying vCPU allocation in HMC, administrators enter a target value (for example, 20 vCPU). Internally, HMC appears to calculate a delta (e.g. -10 vCPU).

If the same target value is entered again while the original operation is still running, the delta may be applied a second time, causing the partition to end below the requested target.

Example:

  • Current allocation: 30 vCPU
  • Target entered: 20 vCPU
  • Internal calculation: -10 vCPU
  • Target entered again before completion
  • Final result: 10 vCPU instead of 20 vCPU

Requested Enhancement

HMC should treat the entered value as the desired end state and always converge to that target, regardless of how often the same value is submitted while the operation is in progress.

Business Value

  • Prevent incorrect CPU allocations
  • Improve predictability and usability
  • Reduce operational errors
  • Align behavior with administrator expectations and desired-state principles

Customer Impact

Administrators expect a target value of 20 vCPU to always result in 20 vCPU, even if the same request is submitted multiple times while a previous adjustment is still being processed.

Idea priority Medium
  • Guest
    Jul 31, 2026

    Additional Customer Feedback (Thanks Patrick!)

    Another customer reported similar behavior when a HMC DLPAR operation does not complete within the configured execution time (default: 5 minutes). The operation may continue in the background and remain visible on AIX as a chrp process.

    The customer recommends increasing the DLPAR execution time (e.g. to 120 minutes).

    Regardless of the underlying cause, the expectation remains that a target value should always result in the requested final configuration and should not be applied multiple times when re-entered while an earlier operation is still running.