You can determine whether VIOS installation images have already been stored on an HMC using the command “hmc lsviosimg”:

LPAR-Tool
$ hmc lsviosimg hmc01
NAME           SIZE     IMAGE_FILES
VIOS_4.1.0.0   3487.68  dvdimage.v1.iso
VIOS_3.1.4.20  5985.77  dvdimage.v2.iso,dvdimage.v1.iso
$
HMC-CLI
hscroot@hmc01:~> lsviosimg
name=VIOS_4.1.0.0,size=3487.55,image_files=dvdimage.v1.iso
name=VIOS_3.1.4.20,size=5985.77,image_files=dvdimage.v2.iso,dvdimage.v1.iso
hscroot@hmc01:~>

The installation images for versions 3.1.4.20 and 4.1.0.0 are already stored on the HMC shown.

If managing installation images on an HMC is not supported, you will receive the following error message:

LPAR-Tool
$ hmc lsviosimg hmc11
hmc11: lsviosimg
ERROR: remote HMC command returned an error (127)
StdErr: /bin/bash: lsviosimg: command not found
$
HMC-CLI
hscroot@virt-hmc11:~> lsviosimg
bash: lsviosimg: command not found
hscroot@virt-hmc11:~> 

If you want to see which installation images are available for a virtual I/O server on the associated HMCs, you can use the command “vios ​​lsviosimg” instead of “hmc lsviosimg“:

LPAR-Tool
$ vios lsviosimg vio1
NAME           HMC    SIZE     IMAGE_FILES
VIOS_4.1.0.0   hmc01  3487.55  dvdimage.v1.iso
VIOS_3.1.4.20  hmc01  5985.77  dvdimage.v2.iso,dvdimage.v1.iso
VIOS_4.1.0.0   hmc02  3487.68  dvdimage.v1.iso
VIOS_3.1.4.30  hmc02  6063.53  dvdimage.v2.iso,dvdimage.v1.iso
$ 
HMC-CLI
hscroot@hmc01:~> lsviosimg
name=VIOS_4.1.0.0,size=3487.55,image_files=dvdimage.v1.iso
name=VIOS_3.1.4.20,size=5985.77,image_files=dvdimage.v2.iso,dvdimage.v1.iso
hscroot@hmc01:~>
hscroot@hmc02:~> lsviosimg
name=VIOS_4.1.0.0,size=3487.55,image_files=dvdimage.v1.iso
name=VIOS_3.1.4.30,size=6063.53,image_files=dvdimage.v2.iso,dvdimage.v1.iso
hscroot@hmc02:~>