Installing The Suse Linux Enterprise Server Starter System For System Z; Preparing The Virtual Machine - Novell LINUX ENTERPRISE SERVER STARTER SYSTEM Installation Manual

Installing the SUSE Linux Enterprise Server Starter
System for System z
This section describes a step by step installation of the SUSE Linux Enterprise Server
Starter System for System z.
For illustration purposes, the installation procedure assumes you will use VM userid
NOVSTART for the starter system as shown in the sample CP directory entry file. Any
userid may be used, however you will need to modify this procedure according to your
local conventions.

Preparing the Virtual Machine

10

Installing the SUSE Linux Enterprise Server Starter System for System z

Be Sure to Read the Procedure Completely Before Beginning
To make sure you understand the process and steps, read the entire procedure through
at least one time from start to finish and ensure that you have completed the planning
worksheets and have all the materials ready before beginning to install the starter
system.
1. Create the virtual machine NOVSTART using your local CP directory maintenance
procedures. Note that the MDISK entries in the sample directory entry are com-
mented out, and should be used for guidance and disk sizing. The real entries will be
added in a later step.
Elevated CP Privileges Are Not Required
The starter system virtual machine does not require any privileges beyond the
normal class G privileges available to an ordinary z/VM user. You should not
grant the starter system virtual machine any additional privileges unless you fully
understand the results and risks associated.
2. Add the minidisks specified in the worksheet using your local directory management
procedures. You can use the comments in the sample directory entry or the planning
worksheet values to estimate the amount of space needed.
If using 3390 model 3 volumes, approximately two full volumes will be required. If
using 3390 model 9 or 27 volumes, only a fraction of one volume will be required,
however there will be a performance impact if all the minidisks are located on the
same volume.
If you are not using an external security manager such as RACF on your z/VM
system, ensure that you add minidisk passwords to the minidisks. The 19F minidisk
will need public access, and should be assigned a read password of ALL. Example
MDISK entries might appear similar to these: