Using Ignite-UX with Integrity Virtual Machines

A white paper from HP

Introduction ................................................................................................................................... 3 Basic Network Installation ................................................................................................................ 3 Setting up the Ignite-UX server ....................................................................................................... 4 Setting up for a static IP environment........................................................................................... 4 Setting up a DHCP environment ................................................................................................. 5 Installing HPUX on the VM with Ignite-UX......................................................................................... 6 Advanced Network Installation ......................................................................................................... 9 Creating a VM configuration for repeated use with Ignite-UX .............................................................. 9 Preparing a system to be a golden image .................................................................................... 9 Installing Integrity VM guest software ........................................................................................ 10 Installing with the new configuration............................................................................................. 10 Using Virtual DVD with ISO Images ................................................................................................. 11 Configuring a Virtual DVD to Use an ISO Image............................................................................. 11 Sharing media among virtual machines......................................................................................... 12 Ignite-UX and the Integrity VM Host.................................................................................................. 13 Creating a VM Host golden image............................................................................................... 13 Summary..................................................................................................................................... 13

Appendix A Creating and Configuring a Golden Image for Network Installation................................... 14 Making the operating system archive ........................................................................................ 14 Configuring the Ignite-UX server to recognize the golden image..................................................... 15 Appendix B Creating and Configuring a Golden Image as an ISO Image............................................ 17 Making the operating system archive ........................................................................................ 17 Creating an archive configuration file ....................................................................................... 17 Creating a copy of the LIF volume............................................................................................. 18 Copying the EFI image ........................................................................................................... 19 Creating the ISO image.......................................................................................................... 19 Rendering the ISO mountable and bootable ............................................................................... 19 Validating the ISO image........................................................................................................ 19 Moving the ISO image to the Integrity VM Host .......................................................................... 20 For more information..................................................................................................................... 13

Introduction
Ignite-UX makes it easier than ever to deploy Integrity Virtual Machines (Integrity VM) product on an Itanium-based server. Once the virtual machine is created, installation of the HP-UX operating system and software on the virtual machine (VM) is made easy through the use of Ignite-UX. Generally speaking, the use of Ignite with Integrity Virtual Machines is no different from that of a physical Integrity server. There are two important differences: identification of the virtual machines MAC address for network installation and the inclusion of the virtual machine guest bundle, HPVM-Guest, in golden images. This white paper provides the basic details of how to use Ignite-UX with Integrity Virtual Machines and highlights some variations for specific software installation scenarios. This white paper is not a replacement for Ignite-UX or Integrity VM product documentation but rather to provide a quick start guide for those with basic understanding of those products. Product documentation such as the Ignite-UX Administration Guide and the Integrity Virtual Machines Installation, Configuration, and Administration Manual are highly recommended, if not required. The practices discussed in this white paper are based on version A.03.00 of Integrity VM (T2767AC) and C.7.2.94 of Ignite-UX (IGNITE). Version C.6.5.61 or later of Ignite-UX is highly recommended. Two general strategies for using Ignite-UX with Integrity VM are addressed in this white paper network installation and the use of ISO (golden) images to install software with a virtual DVD.

Basic Network Installation

The most common use of Ignite-UX is to enable software installation over a network. The Integrity VM product provides virtual machines with features necessary to interact with an Ignite-UX server. As a result, software installation is performed in much the same way as it is on physical systems. This section outlines the steps necessary to install an operating system image on a VM over a network connection. Its assumed that the VM is configured with its virtual LAN associated with a valid virtual switch. Moreover, that virtual switch must be associated with a physical network interface card (NIC) connected to the same subnet as the Ignite-UX server. For example, suppose the Ignite-UX server is on the same subnet as the Integrity VM Hosts lan0. Use hpvmnet to identify the virtual switch (if any) associated with lan0. For example: # hpvmnet Name Number ======== ====== vswA 8 vswB 11 State ======= Up Up Mode ======= Shared Shared PPA ===== lan0 lan1 MAC Address ============== 0x00110a319869 0x00110a3177c6 IP Address =========== 75.99.87.15 76.72.120.11

