16.6. Installing under z/VM
If you are not in CMS mode, enter it now.
If necessary, add the device containing z/VM's TCP/IP tools to your CMS disk list. For example:
vmlink tcpmaint 592 592
If using any of the qdio/qeth based network connection types (such as OSA express or hipersockets), set the VM guest qioassist parameter off:
set qioassist off
FTP to the machine containing the boot images (
initrd.img), log in, and execute the following commands (use the
(repl option if you are overwriting existing
initrd.img image files):
You may now create the parameter file (for example,
). Refer to Chapter 19, Sample Parameter Files
files. Below is an explanation of the
There is a limit of 32 total parameters in the parameter file. In order to accommodate limitations with parameter files, a new configuration file on a CMS DASD should be used to configure the initial network setup and the DASD specification.
.parm file is still required for the
kernel parameters, such as
root=/dev/ram0 ro ip=off ramdisk_size=40000
, and single parameters which are not assigned to variables, such as
. Two parameters which are used in z/VM installs to point the installation program at the new CMS configuration file need to be added to the
CMSDASD is the device ID of the CMS formatted DASD which contains the configuration file. CMSDASD is often the 'A' DASD (usually disk 191) of the z/VM guest account. The name of the configuration file must be set with CMSCONFFILE and needs to be all lowercase.
The syntax of the CMSCONFFILE is bash style with
pairs, one on each line.
root=/dev/ram0 ro ip=off ramdisk_size=40000
'purge rdr all'
'spool punch * rdr'
'PUNCH KERNEL IMG A (NOH'
'PUNCH REDHAT PARM A (NOH'
'PUNCH INITRD IMG A (NOH'
'ch rdr all keep nohold'
The following parameters are required and must be included in the parameter file:
represents the list of DASD devices to be used by Red Hat Enterprise Linux.
Although autoprobing for DASDs is done if this parameter is omitted, it is highly recommended to include the
DASD= parameter, as the device numbers (and therefore the device names) can vary when a new DASD is added to the Red Hat Enterprise Linux guest. This can result in an unusable system.
Additionally, in SAN-based environments, autoprobing in an LPAR-based install may have unintended side effects, as the number of DASD and SCSI volumes visible may be unexpectedly large and include volumes currently in use by other users. In particular, autoprobing during a kickstart install (which may have enabled autopartitioning to clear all partitions) is highly discouraged.
represents the device on which the root file system can be found. For installation purposes, it should be set to
/dev/ram0, which is the ramdisk containing the Red Hat Enterprise Linux installation program.
The following parameters are required to set up networking:
Provides required device bus IDs for the various network interfaces.
qeth: SUBCHANNELS="read_device_bus_id,write_device_bus_id, data_device_bus_id"
For example (a sample qeth SUBCHANNEL statement):
The following parameters are optional:
is the hostname of the newly-installed Linux guest.
must be one of the following:
is the IP address of the new Linux guest.
is the address of your network.
is the netmask.
is the broadcast address.
is the gateway-IP for your
is the Maximum Transmission Unit (MTU) for this connection.
is a list of DNS servers, separated by colons. For example:
is a list of the search domains, separated by colons. For example:
This variable supports OSA devices operating in qdio mode or non-qdio mode.
When using qdio mode:
is the portname specified on the OSA device when operating in qeth mode. PORTNAME is only required for z/VM 4.3 or older without APARs VM63308 and PQ73878.
When using non-qdio mode:
is used to pass the relative port number as integer in the range of 0 through 15.
FCP_n="device_number SCSI_ID WWPN SCSI_LUN FCP_LUN"
The variables can be used on systems with FCP devices to preconfigure the FCP setup and can be subsequently edited in anaconda during the installation. An example value may look similar to:
FCP_1="0.0.5000 0x01 0x5105074308c212e9 0x0 4010"
is an integer value (e.g.
is used to specify the address of the FCP device (
0.0.5000 for device 5000, for example).
is specified in hex-value, typically sequential values (e.g.
0x02 ... ) are used over multiple FCP_ variables.
is the world wide port name used for routing (often in conjunction with multipathing) and is as a 16-digit hex value (e.g.
refers to the local SCSI logical unit value and is specified as a hex-value, typically sequential values (e.g. 0x00, 0x01, ...) are used over multiple FCP_ variables.
refers to the storage logical unit identifier and is specified as a hex-value (such as
Each of the values used in the FCP parameters (FCP_1, FCP_2, ...) are site-specific and are normally supplied by the FCP storage administrator.
Update for Red Hat Enterprise Linux 5.3
Anaconda now supports both ports on CHPID for OSA Express3 cards. The installer will prompt for the port number in the initial stage of the installation. The value provided for the port also affects installed network interface startup script. When port 1 is selected, the value "portno=1" is added to OPTIONS parameter of ifcfg-eth* file.
When installing under z/VM, you can add either
(to use port 0) or
(to use port 1) to the CMS configuration file to avoid being prompted for the mode.
Update for Red Hat Enterprise Linux 5.2
When installing on a System z guest for
Red Hat Enterprise Linux 5.2
, you can make the mode persistent by adding either
to the CMS configuration file. Use
when the OSA is in layer 3 mode, and
when the OSA is in layer 2 mode.
, you can also specify
when connecting to a
when connecting directly to the OSA. If a VSWITCH is not in use, specify the MAC address in the CMS configuration file using the parameter MACADDR=
The following parameters for kickstart installations are optional:
is defined as
1 if you want to run the installation program in noninteractive (kickstart) mode in the 3270 terminal, or
cmdline is specified, 3270 terminal output becomes much more readable, as the installer disables most escape terminal sequences that are applicable to unix-like consoles, but not supported on the 3270 console.
Make sure that your kickstart file contains all required parameters before you use either of the RUNKS of cmdline options.
If any of the network parameters required to make the network operate correctly are omitted from the
parm file, a prompt appears during the installation boot process.
If you logged off, reconnect and log in using z/VM guest ID you configured for installation. If you are not in CMS mode, enter it now.
Create an executable script containing the commands necessary to IPL the kernel image and start the installation. The following sample script is a typical initial start-up script:
/* */ 'CL RDR' 'PURGE RDR ALL' 'SPOOL PUNCH * RDR' 'PUNCH KERNEL IMG A (NOH' 'PUNCH REDHAT PARM A (NOH' 'PUNCH INITRD IMG A (NOH' 'CH RDR ALL KEEP NOHOLD' 'IPL 00C CLEAR'
The initial installation start-up script prompts you for information about your networking and DASDs unless you have specified all necessary information in the