16.3. Installing under z/VM When installing under z/VM, you can boot from: the z/VM virtual reader a DASD or an FCP-attached SCSI device prepared with the zipl boot loader an FCP-attached SCSI DVD drive Log on to the z/VM guest virtual machine chosen for the Linux installation. You can use the x3270 or c3270 terminal emulator, available in the x3270-text package in Red Hat Enterprise Linux, to log in to z/VM from other Linux systems. Alternatively, use the IBM 3270 terminal emulator on the IBM Z Hardware Management Console (HMC). If you are working from a machine with a Microsoft Windows operating system, Jolly Giant ( http://www.jollygiant.com/ ) offers an SSL-enabled 3270 emulator. A free native Windows port of c3270 called wc3270 also exists. Note If your 3270 connection is interrupted and you cannot log in again because the session is still active, you can replace the old session with a new one by entering the following command on the z/VM logon screen: Replace user with the name of the z/VM guest virtual machine. Depending on whether an external security manager, for example RACF, is used, the logon command might vary. If you are not already running CMS (single-user operating system shipped with z/VM) in your guest, boot it now by entering the command: Be sure not to use CMS disks such as your A disk (often device number 0191) as installation targets. To find out which disks are in use by CMS, use the following query: You can use the following CP (z/VM Control Program, which is the z/VM hypervisor) query commands to find out about the device configuration of your z/VM guest virtual machine: Query the available main memory, which is called storage in IBM Z terminology. Your guest should have at least 1 GB of main memory. Query available network devices by type: osa OSA - CHPID type OSD, real or virtual (VSWITCH or GuestLAN), both in QDIO mode hsi HiperSockets - CHPID type IQD, real or virtual (GuestLAN type Hipers) lcs LCS - CHPID type OSE For example, to query all of the network device types mentioned above, run: Query available DASDs. Only those that are flagged RW for read-write mode can be used as installation targets: Query available FCP channels: 16.3.1. Using the z/VM Reader Perform the following steps to boot from the z/VM reader: If necessary, add the device containing the z/VM TCP/IP tools to your CMS disk list. For example: Replace fm with any FILEMODE letter. Execute the command: Where host is the host name or IP address of the FTP server that hosts the boot images ( kernel.img and initrd.img ). 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: Optionally, 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: Press PF3 to quit filelist and return to the CMS prompt. Customize boot parameters in generic.prm as necessary. See Section 16.1, "Customizing boot parameters" for details. 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 . See Section 21.2, "The z/VM Configuration File" for more details. Finally, execute the REXX script redhat.exec to boot the installation program: 16.3.2. Using a Prepared DASD Boot from the prepared DASD and select the zipl boot menu entry referring to the Red Hat Enterprise Linux installation program. Use a command of the following form: Replace DASD_device_number with the device number of the boot device, and boot_entry_number with the zipl configuration menu for this device. For example: 16.3.3. Using a Prepared FCP-attached SCSI Disk Perform the following steps to boot from a prepared FCP-attached SCSI disk: 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: 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: Optionally, confirm your settings with the command: Boot the FCP device connected with the storage system containing the disk with the following command: For example: 16.3.4. Using an FCP-attached SCSI DVD Drive This requires a SCSI DVD drive attached to an FCP-to-SCSI bridge which is in turn connected to an FCP adapter in your IBM Z. The FCP adapter must be configured and available under z/VM. Insert your Red Hat Enterprise Linux for IBM Z DVD into the DVD drive. Configure the SCSI boot loader of z/VM to access the DVD drive in the FCP Storage Area Network and specify 1 for the boot entry on the Red Hat Enterprise Linux for IBM Z DVD. Use a command of the following form: Replace WWPN with the WWPN of the FCP-to-SCSI bridge and FCP_LUN with the LUN of the DVD drive. The 16-digit hexadecimal numbers must be split into two pairs of eight characters each. For example: Optionally, confirm your settings with the command: IPL on the FCP device connected with the FCP-to-SCSI bridge. For example:

Commands:
logon user here
cp ipl cms
query disk
cp query virtual storage
cp query virtual osa
cp query virtual dasd
cp query virtual fcp
cp link tcpmaint 592 592 acc 592 fm
ftp host
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
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
redhat
cp ipl DASD_device_number loadparm boot_entry_number
cp ipl eb1c loadparm 0
cp set loaddev portname WWPN lun LUN bootprog boot_entry_number
cp set loaddev portname 50050763 050b073d lun 40204011 00000000 bootprog 0
query loaddev
cp ipl FCP_device
cp ipl fc00
cp set loaddev portname WWPN lun FCP_LUN bootprog 1
cp set loaddev portname 20010060 eb1c0103 lun 00010000 00000000 bootprog 1
cp query loaddev
cp ipl FCP_device
cp ipl fc00