IBM Support

IBM Virtual I/O Server support for Power Systems

Fix Readme


Abstract

Downloads for Workload Partition Manager for AIX

Content

The Virtual I/O Server facilitates the sharing of physical I/O resources among client logical partitions within the server. The Virtual I/O Server provides virtual SCSI target, virtual fibre channel, Shared Ethernet Adapter, PowerVM Active Memory Sharing and PowerVM Client Partition Mobility capability to client logical partitions within the system. As a result, client logical partitions can share SCSI devices, fibre channel adapters and Ethernet adapters. With VIOS, you can expand the amount of memory available to logical partitions by using paging space devices, and also move AIX and Linux logical partitions from one system to another.

The Virtual I/O Server is included in all PowerVM Editions.

Find links to Fix Central for current updates and to Readmes for current and previous updates below.

Update Release 2.2.6.23 for VIOS 2.2.6
Package Description
Update release 2.2.6.23
17 August 2018
To take full advantage of all the function available in the VIOS, it is necessary to be at the latest system firmware level. The Fix Level Recommendation Tool (FLRT) provides information on recommended levels of system firmware and VIOS. If a system firmware update is necessary, it is recommended that the firmware be updated before you upgrade the VIOS to V2.2.6.23.

The VIOS Update Release V2.2.6.23 includes the IVM code, but it will not be enabled on HMC-managed systems. V2.2.6.23, like all VIOS Update Releases, can be applied to either HMC-managed or IVM-managed VIOS.
 
Update Release 2.2.5.40 for VIOS 2.2.5
Package Description
Update release 2.2.5.40
11 May 2018
To take full advantage of all the function available in the VIOS, it is necessary to be at the latest system firmware level. The Fix Level Recommendation Tool (FLRT) provides information on recommended levels of system firmware and VIOS. If a system firmware update is necessary, it is recommended that the firmware be updated before you upgrade the VIOS to V2.2.5.40.

The VIOS Update Release V2.2.5.40 includes the IVM code, but it will not be enabled on HMC-managed systems. V2.2.5.40, like all VIOS Update Releases, can be applied to either HMC-managed or IVM-managed VIOS.
 
Update Release 2.2.4.60 for VIOS 2.2.4
Package Description
Update release 2.2.4.60
11 May 2018
To take full advantage of all the function available in the VIOS, it is necessary to be at the latest system firmware level. The Fix Level Recommendation Tool (FLRT) provides information on recommended levels of system firmware and VIOS. If a system firmware update is necessary, it is recommended that the firmware be updated before you upgrade the VIOS to V2.2.4.60.

The VIOS Update Release V2.2.4.60 includes the IVM code, but it will not be enabled on HMC-managed systems. V2.2.4.60, like all VIOS Update Releases, can be applied to either HMC-managed or IVM-managed VIOS.
 
Update Release 2.2.3.90 for VIOS 2.2.3
Package Description
Update release 2.2.3.90
20 April 2017
To take full advantage of all the function available in the VIOS, it is necessary to be at the latest system firmware level. The Fix Level Recommendation Tool (FLRT) provides information on recommended levels of system firmware and VIOS. If a system firmware update is necessary, it is recommended that the firmware be updated before you upgrade the VIOS to V2.2.3.90.

The VIOS Update Release V2.2.3.90 includes the IVM code, but it will not be enabled on HMC-managed systems. V2.2.3.90, like all VIOS Update Releases, can be applied to either HMC-managed or IVM-managed VIOS.
 
Update Release 2.2.2.70 for VIOS 2.2.2
Package Description
Update release 2.2.2.70
30 September 2015
To take full advantage of all the function available in the VIOS, it is necessary to be at the latest system firmware level. The Fix Level Recommendation Tool (FLRT) provides information on recommended levels of system firmware and VIOS. If a system firmware update is necessary, it is recommended that the firmware be updated before you upgrade the VIOS to V2.2.2.70.

The VIOS update Release V2.2.2.70 includes the IVM code, but it will not be enabled on HMC-managed systems. V2.2.2.70, like all VIOS Update Releases, can be applied to either HMC-managed or IVM-managed VIOS.
 
Update Release 2.2.1.9 for VIOS 2.2.1
Package Description
Update release 2.2.1.9
27 August 2014
To take full advantage of all the function available in the VIOS, it is necessary to be at the latest system firmware level. The Fix Level Recommendation Tool (FLRT) provides information on recommended levels of system firmware and VIOS. If a system firmware update is necessary, it is recommended that the firmware be updated before you upgrade the VIOS to V2.2.1.9.