From the above, we can deduce that virtual switch vswA is associated with lan0. Assuming lan0 is connected to a subnet with an Ignite-UX server on it, then any VM connected to that virtual switch will also be on the same subnet as the Ignite-UX server. To verify that a given VM is connected to the virtual switch, e.g., vswA, examine the output of hpvmstatus for that VM: # hpvmstatus P myvm02 [Network Interface Details] Interface Adaptor Name/Num Bus Dev Ftn Mac Address ========= ========== ========== === === === ================= vswitch lan vswA 0 1 0 86-ab-c8-5d-75-09

This example indicates that the VM myvm02 is connected to the virtual switch vswA. In the event no such entry exists for the VM, then a virtual network connection must be defined. To create such a connection, use the hpvmmodify command as follows: # hpvmmodify P myvm02 a network:lan::vswitch:vswA Note that the MAC address will not match that shown in this example as Integrity VM will automatically generate a MAC address for the virtual LAN. Moreover, this MAC address is not that of the physical Integrity servers network interface. The virtual machine will have to be restarted before it recognizes the new network connection.

Setting up the Ignite-UX server

The Ignite-UX server is a system with the Ignite-UX software installed and a network connection to systems (clients) intended to use Ignite-UX. Integrity servers with HP-UX 11i v2 are recommended for Ignite-UX servers to be used with Integrity VMs. Older Ignite-UX servers, especially PA-RISC based systems, may not have firmware versions sufficient for network communication with VMs. The Ignite-UX software bundle is available for all HP Integrity and PA-RISC servers. The steps outlined here are based on the HP-UX Installation Utilities (Ignite-UX), bundle IGNITE. For the latest Ignite-UX installation information, please reference the Installing and Configuring an Ignite-UX Server section of the Ignite-UX Administration Guide available from http://docs.hp.com. Basic configuration and initialization of the Ignite-UX server can be done with the Ignite-UX user interface. Currently, the Ignite-UX user interface does not fully accommodate configuration of the Ignite-UX server for use with Integrity servers. In particular, the configuration files /etc/dhcptab or /etc/bootptab must be directly modified on the Ignite-UX server to prepare it for use with Integrity servers, including Integrity VMs. Which of these files require modification depends on whether IP addresses are assigned statically or the network provides DHCP services. Setting up for a static IP environment For Ignite-UX clients that have a static IP address assigned to them, you will need to modify the /etc/bootptab configuration file. A defaults entry simplifies the process of adding new client entries (including those for Integrity VMs). An example of a defaults entry, IADEF, and two client entries are shown in Figure 1. has three entries one that specifies a set of default values (IADEF) and two for Ignite-UX clients (myvm01 and myvm02) that use those defaults. This particular default entry has four values that must be modified for your configuration: bp The IP address of the Ignite-UX server to be used to respond to clients. sm The subnet mask being used by the clients. gw The network gateway address. ds The domain name server address. Typographical errors in any of these will cause no end of enigmatic problems. Check the entries carefully. To add another entry for a new VM, you need to specify an entry similar to that of myvm01 or myvm02 in

Figure 1, where the first attribute is the hostname of the new VM. The other three attributes are defined as follows: tc The defaults to be used for this group of clients (in the example above, this will be IADEF). ip The (fixed) IP address of the client. ha The client hardware (MAC) address. The MAC address for a VM can be obtained from hpvmstatus or from the VMs console (the VM console will be discussed later). For example, the MAC address is the last field of its LAN entry displayed in the output of hpvmstatus: # hpvmstatus -P myvm02 | grep lan vswitch lan vswA 0 1 0 86-ab-c8-5d-75-09

Figure 1 - Entries in /etc/bootptab to accommodate Integrity VM clients IADEF:\ ht=ethernet:\ hn:\ bf=/opt/ignite/boot/nbp.efi:\ bs=48:\ bp=75.99.87.15:\ sm=255.255.248.0:\ gw=75.99.87.254:\ ds=75.99.52.11:\ vm=rfc1048: myvm01:tc=IADEF:ip=75.99.87.205:ha=86abc85d751a: myvm02:tc=IADEF:ip=75.99.87.38:ha=86abc85d7509:

