Actually I use filel <f11> to edit the file. The line numbers are from
the editor. It seems that a copy and paste function adds in the commas
after the line numbers. I apologize for the confusion.
To answer the other question, I am using the redhat command after i cms.
Here is the complete boot output up to the panic. This sequence starts
from me entering redhat.
Ready; T=0.01/0.01 12:27:20
redhat
0000002 FILES PURGED
RDR FILE 0013 SENT FROM PTL511 PUN WAS 0013 RECS 033K CPY 001 A NOHOLD
NOKEEP
DMSOPN002E File REDHAT PRM A not found
RDR FILE 0014 SENT FROM PTL511 PUN WAS 0014 RECS 060K CPY 001 A NOHOLD
NOKEEP
0000002 FILES CHANGED
0000002 FILES CHANGED
hwc low level driver: can write messages
hwc low level driver: can not read state change notifications
hwc low level driver: can read commands
hwc low level driver: can read priority commands
Linux version 2.4.9-37BOOT ([EMAIL PROTECTED]) (gcc version 2.95.3
20010315 (r
elease)) #1 SMP Wed Apr 24 17:32:38 CEST 2002
We are running under VM
This machine has an IEEE fpu
On node 0 totalpages: 32768
zone(0): 32768 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: I
Highest subchannel number detected (hex) : 0018
Calibrating delay loop... 732.36 BogoMIPS
Memory: 124440k/131072k available (1626k kernel code, 0k reserved, 844k
data, 64
k init)
Dentry-cache hash table entries: 16384 (order: 5, 131072 bytes)
Inode-cache hash table entries: 8192 (order: 4, 65536 bytes)
Mount-cache hash table entries: 2048 (order: 2, 16384 bytes)
Buffer-cache hash table entries: 8192 (order: 3, 32768 bytes)
Page-cache hash table entries: 32768 (order: 6, 262144 bytes)
debug: Initialization complete
debug: reserved 4 areas of 4 pages for debugging ccwcache
POSIX conformance testing by UNIFIX
Detected 1 CPU's
Boot cpu address 0
cpu 0 phys_idx=0 vers=FF ident=0F11AA machine=2064 unused=0000
init_mach : starting machine check handler
init_mach : machine check buffer : head = 0023EDF0
init_mach : machine check buffer : tail = 0023EDF4
init_mach : machine check buffer : free = 0023EDF8
init_mach : CRW entry buffer anchor = 0023EDFC
init_mach : machine check handler ready
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
mach_handler : ready
mach_handler : waiting for wakeup
Starting kswapd v1.8
VFS: Diskquotas version dquot_6.5.0 initialized
pty: 256 Unix98 ptys configured
block: queued sectors max/low 82506kB/27502kB, 256 slots per queue
RAMDISK driver initialized: 16 RAM disks of 35840K size 1024 blocksize
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
debug: reserved 4 areas of 16 pages for debugging cio_msg
debug: cio_msg: new level 2
debug: reserved 4 areas of 16 pages for debugging cio_trace
debug: cio_trace: new level 2
debug: reserved 4 areas of 4 pages for debugging cio_crw
debug: cio_crw: new level 6
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 512 buckets, 8Kbytes
TCP: Hash tables configured (established 4096 bind 8192)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
VFS: Cannot open root device "" or 01:00
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 01:00
HCPGIR450W CP entered; disabled wait PSW 000A0000 8026E38A
Hopefully this helps, at least to clear up confusion.
Thanks!
Eric Sammons
(804)697-3925
FRIT - Infrastructure Engineering
"Post, Mark K" <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port <[EMAIL PROTECTED]>
07/21/2003 11:59 AM
Please respond to Linux on 390 Port
To: [EMAIL PROTECTED]
cc:
Subject: Re: Attempting to install Redhat 7.2 in a VM
Adam already mentioned the possibility that you might not have punched the
initrd file to the reader (although if you _named_ it correctly, the
redhat
exec will do that automatically). I'm more concerned about the contents
of
your redhat parm file. Do you really have line numbers in it? Is there
really a comma in front of the "root=/dev/ram0" parameter? If the answer
to
either of these is "yes" then that is at least part of your problem.
Mark Post
-----Original Message-----
From: Eric Sammons [mailto:[EMAIL PROTECTED]
Sent: Monday, July 21, 2003 11:06 AM
To: [EMAIL PROTECTED]
Subject: Attempting to install Redhat 7.2 in a VM
Our organization has been doing a Proof of Concept.. This initiative
started with SuSE Linux, which we have tested etc. . . we are now ready
to look at Redhat; however, I am having difficulty booting up after my
initial prep work.
I am installing into a VM, I have found the instructions (or lack there
of) for install 7.2 into a VM. My REDHAT PARAM file looks as follows:
00000,* * * Top of File * * *
00001,root=/dev/ram0 ro ip=off DASD=292,200,201
00002,HOST=myhost.somewhere.something:hsi0:xxx.xxx.xxx.xxx
00003,NETWORK=xxx.xxx.xxx.xxx:255.255.255.224:xxx.xxx.xxx.xxx:xxx.xxx.xxx.xx
x
00004,RPMSERVER=xxx.xxx.xxx.xxx:/ftp/RedHat
00005,/dev/dasdb1:/,/dev/dasdc1:/usr
00006,INSTALL=default DTZ=EST5EDT
00007,SWAP=/dev/dasda1
00008,* * * End of File * * *
Once I execute the "redhat" command to begin boot up I receive the
following panic:
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
VFS: Cannot open root device "" or 01:00
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 01:00
HCPGIR450W CP entered; disabled wait PSW 000A0000 8026E38A
Has anyone seen this before and if so any idea what I have configured
incorrectly? I am certain it is something I have done as I am really new
to this z/VM environment.
Thanks!
Eric Sammons
FRIT - Infrastructure Engineering
