Hi Thang,
I noticed this line during your IPL:
00: NO FILES CHANGED
Are you purging the reader before punching and IPLing? I copied/pasted
your PARM file, and it worked for me. For reference, here's my exec:
/* EXEC to punch RHEL 5 64-bit install */
'CP SPOOL PUN *'
'CP CLOSE RDR'
'PUR RDR ALL'
'PUN RH53 KERNEL * (NOH'
'PUN 'userid()' PARM * (NOH'
'PUN RH53 INITRD * (NOH'
'CH RDR ALL KEEP'
'IPL 00C CLEAR'
I wonder if you were IPL'ing an old copy of the PARM file (I noticed the
vnc/vncpasswd options are missing from the kernel cmdline output, which
may confirm this theory).
-Brad
Thang Pham wrote:
Hi Brad, I took you advice and put everything in the parm file. I have
the following in my parm file:
root=/dev/ram0 ro ip=off ramdisk_size=40000
DASD=0.0.0100,0.0.0101 HOSTNAME=gpok6.endicott.ibm.com
NETTYPE=qeth IPADDR=10.0.0.6
SUBCHANNELS=0.0.0800,0.0.0801,0.0.0802
NETWORK=10.0.0.0 NETMASK=255.255.255.0
SEARCHDNS=endicott.ibm.com BROADCAST=10.0.0.255
GATEWAY=10.0.0.1 DNS=9.0.2.11 MTU=1500
PORTNAME=UNASSIGNED PORTNO=0 LAYER2=0
vnc vncpassword=123456
When the virtual server IPL 000C, which is where the kernel, parm, and
initrd are punched to, I get the following message:
Which kind of network device do you intend to use
(e.g. ctc, iucv, qeth, lcs).
Enter 'qeth' for OSA-Express Fast Ethernet, Gigabit Ethernet
(including 1000Base-T), High Speed Token Ring, and ATM
(running Ethernet LAN emulation) features in QDIO mode.
Enter 'lcs' for OSA 2 Ethernet/Token Ring, OSA-Express Fast Ethernet in
non-QDIO mode, OSA-Express High Speed Token Ring in non-QDIO mode and
Gigabit Ethernet in non-QDIO mode.
It looks like the parm file was never read. I see this at the beginning
when the virtual server IPLed 000C:
RDR FILE 0121 SENT FROM LINUX254 PUN WAS 0142 RECS 048K CPY 001 A NOHOLD
NOKEEP
RDR FILE 0122 SENT FROM LINUX254 PUN WAS 0143 RECS 0005 CPY 001 A NOHOLD
NOKEEP
RDR FILE 0123 SENT FROM LINUX254 PUN WAS 0144 RECS 117K CPY 001 A NOHOLD
NOKEEP
00: NO FILES CHANGED
Linux version 2.6.18-128.el5 ([email protected]) (gcc version
4.1.2
20080704 (Red Hat 4.1.2-44)) #1 SMP Wed Dec 17 11:45:02 EST 2008
We are running under VM (64 bit mode)
Detected 2 CPU's
Boot cpu address 0
Built 1 zonelists. Total pages: 131072
Kernel command line: root=/dev/ram0 ro ip=off ramdisk_size=40000
DASD=0.0.0100,0.0.0101 HOSTNAME=gpok6.endicott.ibm.com
NETTYPE=qeth IPADDR=10.0.0.6
SUBCHANNELS=0.0.0800,0.0.0801,0.0.0802
NETWORK=10.0.0.0 NETMASK=255.255.255.0
SEARCHDNS=endicott.ibm.com BROADCAST=10.0.0.255
GATEWAY=10.0.0.1 DNS=9.0.2.11 MTU=1500
PORTNAME=UNASSIGNED PORTNO=0 LAYER2=0
What could be wrong?
---------------------------------
Thang Pham
IBM Poughkeepsie
---------------------------------
From:
Brad Hinson <[email protected]>
To:
[email protected]
Date:
10/31/2009 11:17 AM
Subject:
Re: RHEL install
Sent by:
Linux on 390 Port <[email protected]>
Hi Thang,
Yes, you can definitely install without a CONF file. You would just put
everything into the PARM file, and not specify CMSCONFFILE= or CMSDASD=.
In fact, this is how it's done with zPXE, the PXE client for
cobbler/Satellite. For example, see here:
https://fedorahosted.org/cobbler/wiki/SssThreeNinety
(sample PARM file towards the bottom)
Keep in mind though that the PARM file has an architectural limit of 11
lines (880 characters), so you have to be clever and fit as many
parameters on an 80 character line as possible.
-Brad
Thang Pham wrote:
Is there a way to install RHEL on s390x architecture without the need to
specify a CONF file and putting the CONF file on a CMS disk? Can I
append
the configuration onto the PARM file and punch it to reader (which I
tried
but does not work)?
According to Red Hat, "A .parm file is still required for the real
kernel
parameters, such as root=/dev/ram0 ro ip=off ramdisk_size=40000, and
single parameters which are not assigned to variables, such as vnc. Two
parameters which are used in z/VM installs to point the installation
program at the new CMS configuration file need to be added to the .parm
file:
CMSDASD=191 CMSCONFFILE=redhat.conf
CMSDASD is the device ID of the CMS formatted DASD which contains the
configuration file. CMSDASD is often the 'A' DASD (usually disk 191) of
the z/VM guest account. The name of the configuration file must be set
with CMSCONFFILE and needs to be all lowercase." (
http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.4/html/Installation_Guide/s1-s390-steps-vm.html
)
Thank you,
---------------------------------
Thang Pham
IBM Poughkeepsie
---------------------------------
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
Brad Hinson <[email protected]>
Sr. Support Engineer Lead, System z
Red Hat, Inc.
(919) 754-4198
www.redhat.com/z
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
Brad Hinson <[email protected]>
Sr. Support Engineer Lead, System z
Red Hat, Inc.
(919) 754-4198
www.redhat.com/z
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
