Using Ignite-UX with Integrity VM

Copying the EFI image
Itanium-based systems, including Integrity VMs, require an EFI image. Thus, the EFI image must be copied to the directory
where the ISO image is being staged:
# cp -p /opt/ignite/boot/Rel_B.11.23/EFI_CD_image /scratch/staging/
Creating the ISO image
Now that everything is in place, the ISO image is created with the mkisofs command. Note that we use the Itanium-
based variation of this command.
# /opt/ignite/lbin/mkisofs \
-D -R -U -max-iso9660-filenames \
-no-emul-boot \
-b EFI_CD_image \
-eltorito-alt-boot \
-no-emul-boot \
-b vm.lifimage \
-o /scratch/B.11.23.iso \
/scratch/staging/
Note the repeat of the option ‘-no-emul-boot’ is required for the subsequent ‘-b’ option.
You will see two warnings that are expected (please ignore them):
Warning: creating filesystem that does not conform to ISO-9660.
Warning: ISO-9660 filenames longer than 31 may cause buffer overflows in the OS.
The command will take several minutes to complete and will be fairly verbose.
Rendering the ISO mountable and bootable
The final ISO image (virtual DVD) will be both a bootable DVD (via the LIF image) and a file system that can be mounted by
HP-UX. To enable the ISO image to function both ways, instl_combine is used as follows:
# /opt/ignite/lbin/instl_combine -C /scratch/B.11.23.iso
Validating the ISO image
Now that the ISO image is complete, verify that it is a valid LIF image:
# lifls /scratch/B.11.23.iso
which will simply list its contents. If it fails or produces error messages, then your ISO image is either too large for lifls to
read (over 2GB) or it is corrupt.
In the event that the ISO image is larger than 2GB, lifls will produce the following message:
lifls(open): Value too large to be stored in data type
lifls: Can't list /scratch/B.11.23.iso; file not opened
To check whether this (large) image is, in fact, valid use the workaround for this problem - copy the first 600MB to another
file with dd and run lifls on the resulting file.