Setting up a DHCP environment If Ignite-UX clients do not have static IP addresses assigned to them, as in a DHCP environment, then client-specific entries in /etc/bootptab are not practical. To accommodate such anonymous clients, HP-UX 11i v2 provides an option for DHCP configuration that enables the device_pool_group feature to be used. To use this feature, set up an entry in the /etc/dhcptab configuration file similar to that in Figure 2. The attributes of the entry in Figure
2

are described as follows:

dhcp_device_group - This starts a DHCP device pool group that provides a pool of IP addresses to a set of clients that all have the same class-id in their boot messages. class-id - All IPF clients send boot messages that contain a class id with a 32-character string: PXEClient:Arch:00002:UNDI:xxxyyy. Where "xxxyyy" are major and minor numbers for the Universal Network Device Interface revision. This line tells bootpd to respond only to clients that match a string that starts with PXEClient:Arch:00002, that is, IPF clients re - This is a binary option that tells bootpd to perform a regular expression match of the class-id rather than a default literal match. This is a new 11.23 option. ncid - This is a binary option that tells bootpd to not send back a class-id on the message responses. This option is necessary because bootpd does not support the full PXE protocol. This is a new 11.23 option. lease-time - This option indicates the time in seconds for leases given for IP addresses. addr-pool-start-address Identifies the start of a range of IP addresses offered to clients. addr-pool-last-address Identifies the end of a range of IP addresses offered to clients. subnet-mask The subnet mask used by clients. bf The EFI network boot program to use. After this entry is made in the /etc/dhcptab file on the Ignite-UX server, restart the bootpd daemon. It is typically started by inetd and you can verify this by examining the /etc/inetd.conf configuration file. If so, kill any instance of bootpd and inetd -c will restart bootpd for you.

Figure 2 - Entry in /etc/dhcptab to facilitate Ignite-UX server use with anonymous clients dhcp_device_group:\ re:\ ncid:\ class-id="PXEClient:Arch:00002:.*":\ lease-time=300:\ subnet-mask=255.255.248.0:\ addr-pool-start-address=75.99.87.6:\ addr-pool-last-address=75.99.87.253:\ bf=/opt/ignite/boot/nbp.efi

Installing HPUX on the VM with Ignite-UX

Once the Ignite-UX server is configured for your VM, youll need to access the VMs console. To do this, first power on the VM (e.g., with hpvmstart P myvm03) and access the VMs console (e.g., hpvmconsole P myvm03 fi). Once youve done that, the VM console will appear, similar to that shown in

Figure 3. Just as with a physical Integrity server, you may use lanboot to initiate the network installation. Be sure to select the lan entry with the MAC address that corresponds to the entry made for this VM in the Ignite-UX servers /etc/bootptab file. A successful connection and initiation of communication between the client and the Ignite-UX server is shown in Figure 4. A few moments later (and possibly after being prompted for the terminal type), you will arrive at the HP-UX installation menu ( Figure 5). From there, OS and software installation proceeds as with any other HP-UX installation.

Figure 3 - VM console after powering on the VM for the first time

Figure 4 - Initial client contact with the Ignite-UX server

Figure 5 - Successful contact with the Ignite-UX server leads to the HP-UX installation menu

Advanced Network Installation

When deploying several virtual machines, it can be cumbersome to repeatedly configure the operating system and software for each new virtual machine. Ignite-UX provides a means to dramatically simplify that process.

Creating a VM configuration for repeated use with Ignite-UX

If you are in a position where you are or will be installing the same operating system and software configuration on multiple VM systems, it may be prudent to create a golden image. A golden image is a snapshot of a known, reliable system installation and configuration (including operating system and additional software) that is archived for use in installing other clients. Ignite-UX creates such a golden image in the form of a compressed tar or cpio archive of the operating system configuration that Ignite-UX can recognize and use to install on other machines.