The VIOS update Release V2.2.1.9 includes the IVM code, but it will not be enabled on HMC-managed systems. V2.2.1.9, like all VIOS Update Releases, can be applied to either HMC-managed or IVM-managed VIOS.

Migration DVD

30 June 2011

You can now migrate your existing version (1.4 through 1.5) of the VIOS to Version 2.1.0. You cannot upgrade a VIOS to Version 2.1 from a lower level by applying the latest Version 2.1 fix pack. To upgrade to VIOS Version 2.1, you must use the Migration DVD method.


  1. Note:

    Processor folding : Processor folding currently is not supported for VIOS partitions. If processor folding is enabled on your VIOS, and migration media is used to move from VIOS 1.5 to 2.1.0.13 FP 23, or later, processor folding remains enabled. Upgrading via migration media does not change the processor folding state. If you have installed VIOS 2.1.3.0, or later, and have not changed the folding policy, then folding is disabled.

    From the root shell, you can disable processor folding without rebooting the VIOS. The settings are effective immediately. To enter the root shell, use the VIOS oem_setup_env command. In the root shell, you can then verify the state of processor folding: Processor folding is OFF if the vpm_fold_policy is 4. The following command returns the current value of the vpm_fold_policy :
    schedo -L | grep vpm_fold_policy | awk '{print $2}'
    If the vpm_fold_policy is not "4", then use the following command to set it to 4:
    schedo -p -o vpm_fold_policy=4

IBM Security Advisory

Java 5 has a security vulnerability and was removed from VIOS 2.2.5 and later. Java 6 has a security vulnerability and was removed from VIOS 2.2.6 and later. It is possible that your VIOS may still have these old Java versions installed if the Fixpack process was used to update the VIOS. Java 5 is not required for VIOS 2.2.5 and later, it can safely be removed from the VIOS without impacting VIOS operation. Java 6 is not required for VIOS 2.2.6 and later, it can safely be removed from the VIOS without impacting VIOS operaton. Removal of these versions of Java from the VIOS is a supported operation.

To remove Java from your VIOS, follow these steps:

/* For Java5 */
$ oem_setup_env
# installp -u -g Java5.sdk

/* For Java4 */
$ oem_setup_env
# installp -u -g Java14.sdk

VIOS Security Information

To view information on security vulnerabilities that impact the Virtual I/O Server (VIOS), please visit the FLRT security information page: VIOS security information.

Patches to VIOS / AIX components are typically provided in ifix epkg format and should be applied using procedures found in the VIOS documentation. In some cases, patches to non-AIX components such as Java, OpenSSH/OpenSS, etc., may not be in ifix epkg format. These may require installation of new filesets, etc. In these cases, the patches and process provided to fix the problem on AIX can be applied to the VIOS. Determine the level of AIX that your VIOS version is based on by using the VIOS to NIM Master mapping page. Then refer to that level of AIX to get the vulnerability patch and instructions. The procedure to apply the patches would be the same as suggested for AIX after dropping into the root shell via the oem_setup_env command.

Notices

Suspend/Resume Notice

Users of the Suspend/Resume function of PowerVM should take precautions to ensure that virtual devices of suspended LPARs are not unintentionally re-allocated while an LPAR is suspended. When a partition is suspended using the current PowerVM function, the vSCSI disk devices of the partition are reflected as free by VIOS commands such as lsmap and chdev, as well as by management consoles (HMC and SDMC). Devices of suspended LPARs should be tracked carefully by means of the UDID of the device. Before execution of the Suspend operation, the UDID can be acquired by using the lsmap command of VIOS.

After the LPAR is Resumed, its vSCSI devices are again reflected as IN_USE by a VIOS that exports it as a virtual device.

An enhancement to keep these devices marked IN_USE across Suspend / Resume operations is under evalutation.

Technical information

Find technical support and problem solving documentation, as well as a link to the VIOS Advisor wiki on developerWorks.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSPHKW","label":"PowerVM Virtual I\/O Server"},"Component":"","Platform":[{"code":"PF002","label":"AIX"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB57","label":"Power"}}]

Document Information

Modified date:
19 February 2022

UID

hpc1vios_home