Chapter 11. Booting the installation media

Procedure

1. Log in on the IBM Z Hardware Management Console (HMC) or the Support Element (SE) as a user with sufficient privileges to install a new operating system to an LPAR.
2. On the Systems tab, select the mainframe you want to work with, then on the Partitions tab select the LPAR to which you wish to install.
3. At the bottom of the screen, under Daily, find Operating System Messages. Double-click Operating System Messages to show the text console on which Linux boot messages will appear.
4. Double-click Load from Removable Media or Server.

5. In the dialog box that follows, select SFTP/FTPS/FTP Server, and enter the following information:

   • Host Computer - Host name or IP address of the FTP server you want to install from, for example ftp.redhat.com
   • User ID - Your user name on the FTP server. Or, specify anonymous.
   • Password - Your password. Use your email address if you are logging in as anonymous.
   • File location (optional) - Directory on the FTP server holding the Red Hat Enterprise Linux for IBM Z, for example /rhel/s390x/.
6. Click Continue.
7. In the dialog that follows, keep the default selection of generic.ins and click Continue.

Procedure

1. Log in on the IBM Z Hardware Management Console (HMC) or the Support Element (SE) as a user with sufficient privileges to install a new operating system to an LPAR.
2. On the Systems tab, select the mainframe you want to work with, then on the Partitions tab select the LPAR to which you wish to install.
3. At the bottom of the screen, under Daily, find Operating System Messages. Double-click Operating System Messages to show the text console on which Linux boot messages will appear.
4. Double-click Load.
5. In the dialog box that follows, select Normal as the Load type.
6. As Load address, fill in the device number of the DASD.
7. Click the OK button.

Procedure

1. Log in on the IBM Z Hardware Management Console (HMC) or the Support Element (SE) as a user with sufficient privileges to install a new operating system to an LPAR.
2. On the Systems tab, select the mainframe you want to work with, then on the Partitions tab select the LPAR to which you wish to install.
3. At the bottom of the screen, under Daily, find Operating System Messages. Double-click Operating System Messages to show the text console on which Linux boot messages will appear.
4. Double-click Load.
5. In the dialog box that follows, select SCSI as the Load type.
6. As Load address, fill in the device number of the FCP channel connected with the SCSI disk.
7. As World wide port name, fill in the WWPN of the storage system containing the disk as a 16-digit hexadecimal number.
8. As Logical unit number, fill in the LUN of the disk as a 16-digit hexadecimal number.
9. Leave the Boot record logical block address as 0 and the Operating system specific load parameters empty.
10. Click the OK button.

Procedure

1. If necessary, add the device containing the z/VM TCP/IP tools to your CMS disk list. For example:

   cp link tcpmaint 592 592
   acc 592 fm

   Replace fm with any FILEMODE letter.

2. For a connection to an FTPS server, enter:

   ftp <host> (secure

   Where host is the host name or IP address of the FTP server that hosts the boot images (kernel.img and initrd.img).

3. Log in and execute the following commands. Use the (repl option if you are overwriting existing kernel.img, initrd.img, generic.prm, or redhat.exec files:

   cd /location/of/install-tree/images/
   ascii
   get generic.prm (repl
   get redhat.exec (repl
   locsite fix 80
   binary
   get kernel.img (repl
   get initrd.img (repl
   quit

4. Optional: Check whether the files were transferred correctly by using the CMS command filelist to show the received files and their format. It is important that kernel.img and initrd.img have a fixed record length format denoted by F in the Format column and a record length of 80 in the Lrecl column. For example:

   VMUSER FILELIST A0 V 169 Trunc=169 Size=6 Line=1 Col=1 Alt=0

   Cmd Filename	Filetype	Fm	Format	Lrecl	Records	Blocks	Date	Time
   REDHAT	EXEC		B1	V	22	1 	1	4/15/10	9:30:40
   GENERIC	PRM		B1	V	44	1	1	4/15/10	9:30:32
   INITRD	IMG		B1	F	80	118545	2316	4/15/10	9:30:25
   KERNEL	IMG		B1	F	80	74541	912	4/15/10	9:30:17

   Press PF3 to quit filelist and return to the CMS prompt.

5. Customize boot parameters in generic.prm as necessary. For details, see Customizing boot parameters.

   Another way to configure storage and network devices is by using a CMS configuration file. In such a case, add the CMSDASD= and CMSCONFFILE= parameters to generic.prm.

6. Finally, run the REXX script redhat.exec to boot the installation program:

   redhat

Procedure

1. Configure the SCSI boot loader of z/VM to access the prepared SCSI disk in the FCP Storage Area Network. Select the prepared zipl boot menu entry referring to the Red Hat Enterprise Linux installation program. Use a command of the following form:

   cp set loaddev portname WWPN lun LUN bootprog boot_entry_number

   Replace WWPN with the World Wide Port Name of the storage system and LUN with the Logical Unit Number of the disk. The 16-digit hexadecimal numbers must be split into two pairs of eight digits each. For example:

   cp set loaddev portname 50050763 050b073d lun 40204011 00000000 bootprog 0

2. Optional: Confirm your settings with the command:

   query loaddev

3. Boot the FCP device connected with the storage system containing the disk with the following command:

   cp ipl FCP_device

   For example:

   cp ipl fc00