Hello world! The wait is over to experience the few more exciting features and fixes in our signature virtualization product – PowerVC. Today we’re officially releasing the 1.4.2 fix pack, which contains the following updates:

Redundant HMC support
PowerVC allows you to manage a host through more than one HMC, where the first registered HMC is the primary HMC for the host. If there is another HMC managing the host and it is added to PowerVC, it is set as the secondary HMC. In the event of a primary HMC failure, PowerVC automatically fails over the host connection to the secondary HMC. Additionally, you can manually change the connection to the secondary HMC for planned HMC down time. Doing so makes the selected HMC the primary HMC. For more information, visit our Knowledge Center.

Fixes
Although a little less exciting than new support, a fix pack needs to have some fixes too. These are the APAR fixes included with this fix pack:
IT27852 — Unable to edit imported mirror volumes.
IT27839 — Image Export Device discovery fails when PowerVC is installed on Bare-metal Power server.
IT27430 — LPM of a virtual machine fails if the name contains non-ASCII characters.
IT27636 — PowerVC failed to identify the prerequisites before install.
IT27643 — PowerVC install fails if the installer runs from NFS mount.
IT28235 — PowerVC failed to configure SR-IOV when the management server is HMC.
IT28007 — PowerVC 1.4.2 upgrade/restore fails with database error.
You can find the fixes here: Fix Central.
For instructions to install the fixes, see Getting fixes from Fix Central.

Keep watching our social outlets for more interesting information about PowerVC! Find us on Facebook, LinkedIn, and Twitter.

6 comments on"Announcing PowerVC 1.4.2 Fix Pack 1"

  1. Marcello R. April 04, 2019

    Hello SriRamPisupati, i have the last release with Powervc.
    For many weeks i did try to connect with Hitachi G800 and i think than the process is very complex and failed finding a manual with clear step by step
    I try but not have result, can you help with a link efective?

  2. I have our “Host Group” in “Advise only” mode and “Operations: Migrations”. I intentionally set the CPU threshold down to 3% to make it generated DRO Events. It is generating DRO Events now, but I’m not see any the recommended operations. The advise mode says, “Advise only: Optimization operations are recommended but not performed when the specified threshold value is exceeded.” Where do I find the resulting recommendations? The DRO Events page just shows the exceeded event itself.

    • Hi,
      This could be due to the reason that the threshold has been set to a very low value and DRO cannot find any VM which if migrated to any other host in the host group will bring down the source host’s utilization below the threshold and at the same time does not make the destination host’s violate the threshold. Because if it does, this will cause a ping-pong effect where the VM just migrates from one host to another within the host group. So net is that its possible that there is no VM which can be migrated or advised to be migrated to any other host in the host group.
      You could also find more information at /var/log/nova/nova-ibm-ego-resource-optimization.log

  3. Hi folks, when are you planning to deliver a release to fix this one ? IT27272: PowerVC fails to add a resource or deploy a VM when the managed HMC version is V9R1 M921.

    • SriRamPisupati April 24, 2019

      Hi,
      This has already been implemented in the product and there is an iFix available for older versions of PowerVC.
      Hope this helped,
      Thanks!

Join The Discussion

Your email address will not be published. Required fields are marked *