Operating system installation on virtual machines using golden images of VM Host systems is not supported The Integrity VM software itself may not be installed on a virtual machine (VM). Using golden images of VM Host systems (physical servers with the Integrity VM software installed) to install operating systems on virtual machines results in an unsupported software configuration. Such virtual machines may be rendered inoperable by such an installation.

A golden image for a standard software configuration facilitates fast virtual machine deployment. It has distinct advantages over manually selecting the OS attributes and software for installation repeatedly. The process for creating a golden image is detailed in the aptly-named Golden Images chapter of the Ignite-UX Administration Guide. An outline of the process is presented here to highlight some important Integrity VM software that you may choose to include as part of a standard Integrity VM golden image. The basic steps for creating such a configuration for a virtual machine that can be used with Ignite-UX are:
1. Prepare a system to be used in creating a golden image. 2. Install Integrity VM software to be included in the golden image. 3. Make the operating system archive (i.e., the golden image). 4. Configure the Ignite-UX server to recognize the golden image.

Each of these steps is described in the following sections. Preparing a system to be a golden image The first step in creating a golden system (i.e., the system configuration used in creating the golden image), is OS installation. Using an HP-UX Operating Environment (OE) is a good starting point as they contain combinations of HP software well-suited for many data centers. In the process of identifying the software to be installed on the VM, its recommended that you create a single SD-UX software depot containing the software to be installed. By copying all the software bundles (with swcopy) to a single depot, you will be able to select all the software from that depot for installation at one time and eliminate the need for multiple reboots.

Installing Integrity VM guest software The HPVM-Guest bundle should be considered when creating an Integrity VM golden system. This bundle tunes the HP-UX operating system for operation on a VM and also includes commands for collecting status and state of a VM as well as managing it. The dynamic memory control device driver is also included in this bundle and care must be taken to make sure golden images have this device driver configured correctly when the bundle is installed on the golden system. The HPVM-Guest bundle for HPUX 11iv2 may be obtained from the Integrity VM host in the form of a SD-UX distribution tape file: /opt/hpvm/guest-images/hpux/11iv2/hpvm_guest_depot.11iv2.sd The bundle for 11iv3 is contained in a SD-UX distribution tape file with analogous path and filename. This SD distribution tape file contains the HPVM-Guest software bundle. The file may be moved directly to the VM so that the bundle can be installed directly from that file with swinstall. Alternatively, the file may be used to swcopy the HPVM-Guest bundle to a directory depot on a system from which the software can be installed in a more typical fashion with swinstall. Use the command swcopy to copy it to the depot: # swcopy -s /opt/hpvm/guest-images/hpux/hpvm_guest_depot.sd \ \* @ <host>:/<depot path>/ The HPVM-Guest bundle is a good candidate for consolidating into one depot for a single installation with other software because it requires a reboot during installation. The remaining steps making the operating system archive and configuring the Ignite-UX server to recognize the golden image are as described in the Ignite-UX product documentation with one important addition. When configuring the IgniteUX server to recognize the golden image, care must be taken to modify the associated Ignite configuration file so that the HPVM-Guest bundles device drivers are configured correctly. The details of these steps are provided for convenience in Appendix A Creating and Configuring a Golden Image for Network Installation.

Golden images of systems with the HPVM-Guest bundle installed must explicitly configure the dynamic memory device driver If your golden system has the HPVM-Guest bundle installed, then be sure the dynamic memory device driver is configured correctly. To achieve this, add the line set_kernel += module hpvmdynmem loaded after the init sw_sel stanza in the golden images configuration file.

Installing with the new configuration

You may now install the new VM configuration using Ignite-UX as described in the section Installing HPUX on the VM with Ignite-UX above. From the HP-UX installation user interface ( Figure 5), continue to the Select an overall system configuration window (Figure 6). With the cursor in the Configurations: field, press enter and you will see the custom VM configuration listed as a selection. You may receive an error at this point indicating that the golden image (for example, B.11.23_VM_archive.gz) was not found. This is typically the result of having the file in a file system that is not being exported to NFS clients. Make sure the appropriate file system on the Ignite-UX server is exported, then restart the installation sequence.

