Readme for IBM PowerVM NovaLink 1.0.0.2 This is the March 2016 release of IBM PowerVM NovaLink. Learn more about PowerVM NovaLink at * https://ibm.biz/pvm224-novalink (Blog) * https://ibm.biz/novalink-kc (Knowledge Center) Download of the IBM PowerVM NovaLink installation media is available at the Entitled Systems Support site (ESS). http://www-304.ibm.com/servers/eserver/ess/OpenServlet.wss NovaLinkis entitled for download if you have a license for IBM PowerVM * IBM PowerVM Virtual I/O Server Enterprise Version 2.2.4 5765-PVE * IBM PowerVM Virtual I/O Server Standard Version 2.2.4 5765-PVS * IBM PowerVM for IBM PowerLinux Virtual I/O Server Version 2.2.4 5765-PVL Contents Where to get fixes Changes in 1.0.0.2 Known Issues Installation Software Life Cycle Where to get fixes Fixes and service packs for this product are available on an online repository · ftp://public.dhe.ibm.com/systems/virtualization/Novalink/debian See the Infocenter documentation for more information on installing fixes and updates · http://www.ibm.com/support/knowledgecenter/POWER8/p8eig/p8eig_updating_ubuntu_online.htm?cp=POWER8 Changes in 1.0.0.2 · Full release support for HMC/NovaLink Co-Management. This requires HMC V8.840 SP1, Firmware 840.11, and PowerVC 1.3.0.2. Previously, this function was delivered as a technology preview. · Support for PowerVM Active Memory Expansion · Support for IBMi partitions – including mobility and operating system shutdown support · Improvements to the pvmctl command line list commands Known Issues · Issues affecting HMC Co-Management o Prior to converting a system to a co-managed environment, the user should create a backup of the profile data (bkprofdata) on the HMC. This will allow the user to revert back to the state prior to co-management should they desire. o Any LPAR that has not been powered on at least once prior to switching over to a co-managed mode will need to be re-created. o The HMC Enhanced UI should be used when using the HMC in a co-managed mode. The classic UI is missing key functionality due to the lack of partition profiles when running co-managed. o NovaLinkdoes not currently have support for SRIOV, vNIC, Active Memory Sharing, or Hibernation. · Issues affecting full installs (where NovaLink deploys the entire PowerVM stack including the VIOS). o When performing a full install on a new system, if any error occurs before the VIOS server(s) have been created or installed, you will need to reset the system in order to try again. *Resolution:* If you encounter an error during the creation or installation of the VIOS Server(s), you will need to reset your system to the initial factory settings. This can be done via the ASMI interface or by rebooting the NovaLink partition and use the 'Reset System' under the 'Choose to repair a system' option of the NovaLink installation wizard. o When performing a full install on a new system, the IP addresses associated with NovaLink and the VIOS should not use the 192.168.128.1 network (or any superset). NovaLink sets up a 192.68.128.1 network through which to install the VIOS, and allocating that same network for the external facing IPs will cause the install to fail. * Issues affecting Co-Managed Installs o Make sure you assign sufficient resources to the NovaLink partition to complete the installs. The base requirements are 4.5 GB of memory and 0.5 processor units uncapped with a non-zero weight. After install is complete you can drop the NovaLink lpar down to 2.5 GB of memory. * Issues affecting Partition Mobility o Mobility is fully supported using the the latest levels of software for both HMC and NovaLink + HMC (co-managed and master or not co-managed) V8.840 SP1 or later <-> NovaLink 1.0.0.2 or later + NovaLink1.0.0.2 or later <-> NovaLink 1.0.0.2 or later o Mobility is *not* supported using older levels of software. + NovaLink1.0.0.2 <-> NovaLink 1.0.0.1 is *not* supported. + HMC V8.840 or earlier <-> NovaLink is *not *supported · The IBM NovaLink application will be translated in a future release. It will be U.S. English only initially. Installation Installation instructions for PowerVM NovaLink are available on the on-line Knowledge Center. · http://www.ibm.com/support/knowledgecenter/POWER8/p8eig/p8eig_installing.htm?cp=POWER8 Software Life Cycle PowerVMNovaLink uses versioning in the form of Version, Release, Mod Level and Fix (VRMF). Example 1.0.0.2 · Version and Release increments have a 3 year software support Lifecycle and follow IBM’s standard software lifecycle (_http://www-01.ibm.com/software/support/lifecycle/lc-policy.html)_. · Mod Level (third digit) increments have an N-1 support policy. The current available Mod Level and the previous release of a Mod Level are supported. o For example if 1.0.1.x is currently the latest shipped release, then 1.0.0.x versions are in support. Once 1.0.2.x release is available, support for 1.0.0.x ceases. · Fix (fourth digit) increments indicate fix and service pack levels for the Mod Level of the release. PowerVM NovaLink uses the Debian method of delivering fixes via a fix repository. See the Knowledge Center for more information. Errata for service fixes will be posted to Fix Central .