PowerVM

Power Virtualization

Learn about the virtualization technologies designed specifically for IBM Power including #PowerVM, #PowerVC, #VM Recovery Manager#HCM/CMC, and more. #Power #TechXchangeConferenceLab #Servers

 View Only
  • 1.  PowerVC 2.3.3 End of SLES

    Posted 07/22/26 10:09 PM

    PowerVC 2.3.3: End of SLES support and the move to the PowerVC Appliance

    I noticed that with the release of PowerVC 2.3.3, IBM no longer supports installing the PowerVC management server on SUSE Linux Enterprise Server (SLES). The supported operating systems are now limited to RHEL, and the documentation explicitly states that migration from SLES to RHEL or to the PowerVC Appliance is supported. (IBM⁠)

    For many customers, especially those who have standardized their Power infrastructure around SLES for years, this represents a significant architectural change.

    I'm curious to understand the community's perspective.

    Some questions that come to mind:

    • What was the main reason behind IBM's decision to discontinue SLES support?
    • Is the long-term strategy to make the PowerVC Appliance the preferred and eventually standard deployment model?
    • Were there any operational benefits after the migration, such as simplified lifecycle management, upgrades, or support?
    • For customers with existing automation, monitoring, backup procedures, or security hardening built around SLES, how disruptive was this transition?

    From my perspective, many enterprise customers deliberately chose the Linux-based installation because it offered greater flexibility, better integration with existing operational standards, and more control over the underlying operating system.

    While I understand the operational advantages that an appliance can provide, I'm interested in understanding whether this transition was driven mainly by engineering simplification, supportability, or if there is a broader roadmap behind this decision.

    I'd really appreciate hearing experiences from other customers, IBM engineers, and Business Partners who have already gone through this migration.

    For reference, IBM documents this change in the PowerVC 2.3.3 Hardware and Software Requirements, where SLES is no longer listed as a supported operating system for the PowerVC management server, and migration to RHEL or the PowerVC Appliance is the recommended path.

    https://www.ibm.com/docs/en/powervc-cloud/2.3.3?topic=powervc-hardware-software-requirements

    Although I understand that the PowerVC Appliance is clearly the direction IBM is taking, and I agree that an appliance-based deployment greatly simplifies installation, upgrades, lifecycle management, and overall operational consistency, I still feel there are important gaps that need to be addressed before it becomes a complete replacement for the traditional Linux deployment. Today, some administrative tasks that were relatively straightforward on a standard SLES installation, such as certificate management, still require opening IBM support cases or relying on undocumented procedures. Greater administrative flexibility, better documentation, and self-service capabilities for common operational tasks would make the appliance much more attractive for enterprise environments. I truly believe the appliance is the future of PowerVC, but I also believe there is still significant room for improvement before customers can migrate without losing operational flexibility.



    ------------------------------
    Rafael Cezario
    Technical Director
    BLUE TRUST
    Brasilia, DF, Brazil
    ------------------------------


  • 2.  RE: PowerVC 2.3.3 End of SLES

    Posted 07/23/26 02:00 AM

    Hi Rafael,

    Thank you for your feedback. PowerVC is transitioning into a completely virtual Appliance model starting with our upcoming release slated for Dec'26. Our first version of virtual appliance was with 2.3.2 which GA'ed in Dec 2025. We have further enhanced this model in 2.3.3 which was released in June'26. This does include supported CLI for certificate management, support network configuration and NTP to name a few.(https://www.ibm.com/docs/en/powervc-cloud/2.3.3?topic=introduction-whats-new-in-powervc-private-cloud) .

    Happy to connect with you to discuss what we have in store for our upcoming release and any other operational gaps you are seeing with the virtual Appliance model.

    Thank you,

    Shyama



    ------------------------------
    Shyama Venugopal
    ------------------------------



  • 3.  RE: PowerVC 2.3.3 End of SLES

    Posted 07/24/26 04:50 AM

    Hi Shyama,

    I'm yet to test the 2.3.3 virtual appliance, but one of the issues I can see from the documentation is no ability to create individual logins for the CLI.  We currently have our PowerVC systems integrated with Active Directory at the OS layer (using realm).  We have users at the CLI and scripted automation that collects data via the CLI.  Having individual accounts is a must, without that ability moving to the appliance is somewhat of a no-go. 

    Phill.



    ------------------------------
    Phill Rowbottom
    Unix Consultant
    Service Express
    Bedford
    ------------------------------