Figure 6 - Selecting the new VM configuration for installation

Using Virtual DVD with ISO Images

Integrity Virtual Machines have a unique use for golden images in that they may be converted into ISO images which can be used as virtual DVDs. To do this, the golden system is set up as discussed in the Preparing a system to be a golden image section above. This system is used to create an ISO image which is then mapped to virtual DVDs for one or more VMs. Such virtual DVDs are then used to boot and install an operating system image on that VM. The detailed instructions are derived from the Creating Your Own Installation Media chapter of the Ignite-UX Administration Guide and are included here in Appendix B Creating and Configuring a Golden Image as an ISO Image for completeness. As is the case with the golden image configuration for network installation, take care that the golden images configuration file configures the device drivers installed with the HPVM-Guest bundle.

Configuring a Virtual DVD to Use an ISO Image

A VM may be configured with a virtual DVD by specifying the virtual DVD definition with commands such as hpvmcreate and hpvmmodify. To check what virtual DVD devices (if any) are defined for a VM, execute the following: # hpvmstatus -P myvm03 | grep dvd dvd scsi 0 0 0 1 0 file /hpvm/ISO/B.11.23.iso

From the above we deduce that there is, indeed, a virtual DVD device associated with myvm03 which is associated with the file /hpvm/ISO/B.11.23.iso. If no such device exists, add it as follows: # hpvmmodify -P myvm02 -a dvd:scsi::file:/hpvm/ISO/B.11.23.iso Once the virtual DVD is associated with the VM, it will automatically identify it when powered on and start the booting process as highlighted in Figure 7. Note that the VMs EFI automatically identifies the file system (fs0) on the virtual DVD. Subsequently, the installation media is located on the virtual DVD (i.e., the ISO image) and the installation boot sequence begins. From this point, the HP-UX installation is the same as if you are using physical installation media.

Figure 7 - Virtual console showing automatic boot from virtual DVD (ISO image)

Sharing media among virtual machines

Once you have the ISO image on the Integrity VM Host, you may want to use it with multiple VMs to start the installation process. As before, the virtual DVD must be defined for the new VM. For example: # hpvmmodify -P vm12 -a dvd:scsi::file:/hpvm/ISO/B.11.23.iso When doing so, you may receive messages similar to the following: hpvmmodify: ERROR (vm12): Duplicate backing device /hpvm/ISO/B.11.23.iso. hpvmmodify: ERROR (vm12): Unable to add device /hpvm/ISO/B.11.23.iso. hpvmmodify: Unable to create device dvd:scsi::file:/hpvm/ISO/B.11.23.iso. hpvmmodify: Unable to modify the guest. This indicates that another VM already has the (duplicate backing device) ISO image mapped to one of its virtual devices. This can be verified by the examining the state of the guest device from Integrity VMs perspective using hpvmdevmgmt: # hpvmdevmgmt -l gdev:/hpvm/ISO/B.11.23.iso /hpvm/ISO/B.11.23.iso:CONFIG=gdev,EXIST=YES,DEVTYPE=FILE,SHARE=NO: Among the attributes listed here, note the attribute SHARE is set to NO. By setting this attribute to YES, multiple VMs may share this ISO image. This is accomplished by executing: # hpvmdevmgmt -m gdev:/hpvm/ISO/B.11.23.iso:attr:SHARE=YES The attribute value may be confirmed as before: # hpvmdevmgmt -l gdev:/hpvm/ISO/B.11.23.iso /hpvm/ISO/B.11.23.iso:CONFIG=gdev,EXIST=YES,DEVTYPE=FILE,SHARE=YES: Now, the ISO image may be used by multiple VMs and the hpvmmodify command above will succeed. Changing the SHARE attribute value on a device is only recommended for ISO files, not for physical DVD drives.

