The Virtualization Cookbook for SLES 10 SP2 - z/VM - IBM
The Virtualization Cookbook for SLES 10 SP2 - z/VM - IBM
The Virtualization Cookbook for SLES 10 SP2 - z/VM - IBM
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
'CP XAUTOLOG DTCVSW2' /* start VSWITCH controller 2 */<br />
'cp set pf12 ret' /* set the retrieve key */<br />
'cp set mdc stor 0m 128m' /* Limit minidisk cache in CSTOR */<br />
'cp set mdc xstore 0m 0m' /* Disable minidisk cache in XSTOR */<br />
'cp set srm storbuf 300% 250% 200%' /* Overcommit memory */<br />
'cp set signal shutdown 300' /* Allow guests 5 min to shut down */<br />
/* Grant access to VSWITCH <strong>for</strong> each Linux user */<br />
'cp set vswitch vsw1 grant rh6clone'<br />
/* XAUTOLOG each Linux user that should be started */<br />
'cp xautolog rh6clone'<br />
'cp logoff' /* logoff when done */<br />
====> file<br />
<strong>The</strong>se changes will not take effect until the next IPL, so you must grant this user ID access to<br />
the VSWITCH <strong>for</strong> this z/<strong>VM</strong> session. This is done as follows:<br />
==> set vswitch vsw1 grant rh6clone<br />
Command complete<br />
7.1.3 Preparing RH6CLONE bootstrap files<br />
To IPL a RHEL 6 installation system, four bootstrap files must be prepared. Three are<br />
punched to z/<strong>VM</strong> reader and then IPLed. <strong>The</strong>se three files IPLed are a kernel, a parameter<br />
file and an initial RAMdisk. <strong>The</strong> fourth file is a configuration file stored on a CMS disk that the<br />
parameter file points to.<br />
Think of these as the files that are on as a PC Linux boot CD (or floppy disk). Also, a small<br />
REXX EXEC is commonly used to clean out the reader, punch the three files and IPL the<br />
reader. A sample RHEL 6 parameter file, configuration file and install EXEC are supplied and<br />
should be on the LNXMAINT 192 disk (this task is in section 4.7.5, “Copying files associated<br />
with this book to LNXMAINT” on page 60). <strong>The</strong>re<strong>for</strong>e, only the kernel and RAMdisk need to<br />
be copied.<br />
► Start an SSH session as root on the NFS server.<br />
► Use the ftp command to copy the RHEL 6 kernel and initial RAMdisk to LNXMAINT’s D disk.<br />
<strong>The</strong>se files must have a record <strong>for</strong>mat of fixed 80 byte records. This <strong>for</strong>mat can be set with<br />
the site fix 80 FTP subcommand (if this subcommand fails, try quote site fix 80).<br />
Following is an example:<br />
# cd /nfs/rhel6/dvd1/images<br />
# ftp 9.60.18.249<br />
Name (9.60.18.249:root): lnxmaint<br />
Password:<br />
230 LNXMAINT logged in; working directory = LNXMAINT 191<br />
Remote system type is z/<strong>VM</strong>.<br />
ftp> cd lnxmaint.192<br />
250 Working directory is LNXMAINT 192<br />
ftp> site fix 80<br />
200 Site command was accepted.<br />
ftp> bin<br />
200 Representation type is IMAGE.<br />
ftp> put initrd.img rhel6.initrd<br />
...<br />
23651842 bytes sent in 00:01 (11.34 MB/s)<br />
ftp> put kernel.img rhel6.kernel<br />
...<br />
Chapter 7. Installing RHEL 6 on the cloner <strong>10</strong>5