Installing in VM

Log onto VM as the user maintaining Linux installations. You can use x3270 or c3270 (from the x3270-text package in Red Hat Linux) to log in to VM from other Linux systems. Alternatively, use the OS/2 3270 terminal emulator on the s390 management console. If you are working from a Windows based machine, Jolly Giant (http://www.jollygiant.com) has a decent SSL enabled 3270 emulator.

If you aren't already in CMS mode, enter it now.

i cms

FTP to the machine containing the Red Hat Linux boot images, log in, and execute the following commands:

	Note
	If you are using the OCO driver modules, be sure to copy the initrd64.bin modified by the prepinitrd script from the RedHat/Drivers/ directory instead of the one in images/ to the host machine.

• cd /where/the/boot/images/are

• locsite fix 80

• bin

• get vmkrnl64.bin (repl

• get initrd64.bin (repl

• ascii

• mget *.parm redhat.* (repl

• quit

You may now customize the parameter file (inst64.parm). See Appendix B for several examples of parm files. Below is an explanation of the parm file contents.

	Note
	The limit on the parameters in the parm file is a max of 9 (nine). All others supplied parameters will not be set by the boot kernel, thus forcing a prompt during boot of the installation program. This count includes the basic root=/dev/ram0 ro ip=off which count as 3 (three) separate parameters leaving only 6 (six) more parameters that could be added.

root=/dev/ram0 ro ip=off

These values are given directly to the linux kernel and should be left as provided.

HOST=<...>

DASD=x-y[,a-c...]

Range of addresses of your DASD devices. 200-20f should be sufficient in most cases. Example: DASD=200-20f,B01-B03,F01

DTZ=timezone

Default time zone as returned by the linux tzselect-utility, Examples: DTZ=Europe/Berlin or DTZ=America/Chicago

LCS=lcs|qeth<dev_num>,<read>,<write>,<data (qeth only, ignored otherwise)>,<memory_usage>,<port_no/protocol_no>, <checksum_received_ip_pkts>,<use_hw_stats>

	Note
	The above LCS line values have been broken into segments for easier reading. Ideally, everything listed after LCS= should be included as one line.

• <dev_num> is the device number that is appended to qeth (values of -1 indicates driver chooses the value and leaving this field blank will change <read> and <write> to a probe range for non-qeth devices).

• <read> is the read address.

• <write> is the write address.

• <memory_usage> is the amount of memory in kilobytes to allow the driver to use.

• <port_no/protocol_no> allows a port number or protocol to be specified for use by the driver.

• <check-sum_received_ip_pkts> performs error checking on the packets.

• <use_hw_stats> makes the driver keep statistics on the hardware being used.

If one or more of the fields are not specified, the default values are used. For example:

LCS=lcs0,0x9a4,0x9a5,0,0 for OSA-2 with LCS, where read=0x9a4 
and write=0x9a5.

QETH=qethINCLUDE>,<read>,<write>,<data>, <memory_usage>,<port_no/protocol_no>,<checksum_received_ip_pkts>, <use_hw_stats>

	Note
	The above QETH line values have been broken into segments for easier reading. Ideally, everything listed after QETH= should be included as one line.

• <dev_num> is the device number that is appended to qeth (values of -1 indicates driver chooses the value and leaving this field blank will change <read> and <write> to a probe range for non-qeth devices).

• <read> is the read address.

• <write> is the write address.

• <memory_usage> is the amount of memory in kilobytes to allow the driver to use.

• <port_no/protocol_no> allows a port number or protocol to be specified for use by the driver.

• <check-sum_received_ip_pkts> performs error checking on the packets.

• <use_hw_stats> makes the driver keep statistics on the hardware being used.

For example:

QETH=qeth1,0x0fc00,0xfc01,0x7c02 for an OSA-Express with QDIO/QETH, where
read=0x7c00, write=0x7c01, and data=0x7c02.

NETWORK=IP:netmask:broadcast[:gw]

where, IP is your S/390 virtual machine IP; netmask the netmask; broadcast the broadcast address; gw the gateway-IP for your eth device (for eth-device only).

DNS=list:of:dns:servers

The list of DNS servers, separated by colons. Examples: DNS=10.0.0.1:10.0.0.2 will use the DNS servers 10.0.0.1 and 10.0.0.2

SEARCHDNS=list:of:search:domains

The list of the search domains, separated by colons. Example: SEARCHDNS=redhat.com:redhat.de

RPMSERVER=ftp://your.ftp.server/your.s390x.rpm.dir

To access the S/390 zSeries binary RPM packages via FTP.

RPMSERVER=http://your.http.server/your.s390x.rpm.path

To access the S/390 zSeries binary RPM packages via HTTP.

RPMSERVER=IP:/your.s390x.rpm.dir

Give the IP address of the NFS server containing the S/390 zSeries binary RPM packages (e.g. via an NFS mount of the Red Hat Linux for S/390 zSeries CD-ROM).

MOUNTS=dev:mountpoint,dev2:mountpoint2

This defines a comma-delimited list of the DASD device-partitions and where they should be mounted by default. Example: MOUNTS=/dev/dasda1:/,/dev/dasdb1:/usr/share,/dev/dasdc1:/tmp

SWAP=list:of:swap:devices

The list of initial swap devices, delimeted by colons. Example: SWAP=/dev/dasds1:/dev/dasdw1:/dev/dasdp1

DEBUG=<value>

If you encounter problems during an install, set DEBUG to any value to get a shell at certain steps during an installation.

CTC=ctc0,<read_channel_address>,<write_channel_address>

This setup parameter will allow the ctc driver to properly connect to the ctc read and write channels if connections are reversed. If the CTC parameter is not set, the driver will default to detected settings, which, depending on the system setup, the ctc read and write channels may be reversed. Example: CTC=ctc0,05b5,05b6 — As an alternative to setting this parameter, the read and write channel connections can be physically swapped.

If any of the network parameters required to make the network operate correctly are omitted from the parm file, a prompt will be appear during the installation boot process.

Next, if the guest id under which you wish to install is under a different guest, then log out of the 3270 VM session.

#cp log

If you logged off, reconnect and log in using the VM guest ID you configured earlier for the install. If you are not in CMS mode, enter it now.

i cms

Run the inst64 script.

inst64

Answer any questions the script asks you (if you've set up the inst64.parm file, you shouldn't be asked anything). When the bootup process is complete, telnet to your S390 machine, if prompted, log in as root (any password will work), and run rhsetup. Refer to Chapter 3 for instructions on using the installation program.

When the installation is finished, set up your linux virtual machine to boot from the DASD (virtual harddisk) rather than entering CMS or CP. This is done by setting the IPL address to the address of the DASD, usually 200.

Once installation is complete and the installed system is running (after IPLing from 200 for example), disconnect from 3270 using

#cp disc

rather than logging out — logging out will stop the virtual Linux machine.

To continue with the installation, refer to Chapter 3 for further instructions.