Ignite-UX and the Integrity VM Host

Creating a VM Host golden image
Typically, the need for a golden image is associated with virtual machines that are being deployed, rather than the Integrity VM host itself. The steps above can be used to create a golden image of any configuration including one for an Integrity VM host. For example, there may be a standard set of management tools and system software that is used to manage and monitor an Integrity VM host. The golden system to be used to create such a golden image must not contain any virtual machine configurations. The unique system identifiers, virtual MAC addresses, etc., defined for virtual machine configurations must remain unique. Hence, a system with virtual machine configurations is not practical for creating a golden image.

Summary
Ignite-UX can be used in many ways to improve operating system and application installation on Integrity Virtual Machines. Network installation variations can dramatically improve productivity when faced with the task of installing software on dozens of virtual machines. Using ISO images for virtual DVDs will eliminate the time required to insert the installation media and later to extract it from the physical DVD. The step-by-step procedures given in this white paper can make these benefits a reality.

For more information

http://www.hp.com/go/vse for information on HPs virtual server environment http://docs.hp.com/ for product documentation, including HP Integrity Virtual Machines Installation, Configuration, and Administration Ignite-UX Administration Guide

Appendix A Creating and Configuring a Golden Image for Network Installation

Making the operating system archive Once the golden system is configured the way you want it, either install the Ignite-UX software or copy the file /opt/ignite/data/scripts/make_sys_image to /tmp on the golden system. If youve copied the above file, change the permissions of /tmp/make_sys_image to be executable. On the Ignite-UX server make sure there is sufficient space in the target file system to hold the golden-image archive that will be created. By default, the directory is /var/tmp, but you may want to store the golden image on another file system because /var is typically more difficult to extend than other file systems. 1. On the golden system, run: # /tmp/make_sys_image -s <Ignite-UX server IP address> \ d /<path to target directory> For example, executing: # /tmp/make_sys_image -s 75.99.87.15 \ d /var/opt/ignite/data/Rel_B.11.23 -n B.11.23_VM_archive.gz -n <archive file name>

will create the golden image in the directory /var/opt/ignite/data/Rel_B.11.23 on the host with the IP address 75.99.87.15. Note that the golden system must be listed in the /.rhosts file on the Ignite-UX server. If not, you will see the following error: ERROR: Cannot remsh server system_name (check server .rhosts file). Typically make_sys_image will run for several minutes. Once finished, it will have created the B.11.23_VM_archive.gz gzip (suffix .gz) file (for example, /var/opt/ignite/data/Rel_B.11.23/B.11.23_VM_archive.gz ) on the Ignite-UX server. 2. In the directory where the archive has been created, change the ownership of the archive to bin: # chown bin:bin *.gz 3. You will need to make sure that the directory where the golden image resides is available for an NFS mount. In our example, the path /var/opt/ignite/data/Rel_B.11.23 is added to the Ignite-UX servers /etc/exports file as follows: /var/opt/ignite/data/Rel_B.11.23 -anon=2 and is subsequently exported by running exportfs a.

Configuring the Ignite-UX server to recognize the golden image Once the golden image has been created, youll need to finish setting up the configuration for use on the Ignite-UX server. The steps to do this are as follows: 1. Capture the necessary impacts statements to be used in the configuration file by executing: # /opt/ignite/lbin/archive_impact -t -g B.11.23_VM_archive.gz

