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 (

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.

Status Future consideration
Created by Guest
Created on Nov 12, 2021

VMRM Discover/Verify - VM_CONFIG_COLLECTION_FAILURE for one LPar must not impact others

We've VMRM 'HA' cluster among 2 Hosts. I had 5 VMs as 'managed', then i ran a Hostgroup discover + verify. Due to a HW failure the 'discover' failed for 2 VMs with event VM_CONFIG_COLLECTION_FAILURE, but was successful for the other 3 VMs. At the end of the discover + verify however all 5 VMs were in READY state.
My desire would be to have the VMs not affected by the HW failure in READY_TO_MOVE state instead, so that i can avoid having to 'unmanage' the 2 VMs affected by the HW issue and then re-run discover + verify to have the 3 VMs in READY_TO_MOVE.
All details in Case TS007342720

Idea priority Medium
  • Guest
    Jul 4, 2022
    Once after discovery is success, then it moves to verification. Verification moves LPARs state into READY_TO_MOVE.
    But since the discovery itself failed, it is not moving to verification process.
    It is critical to pass discovery process, since HA cluster at VIOS level creation and trunk, client adapter creations happen automatically.