in the directory where the archive was created and capturing the output. For our example, in the directory where the archive resides (/var/opt/ignite/data/Rel_B.11.23), you would run: # /opt/ignite/lbin/archive_impact -t -g \ ./B.11.23_VM_archive.gz > impacts.txt This may take a minute or two to complete. 2. Create a configuration file by copying the example configuration file to the directory with the system archive. For example: # cp /opt/ignite/data/examples/B.11.23.golden_image.cfg \ /var/opt/ignite/data/Rel_B.11.23/vm.cfg Youll need to customize the configuration file for your archive as follows. 3. In the configuration file, modify the nfs_source definition in the sw_source section so that it references the Ignite UX server and the correct path. That is, using the example systems here, change: nfs_source = "10.2.72.150: /var/opt/ignite/archives/Rel_B.11.23" to: nfs_source = "75.99.87.15: /var/opt/ignite/data/Rel_B.11.23" 4. Continuing in the configuration file, modify the init sw_sel section(s) so that it corresponds to your golden image. Note that the example configuration specifies two different images one for Itanium-based systems (ia64) and another for PA-RISC systems (hppa). Assuming you didnt create an image for a PA-RISC systems version of HP-UX, you may simply delete the init sw_sel section for the PA-RISC system image ("is_hppa"). Follow these steps: a) Change the description parameter to better describe your golden image. For example, change: description = "B.11.23 IA golden image archive" to: description = "HP-UX 11.23 image for VMs" b) Change the archive_path to contain the name of the actual archive file. Using our example, you would change: archive_path = "B.11.23_archive_IA.gz" to: archive_path = "B.11.23_VM_archive.gz"

c) Replace the impacts lines with those captured in step 1 above. For example, replace the lines: impacts = "/" 7659Kb impacts = "/dev" 11Kb impacts = "/etc" 76229Kb impacts = "/home" 1Kb impacts = "/opt" 2223298Kb impacts = "/sbin" 109002Kb impacts = "/stand" 51127Kb impacts = "/usr" 2379518Kb impacts = "/var" 848454Kb with: impacts impacts impacts impacts impacts impacts impacts impacts impacts impacts = = = = = = = = = = "/" 833Kb "/dev" 13Kb "/etc" 82077Kb "/home" 133696Kb "/opt" 2536512Kb "/sbin" 111333Kb "/scratch" 135843Kb "/stand" 52187Kb "/usr" 2396952Kb "/var" 1603044Kb

where the latter are those from the impacts.txt file created in step 1. d) If your golden image has the HPVM-Guest bundle installed (recommended), then youll want to make sure the dynamic memory device driver is configured correctly. To achieve this, add the following line after the init sw_sel stanza: set_kernel += "module hpvmdynmem loaded"

The resulting section will then read as follows: (is_ia64) { init sw_sel "B.11.23 IA golden image archive" { description = "HPUX 11.23 image for VMs" sw_source = "golden image archive" sw_category = "HPUXEnvironments" archive_type = gzip tar archive_path = "B.11.23_VM_archive.gz" impacts impacts impacts impacts impacts impacts impacts impacts impacts impacts } = TRUE} = = = = = = = = = = / 833Kb /dev 13Kb /etc 82077Kb /home 133696Kb /opt 2536512Kb /sbin 111333Kb /scratch 135843Kb /stand 52187Kb /usr 2396952Kb /var 1603044Kb

set_kernel += "module hpvmdynmem loaded"

5. Edit the file /var/opt/ignite/INDEX to install the new configuration for Ignite-UX. This is done by adding a new cfg section to that file. For our example, the new cfg section would read as follows: cfg "HP-UX B.11.23 VM Config" { description "This selection supplies the VM configuration." "/opt/ignite/data/Rel_B.11.23/config" "/var/opt/ignite/data/Rel_B.11.23/vm.cfg" "/var/opt/ignite/config.local" }

6. Verify the syntax of your newly-entered configuration information with the following command: # /opt/ignite/bin/instl_adm T If this command is successful, your configuration is now ready to use.

Appendix B Creating and Configuring a Golden Image as an ISO Image

This section outlines the steps necessary to create such an ISO image for use as a virtual DVD with Integrity VMs. Once a golden system is defined, you need to make sure that there is enough file system space for the golden image and the resulting ISO image. For example, if the system image is 3GB in size, then you will need a directory with 3GB available space for the golden image and another directory with 3GB available space for the ISO image. One important thing to keep in mind when creating an ISO image is that these tools are designed to be used to create installation media on CD or DVD. As a result, the overall size of the ISO image is not expected to be more than approximately 4GB. Older versions of these tools were even limited to golden images of no more than 2GB. You will need to install the Ignite-UX utilities software on the golden system. Version C.6.5.61 or later of B5725AA (IgniteUX) and Ignite-UX-11-23 (HP-UX Installation Utilities for Installing 11.23 Systems) is highly recommended so that larger ISO images (up to 4GB) can be accommodated. After the golden system is prepared, the ISO image is created with the following steps. Making the operating system archive The operating system archive is created locally on the golden system itself with the following command: # /opt/ignite/data/scripts/make_sys_image \ -s local -d /scratch/staging -n vm.gz This will create a golden system archive file with the name vm.gz on the local system in the directory /scratch/staging. It may take several minutes to complete. Creating an archive configuration file An archive configuration file must be created for the golden image. First, capture the necessary impacts statements to be used in the configuration file by executing: # /opt/ignite/lbin/archive_impact -t -g ./vm.gz > impacts.txt in the directory where the system archive file was created (/scratch/staging for our example). This may take several minutes to complete. Now create a configuration file by copying the example configuration file to the directory with the system archive. In this case, use the archives.cfg file for your particular operating system. For example:

# cp p /opt/ignite/data/examples/B.11.23.archives.cfg \ /scratch/staging/vm.cfg Youll need to customize the configuration file for your archive. Two modifications of the (is_ia64) section are necessary. First, change the archive_path so that it reflects the path of the operating system archive file. For example, in the vm.cfg file, change: archive_path = "data/B.11.23_archive_IA.gz" to: archive_path = "./vm.gz" Then replace all of the impacts entries in the init sw_sel stanza with those from those from the impacts.txt file (created above). You can remove the (is_hppa) section from the configuration file. If your golden image has the HPVM-Guest bundle installed, then youll want to make sure the dynamic memory device driver is configured correctly. To achieve this, add the following line after the init sw_sel stanza: set_kernel += "module hpvmdynmem loaded" For our example, the section would then read as follows: (is_ia64) { init sw_sel "B.11.23 client archive IA" { description = "B.11.23 client archive IA" sw_source = "hp client archives" sw_category = "HPUXEnvironments" archive_type = gzip tar archive_path = "./vm.gz" impacts = "/" 241Kb impacts = "/cfs" 1Kb impacts = "/dev" 13Kb impacts = "/etc" 82004Kb impacts = "/home" 13369Kb impacts = "/stand" 52187Kb impacts = "/usr" 2396952Kb impacts = "/var" 1603493Kb } = TRUE } set_kernel += "module hpvmdynmem loaded"

Creating a copy of the LIF volume The ISO image must contain a LIF volume. Execute the following to create it: # /opt/ignite/bin/make_medialif -a -r B.11.23 \ -f /opt/ignite/data/Rel_B.11.23/config \ -f /scratch/staging/vm.cfg \ -l /scratch/stging/vm.lifimage Note the specification of two configuration files with the f option. These are concatenated together for use by make_medialif.

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 Itaniumbased 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.

Moving the ISO image to the Integrity VM Host Once youve verified it to be a valid LIF image, move it to the Integrity VM Host by whatever means is most efficient in your environment (for example, using ftp). A final note with regard to creating ISO images from golden images larger than 2GB - version C.6.5.61 or later of IgniteUX is required. Earlier versions of Ignite-UX may result in a failure during OS installation using such an image, producing a message similar to the following: * Thu Nov 03 12:37:56 EST 2005: Starting archive load of the source (B.11.23 client archive IA). * Completed 0% of archive

gunzip: stdin: unexpected end of file pax_iux: The archive is empty. ERROR: Cannot load OS archive (B.11.23 client archive IA)

The configuration process has incurred an error, would you like to push a shell for debugging purposes? (y/[n]): In such cases it is recommended that you upgrade Ignite-UX to the latest version.

2007 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Itanium is a trademark or registered trademark of Intel Corporation in the U.S. and other countries and is used under license. Rev 3.0, 7/2007