Re: Installing RHEL 7
Looping back around - a colleague got DHCP to work - "less is more" - a PARM file but no CONF file, almost no networking variables set, then DHCP kicks in: ro ramdisk_size=4 CMSDASD=191 rd.znet=qeth,0.0.0350,0.0.0351,0.0.0352,layer2=1 nameserver=10.10.10.10 nameserver=10.10.10.11 rd.dasd=0.0.0100 rd.dasd=0.0.0101 rd.dasd=0.0.0102 inst.repo=http://10.10.10.248/rhel vnc vncpassword=12345678 -Mike M On Thu, Nov 17, 2016 at 9:49 AM, Michael MacIsaac wrote: > Thanks Steffen for a thorough reply - we will dig on this... > > -Mike > > On Thu, Nov 17, 2016 at 9:21 AM, Steffen Maier > wrote: > >> Hi Mike, >> >> On 11/17/2016 01:15 PM, Michael MacIsaac wrote: >> >>> Is there any documentation on how to install RHEL 7 using DHCP? >>> >>> The current "Cookbook" only shows how to static IP (who wrote that thing? >>> :)) The Red Hat documentation on line alludes to DHCP, but does not have >>> a >>> specific example - perhaps I'm missing it. >>> >> >> The RHEL installation guide describes (a subset of) the "ip=" (pseudo) >> kernel parameter syntax: >> https://access.redhat.com/documentation/en-US/Red_Hat_Enterp >> rise_Linux/7/html/Installation_Guide/chap-installer-booting- >> ipl-s390.html#sect-customizing-generic-prm-s390 >> refers to: >> https://access.redhat.com/documentation/en-US/Red_Hat_Enterp >> rise_Linux/7/html/Installation_Guide/chap-anaconda-boot-opti >> ons.html#list-boot-options-network >> (It also occurs in the x- and p-specific network install chapter of which >> some parts are common code and also apply to z: >> https://access.redhat.com/documentation/en-US/Red_Hat_Enterp >> rise_Linux/7/html/Installation_Guide/chap-installation-server-setup.html) >> >> I think omitting the "ip=..." entirely also defaults to dhcp. >> >> A kickstart file itself also has some dhcp syntax (network >> --bootproto=dhcp): >> https://access.redhat.com/documentation/en-US/Red_Hat_Enterp >> rise_Linux/7/html/Installation_Guide/sect-kickstart-syntax.h >> tml#sect-kickstart-commands >> >> >> On z Systems you likely still need "rd.znet=..." if you use a native >> network device. >> >> >> The full syntax of the ip= parameter (not sure if RHEL supports all of >> this) is described for the dracut upstream project in >> https://www.kernel.org/pub/linux/utils/boot/dracut/dracut.html#_network. >> >> The anaconda upstream documentation has its own (subset?) copy under >> https://github.com/rhinstaller/anaconda/blob/master/docs/boo >> t-options.rst#network-options or https://rhinstaller.github.io/ >> anaconda/boot-options.html#network-options, but since RHEL7 uses dracut >> even for the installer initrd it's the same mechanism as in my previous >> paragraph. >> >> >> -- >> Mit freundlichen Grüßen / Kind regards >> Steffen Maier >> >> Linux on z Systems Development >> >> IBM Deutschland Research & Development GmbH >> Vorsitzende des Aufsichtsrats: Martina Koederitz >> Geschaeftsfuehrung: Dirk Wittkopp >> Sitz der Gesellschaft: Boeblingen >> Registergericht: Amtsgericht Stuttgart, HRB 243294 >> >> -- >> For LINUX-390 subscribe / signoff / archive access instructions, >> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or >> visit >> http://www.marist.edu/htbin/wlvindex?LINUX-390 >> -- >> For more information on Linux on System z, visit >> http://wiki.linuxvm.org/ >> > > -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Installing RHEL 7
Thanks Steffen for a thorough reply - we will dig on this... -Mike On Thu, Nov 17, 2016 at 9:21 AM, Steffen Maier wrote: > Hi Mike, > > On 11/17/2016 01:15 PM, Michael MacIsaac wrote: > >> Is there any documentation on how to install RHEL 7 using DHCP? >> >> The current "Cookbook" only shows how to static IP (who wrote that thing? >> :)) The Red Hat documentation on line alludes to DHCP, but does not have a >> specific example - perhaps I'm missing it. >> > > The RHEL installation guide describes (a subset of) the "ip=" (pseudo) > kernel parameter syntax: > https://access.redhat.com/documentation/en-US/Red_Hat_Enterp > rise_Linux/7/html/Installation_Guide/chap-installer-booting- > ipl-s390.html#sect-customizing-generic-prm-s390 > refers to: > https://access.redhat.com/documentation/en-US/Red_Hat_Enterp > rise_Linux/7/html/Installation_Guide/chap-anaconda-boot- > options.html#list-boot-options-network > (It also occurs in the x- and p-specific network install chapter of which > some parts are common code and also apply to z: > https://access.redhat.com/documentation/en-US/Red_Hat_Enterp > rise_Linux/7/html/Installation_Guide/chap-installation-server-setup.html) > > I think omitting the "ip=..." entirely also defaults to dhcp. > > A kickstart file itself also has some dhcp syntax (network > --bootproto=dhcp): > https://access.redhat.com/documentation/en-US/Red_Hat_Enterp > rise_Linux/7/html/Installation_Guide/sect-kickstart-syntax. > html#sect-kickstart-commands > > > On z Systems you likely still need "rd.znet=..." if you use a native > network device. > > > The full syntax of the ip= parameter (not sure if RHEL supports all of > this) is described for the dracut upstream project in > https://www.kernel.org/pub/linux/utils/boot/dracut/dracut.html#_network. > > The anaconda upstream documentation has its own (subset?) copy under > https://github.com/rhinstaller/anaconda/blob/master/docs/ > boot-options.rst#network-options or https://rhinstaller.github.io/ > anaconda/boot-options.html#network-options, but since RHEL7 uses dracut > even for the installer initrd it's the same mechanism as in my previous > paragraph. > > > -- > Mit freundlichen Grüßen / Kind regards > Steffen Maier > > Linux on z Systems Development > > IBM Deutschland Research & Development GmbH > Vorsitzende des Aufsichtsrats: Martina Koederitz > Geschaeftsfuehrung: Dirk Wittkopp > Sitz der Gesellschaft: Boeblingen > Registergericht: Amtsgericht Stuttgart, HRB 243294 > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > -- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Installing RHEL 7
Hi Mike, On 11/17/2016 01:15 PM, Michael MacIsaac wrote: Is there any documentation on how to install RHEL 7 using DHCP? The current "Cookbook" only shows how to static IP (who wrote that thing? :)) The Red Hat documentation on line alludes to DHCP, but does not have a specific example - perhaps I'm missing it. The RHEL installation guide describes (a subset of) the "ip=" (pseudo) kernel parameter syntax: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Installation_Guide/chap-installer-booting-ipl-s390.html#sect-customizing-generic-prm-s390 refers to: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Installation_Guide/chap-anaconda-boot-options.html#list-boot-options-network (It also occurs in the x- and p-specific network install chapter of which some parts are common code and also apply to z: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Installation_Guide/chap-installation-server-setup.html) I think omitting the "ip=..." entirely also defaults to dhcp. A kickstart file itself also has some dhcp syntax (network --bootproto=dhcp): https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Installation_Guide/sect-kickstart-syntax.html#sect-kickstart-commands On z Systems you likely still need "rd.znet=..." if you use a native network device. The full syntax of the ip= parameter (not sure if RHEL supports all of this) is described for the dracut upstream project in https://www.kernel.org/pub/linux/utils/boot/dracut/dracut.html#_network. The anaconda upstream documentation has its own (subset?) copy under https://github.com/rhinstaller/anaconda/blob/master/docs/boot-options.rst#network-options or https://rhinstaller.github.io/anaconda/boot-options.html#network-options, but since RHEL7 uses dracut even for the installer initrd it's the same mechanism as in my previous paragraph. -- Mit freundlichen Grüßen / Kind regards Steffen Maier Linux on z Systems Development IBM Deutschland Research & Development GmbH Vorsitzende des Aufsichtsrats: Martina Koederitz Geschaeftsfuehrung: Dirk Wittkopp Sitz der Gesellschaft: Boeblingen Registergericht: Amtsgericht Stuttgart, HRB 243294 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Installing RHEL 7
Thanks, Dan - that did the trick. Ray On 11/6/2014 10:06, Dan Horák wrote: On Thu, 6 Nov 2014 09:46:47 -0500 Ray Mansell wrote: I'm having pretty much the same problem described by Mike, except that my generic.prm looks like this: ro ramdisk_size=4 cio_ignore=all,!condev inst.repo=ftp://9.2.98.16/e/redhat/rhel7 Looking at the FTP server, there is no sign that any attempt was made to access it. Any ideas? I must be doing something wrong, but it's eluding me so far. There is no interactive s390 specific part in the installation where you could enter network and disk info as opposed to RHEL <= 6. They all need to be specified in advance in the generic.prm or in the old style CMSCONF file. Please read https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Installation_Guide/chap-installer-booting-ipl-s390.html#sect-customizing-generic-prm-s390 Dan -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Installing RHEL 7
On Thu, 6 Nov 2014 09:46:47 -0500 Ray Mansell wrote: > I'm having pretty much the same problem described by Mike, except > that my generic.prm looks like this: > > ro ramdisk_size=4 cio_ignore=all,!condev > inst.repo=ftp://9.2.98.16/e/redhat/rhel7 > > Looking at the FTP server, there is no sign that any attempt was made > to access it. > > Any ideas? I must be doing something wrong, but it's eluding me so > far. There is no interactive s390 specific part in the installation where you could enter network and disk info as opposed to RHEL <= 6. They all need to be specified in advance in the generic.prm or in the old style CMSCONF file. Please read https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Installation_Guide/chap-installer-booting-ipl-s390.html#sect-customizing-generic-prm-s390 Dan -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Installing RHEL 7
I'm having pretty much the same problem described by Mike, except that my generic.prm looks like this: ro ramdisk_size=4 cio_ignore=all,!condev inst.repo=ftp://9.2.98.16/e/redhat/rhel7 Looking at the FTP server, there is no sign that any attempt was made to access it. Any ideas? I must be doing something wrong, but it's eluding me so far. Ray On 9/16/2014 15:41, Michael MacIsaac wrote: Hello list, 1) Has anyone been able to install RHEL 7 on z? 2) Is there any documentation specific to System z? I was able to download the two ISO images from rhn.redhat.com. I did not see any documentation on the Web nor on the mounted ISO (perhaps I'm missing it). I tried the following steps, but got errors similar to what others have reported in this forum: Thanks. -Mike M. -) Mount ISO image on an NFS server and export it -) Copy kernel and RAMdisk from images/ directory to CMS disk -) Update parmfile in the images/ directory with new first line: # cat generic.prm ro ramdisk_size=4 cio_ignore=all,!condev -) Log on to Linux virtual machine -) DEF STOR 1G -) IPL CMS -) run the RHEL7 EXEC - system starts booting: ... 7.280120 systemd-udevd: renamed network interface eth0 to enccw0.0.0600 ... *really, systemd, I will miss the old sysVinit ... (sniff, sniff :))really, enccw0.0.0600 is better than eth0? (not a good start systemd :))* ... OKMounted Configuration File System. OKReached target System Initialization. OKStarted Show Plymouth Boot Screen. OKReached target Paths. OKReached target Basic System. ... *install stops here for a couple of minutes, then:* ... dracut-initqueueÝ706¨: Warning: Could not boot. OKStarted Show Plymouth Boot Screen. OKReached target Paths. OKReached target Basic System. dracut-initqueue: Warning: Could not boot. dracut-initqueue: Warning: /dev/root does not exist ... generating /run/initramfs/rdsosreport.txt -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Installing RHEL 7
Yes, about 2-3 months ago. Problems with !condev and also number of disks and custom partioining. When we tried with kickstart file we could however set our own disk setup without problem. There is z specific info included in the Install manual. /Tore -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Michael MacIsaac Sent: den 16 september 2014 9:42 To: LINUX-390@VM.MARIST.EDU Subject: Installing RHEL 7 Hello list, 1) Has anyone been able to install RHEL 7 on z? 2) Is there any documentation specific to System z? I was able to download the two ISO images from rhn.redhat.com. I did not see any documentation on the Web nor on the mounted ISO (perhaps I'm missing it). I tried the following steps, but got errors similar to what others have reported in this forum: Thanks. -Mike M. -) Mount ISO image on an NFS server and export it -) Copy kernel and RAMdisk from images/ directory to CMS disk -) Update parmfile in the images/ directory with new first line: # cat generic.prm ro ramdisk_size=4 cio_ignore=all,!condev -) Log on to Linux virtual machine -) DEF STOR 1G -) IPL CMS -) run the RHEL7 EXEC - system starts booting: ... 7.280120 systemd-udevd: renamed network interface eth0 to enccw0.0.0600 ... *really, systemd, I will miss the old sysVinit ... (sniff, sniff :))really, enccw0.0.0600 is better than eth0? (not a good start systemd :))* ... OKMounted Configuration File System. OKReached target System Initialization. OKStarted Show Plymouth Boot Screen. OKReached target Paths. OKReached target Basic System. ... *install stops here for a couple of minutes, then:* ... dracut-initqueueÝ706¨: Warning: Could not boot. OKStarted Show Plymouth Boot Screen. OKReached target Paths. OKReached target Basic System. dracut-initqueue: Warning: Could not boot. dracut-initqueue: Warning: /dev/root does not exist ... generating /run/initramfs/rdsosreport.txt -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Installing RHEL 7
Neale, Yes, that's the magic charm. Thanks! -Mike On Tue, Sep 16, 2014 at 4:49 PM, Neale Ferguson wrote: > You need to point it at the install.img file. Here's what I used (it needs > to spill at 80 characters): > > root=live:nfs:// > repo.dev.sinenomine.net/export/repository/s390x/linux/RHEL/7/7.0/iso/images/install.img > ramdisk_size=131072 cio_ignore=all,!condev > CMSDASD=191 CMSCONFFILE=rhel.conf > > On Sep 16, 2014, at 4:39 PM, Michael MacIsaac wrote: > > > Neale, Felipe, > > > > Thanks for the quick replies. I got to the documentation on the Web and > > will bookmark it. > > > > In section 14.1 "Customizing generic.prm", I don't see anything about > > live:nfs://, nor root= (maybe I'm missing it). > > > > In section 14.2 "Considerations for Hard Drive Installation on IBM System > > z" I read: > > "If you wish to boot the installation program from a hard drive, you can > > optionally install the zipl boot loader on the same (or a different) > > disk..." He he - perhaps this was copied from the Intel book? (sorry, > > couldn't resist :)) > > > > So I followed Neale's hint and tried adding a line to the parm file: > > > > root=live:nfs://myserver/srv/nfs/rhel7/dvd1 > > > > where the dvd1 directory is mounted loopback. > > > > Then after the "Reached target Basic System." message it only waits a few > > seconds, so it seems to be communicating with the NFS server. But now it > > fails with: > > ... > > 33.492098¨ FS-Cache: Loaded > > 33.500256¨ FS-Cache: Netfs 'nfs' registered for caching > > 33.504518¨ Key type dns_resolver registered > > 33.511157¨ NFS: Registering the id_resolver key type > > 33.511167¨ Key type id_resolver registered > > 33.511170¨ Key type id_legacy registered > > 33.542071¨ dracut: FATAL: failed to download live image: error 1 > > 33.542091¨ dracut: Refusing to continue > > ... > > > > I tried again with the line whereby the install program does the NFS > mount: > > > > root=live:nfs://myserver/srv/nfs/rhel7/rhel-server-7.0-s390x-dvd.iso > > > > But got the same error. Both directories /srv/nfs/rhel7/ and > > /srv/nfs/rhel7/dvd1 are NFS exported on 'myserver'. > > > > Any help will be appreciated. > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > -- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Installing RHEL 7
Hello Stuart, The architecture level for RHEL7 is z196/z114 and above - no z10 support from this point forward (z10 only with RHEL5 and RHEL6) Kind Regards, Filipe On Sep 16, 2014, at 1:52 PM, Stewart, Lee wrote: > I thought I saw somewhere that RHEL 7 needed an EC12 levelset... I can't > find it offhand right now... Anyone else... > > Lee Stewart ● VM System Support ● Visa ● Phone: 6(750)4601 - +1-303-389-4601 > ● lstew...@visa.com > > -Original Message- > From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Michael > MacIsaac > Sent: Tuesday, September 16, 2014 1:42 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Installing RHEL 7 > > Hello list, > > 1) Has anyone been able to install RHEL 7 on z? > 2) Is there any documentation specific to System z? > > I was able to download the two ISO images from rhn.redhat.com. I did not see > any documentation on the Web nor on the mounted ISO (perhaps I'm missing it). > > I tried the following steps, but got errors similar to what others have > reported in this forum: > > Thanks. > >-Mike M. > > -) Mount ISO image on an NFS server and export it > -) Copy kernel and RAMdisk from images/ directory to CMS disk > -) Update parmfile in the images/ directory with new first line: > # cat generic.prm > ro ramdisk_size=4 cio_ignore=all,!condev > -) Log on to Linux virtual machine > -) DEF STOR 1G > -) IPL CMS > -) run the RHEL7 EXEC - system starts booting: > ... > 7.280120 systemd-udevd: renamed network interface eth0 to enccw0.0.0600 ... > > *really, systemd, I will miss the old sysVinit ... (sniff, sniff :))really, > enccw0.0.0600 is better than eth0? (not a good start systemd :))* ... > OKMounted Configuration File System. > OKReached target System Initialization. > OKStarted Show Plymouth Boot Screen. > OKReached target Paths. > OKReached target Basic System. > ... > *install stops here for a couple of minutes, then:* ... > dracut-initqueueÝ706¨: Warning: Could not boot. > OKStarted Show Plymouth Boot Screen. > OKReached target Paths. > OKReached target Basic System. > dracut-initqueue: Warning: Could not boot. > dracut-initqueue: Warning: /dev/root does not exist ... > generating /run/initramfs/rdsosreport.txt > > -- > For LINUX-390 subscribe / signoff / archive access instructions, send email > to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > -- > For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ signature.asc Description: Message signed with OpenPGP using GPGMail
Re: Installing RHEL 7
Mike,
Use this as an example:
> ro ramdisk_size=4 cio_ignore=all,!condev
> ip=10.16.105.69::10.16.111.254:21:train6.redhat.com:enccw0.0.0600:none
> rd.znet=qeth,0.0.0600,0.0.0601,0.0.0602,layer2=0,portname=FOOBAR
> nameserver=10.16.46.224 nameserver=10.16.36.29
> rd.dasd=0.0.0100 rd.dasd=0.0.0101
> inst.repo=http://10.13.145.5/rhel7_s390/ or
> inst.repo=nfs:[options:]server:/path
> vnc vncpassword=redhat
Where:
The documentation explains the semantics of all the bits and pieces:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Installation_Guide/chap-anaconda-boot-options.html#list-boot-options-network
The upstream docs might explain the double colon, which is just an
optional "peer" option that is not needed in our case:
https://www.kernel.org/pub/linux/utils/boot/dracut/dracut.html#_network
"ip=:[]
:{none|off|dhcp|on|any|dhcp6|auto6|ibft}:[:[][:]]
"
or
"ip=:[]
:{none|off|dhcp|on|any|dhcp6|auto6|ibft}[:[][:]] "
" is optional and is the address of the remote endpoint for
pointopoint interfaces"
If one does not follow the ip= syntax to the very last detail, it just
fails (or falls back to dhcp) without helpful user message [see more
recent pre-validation comments of bug 1070104].
or
Try Neale suggestion - it also worked :-)
Kind Regards,
Filipe
On Sep 16, 2014, at 1:39 PM, Michael MacIsaac wrote:
> Neale, Felipe,
>
> Thanks for the quick replies. I got to the documentation on the Web and
> will bookmark it.
>
> In section 14.1 "Customizing generic.prm", I don't see anything about
> live:nfs://, nor root= (maybe I'm missing it).
>
> In section 14.2 "Considerations for Hard Drive Installation on IBM System
> z" I read:
> "If you wish to boot the installation program from a hard drive, you can
> optionally install the zipl boot loader on the same (or a different)
> disk..." He he - perhaps this was copied from the Intel book? (sorry,
> couldn't resist :))
>
> So I followed Neale's hint and tried adding a line to the parm file:
>
> root=live:nfs://myserver/srv/nfs/rhel7/dvd1
>
> where the dvd1 directory is mounted loopback.
>
> Then after the "Reached target Basic System." message it only waits a few
> seconds, so it seems to be communicating with the NFS server. But now it
> fails with:
> ...
> 33.492098¨ FS-Cache: Loaded
> 33.500256¨ FS-Cache: Netfs 'nfs' registered for caching
> 33.504518¨ Key type dns_resolver registered
> 33.511157¨ NFS: Registering the id_resolver key type
> 33.511167¨ Key type id_resolver registered
> 33.511170¨ Key type id_legacy registered
> 33.542071¨ dracut: FATAL: failed to download live image: error 1
> 33.542091¨ dracut: Refusing to continue
> ...
>
> I tried again with the line whereby the install program does the NFS mount:
>
> root=live:nfs://myserver/srv/nfs/rhel7/rhel-server-7.0-s390x-dvd.iso
>
> But got the same error. Both directories /srv/nfs/rhel7/ and
> /srv/nfs/rhel7/dvd1 are NFS exported on 'myserver'.
>
> Any help will be appreciated.
>
>-Mike M
>
> On Tue, Sep 16, 2014 at 3:46 PM, Filipe Miranda wrote:
>
>> Hello Mike,
>>
>> Here is the documentation for RHEL on z:
>>
>> https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Installation_Guide/part-installation-system-z.html
>>
>> Let me know if you have any questions,
>>
>>
>> Kind Regards,
>>
>> Filipe Miranda
>>
>>
>> On Sep 16, 2014, at 12:41 PM, Michael MacIsaac
>> wrote:
>>
>>> Hello list,
>>>
>>> 1) Has anyone been able to install RHEL 7 on z?
>>> 2) Is there any documentation specific to System z?
>>>
>>> I was able to download the two ISO images from rhn.redhat.com. I did
>> not
>>> see any documentation on the Web nor on the mounted ISO (perhaps I'm
>>> missing it).
>>>
>>> I tried the following steps, but got errors similar to what others have
>>> reported in this forum:
>>>
>>> Thanks.
>>>
>>> -Mike M.
>>>
>>> -) Mount ISO image on an NFS server and export it
>>> -) Copy kernel and RAMdisk from images/ directory to CMS disk
>>> -) Update parmfile in the images/ directory with new first line:
>>> # cat generic.prm
>>> ro ramdisk_size=4 cio_ignore=all,!condev
>>> -) Log on to Linux virtual machine
>>> -) DEF STOR 1G
>>> -) IPL CMS
>>> -) run the RHEL7 EXEC - system starts booting:
>>> ...
>>> 7.280120 systemd-udevd: renamed network interface eth0 to enccw0.0.0600
>>> ...
>>>
>>> *really, systemd, I will miss the old sysVinit ... (sniff, sniff
>> :))really,
>>> enccw0.0.0600 is better than eth0? (not a good start systemd :))*
>>> ...
>>> OKMounted Configuration File System.
>>> OKReached target System Initialization.
>>> OKStarted Show Plymouth Boot Screen.
>>> OKReached target Paths.
>>> OKReached target Basic System.
>>> ...
>>> *install stops here for a couple of minutes, then:*
>>> ...
>>> dracut-initqueueÝ706¨: Warning: Could not boot.
>>> OKStarted Show Plymouth Boot Screen.
>>> OKReached target Paths.
>>> OKReached target Basic S
Re: Installing RHEL 7
No, z196 or better. On Sep 16, 2014, at 4:52 PM, Stewart, Lee wrote: > I thought I saw somewhere that RHEL 7 needed an EC12 levelset... I can't > find it offhand right now... Anyone else... -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Installing RHEL 7
I thought I saw somewhere that RHEL 7 needed an EC12 levelset... I can't find it offhand right now... Anyone else... Lee Stewart ● VM System Support ● Visa ● Phone: 6(750)4601 - +1-303-389-4601 ● lstew...@visa.com -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Michael MacIsaac Sent: Tuesday, September 16, 2014 1:42 PM To: LINUX-390@VM.MARIST.EDU Subject: Installing RHEL 7 Hello list, 1) Has anyone been able to install RHEL 7 on z? 2) Is there any documentation specific to System z? I was able to download the two ISO images from rhn.redhat.com. I did not see any documentation on the Web nor on the mounted ISO (perhaps I'm missing it). I tried the following steps, but got errors similar to what others have reported in this forum: Thanks. -Mike M. -) Mount ISO image on an NFS server and export it -) Copy kernel and RAMdisk from images/ directory to CMS disk -) Update parmfile in the images/ directory with new first line: # cat generic.prm ro ramdisk_size=4 cio_ignore=all,!condev -) Log on to Linux virtual machine -) DEF STOR 1G -) IPL CMS -) run the RHEL7 EXEC - system starts booting: ... 7.280120 systemd-udevd: renamed network interface eth0 to enccw0.0.0600 ... *really, systemd, I will miss the old sysVinit ... (sniff, sniff :))really, enccw0.0.0600 is better than eth0? (not a good start systemd :))* ... OKMounted Configuration File System. OKReached target System Initialization. OKStarted Show Plymouth Boot Screen. OKReached target Paths. OKReached target Basic System. ... *install stops here for a couple of minutes, then:* ... dracut-initqueueÝ706¨: Warning: Could not boot. OKStarted Show Plymouth Boot Screen. OKReached target Paths. OKReached target Basic System. dracut-initqueue: Warning: Could not boot. dracut-initqueue: Warning: /dev/root does not exist ... generating /run/initramfs/rdsosreport.txt -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Installing RHEL 7
You need to point it at the install.img file. Here's what I used (it needs to spill at 80 characters): root=live:nfs://repo.dev.sinenomine.net/export/repository/s390x/linux/RHEL/7/7.0/iso/images/install.img ramdisk_size=131072 cio_ignore=all,!condev CMSDASD=191 CMSCONFFILE=rhel.conf On Sep 16, 2014, at 4:39 PM, Michael MacIsaac wrote: > Neale, Felipe, > > Thanks for the quick replies. I got to the documentation on the Web and > will bookmark it. > > In section 14.1 "Customizing generic.prm", I don't see anything about > live:nfs://, nor root= (maybe I'm missing it). > > In section 14.2 "Considerations for Hard Drive Installation on IBM System > z" I read: > "If you wish to boot the installation program from a hard drive, you can > optionally install the zipl boot loader on the same (or a different) > disk..." He he - perhaps this was copied from the Intel book? (sorry, > couldn't resist :)) > > So I followed Neale's hint and tried adding a line to the parm file: > > root=live:nfs://myserver/srv/nfs/rhel7/dvd1 > > where the dvd1 directory is mounted loopback. > > Then after the "Reached target Basic System." message it only waits a few > seconds, so it seems to be communicating with the NFS server. But now it > fails with: > ... > 33.492098¨ FS-Cache: Loaded > 33.500256¨ FS-Cache: Netfs 'nfs' registered for caching > 33.504518¨ Key type dns_resolver registered > 33.511157¨ NFS: Registering the id_resolver key type > 33.511167¨ Key type id_resolver registered > 33.511170¨ Key type id_legacy registered > 33.542071¨ dracut: FATAL: failed to download live image: error 1 > 33.542091¨ dracut: Refusing to continue > ... > > I tried again with the line whereby the install program does the NFS mount: > > root=live:nfs://myserver/srv/nfs/rhel7/rhel-server-7.0-s390x-dvd.iso > > But got the same error. Both directories /srv/nfs/rhel7/ and > /srv/nfs/rhel7/dvd1 are NFS exported on 'myserver'. > > Any help will be appreciated. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Installing RHEL 7
Neale, Felipe, Thanks for the quick replies. I got to the documentation on the Web and will bookmark it. In section 14.1 "Customizing generic.prm", I don't see anything about live:nfs://, nor root= (maybe I'm missing it). In section 14.2 "Considerations for Hard Drive Installation on IBM System z" I read: "If you wish to boot the installation program from a hard drive, you can optionally install the zipl boot loader on the same (or a different) disk..." He he - perhaps this was copied from the Intel book? (sorry, couldn't resist :)) So I followed Neale's hint and tried adding a line to the parm file: root=live:nfs://myserver/srv/nfs/rhel7/dvd1 where the dvd1 directory is mounted loopback. Then after the "Reached target Basic System." message it only waits a few seconds, so it seems to be communicating with the NFS server. But now it fails with: ... 33.492098¨ FS-Cache: Loaded 33.500256¨ FS-Cache: Netfs 'nfs' registered for caching 33.504518¨ Key type dns_resolver registered 33.511157¨ NFS: Registering the id_resolver key type 33.511167¨ Key type id_resolver registered 33.511170¨ Key type id_legacy registered 33.542071¨ dracut: FATAL: failed to download live image: error 1 33.542091¨ dracut: Refusing to continue ... I tried again with the line whereby the install program does the NFS mount: root=live:nfs://myserver/srv/nfs/rhel7/rhel-server-7.0-s390x-dvd.iso But got the same error. Both directories /srv/nfs/rhel7/ and /srv/nfs/rhel7/dvd1 are NFS exported on 'myserver'. Any help will be appreciated. -Mike M On Tue, Sep 16, 2014 at 3:46 PM, Filipe Miranda wrote: > Hello Mike, > > Here is the documentation for RHEL on z: > > https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Installation_Guide/part-installation-system-z.html > > Let me know if you have any questions, > > > Kind Regards, > > Filipe Miranda > > > On Sep 16, 2014, at 12:41 PM, Michael MacIsaac > wrote: > > > Hello list, > > > > 1) Has anyone been able to install RHEL 7 on z? > > 2) Is there any documentation specific to System z? > > > > I was able to download the two ISO images from rhn.redhat.com. I did > not > > see any documentation on the Web nor on the mounted ISO (perhaps I'm > > missing it). > > > > I tried the following steps, but got errors similar to what others have > > reported in this forum: > > > > Thanks. > > > >-Mike M. > > > > -) Mount ISO image on an NFS server and export it > > -) Copy kernel and RAMdisk from images/ directory to CMS disk > > -) Update parmfile in the images/ directory with new first line: > > # cat generic.prm > > ro ramdisk_size=4 cio_ignore=all,!condev > > -) Log on to Linux virtual machine > > -) DEF STOR 1G > > -) IPL CMS > > -) run the RHEL7 EXEC - system starts booting: > > ... > > 7.280120 systemd-udevd: renamed network interface eth0 to enccw0.0.0600 > > ... > > > > *really, systemd, I will miss the old sysVinit ... (sniff, sniff > :))really, > > enccw0.0.0600 is better than eth0? (not a good start systemd :))* > > ... > > OKMounted Configuration File System. > > OKReached target System Initialization. > > OKStarted Show Plymouth Boot Screen. > > OKReached target Paths. > > OKReached target Basic System. > > ... > > *install stops here for a couple of minutes, then:* > > ... > > dracut-initqueueÝ706¨: Warning: Could not boot. > > OKStarted Show Plymouth Boot Screen. > > OKReached target Paths. > > OKReached target Basic System. > > dracut-initqueue: Warning: Could not boot. > > dracut-initqueue: Warning: /dev/root does not exist > > ... > > generating /run/initramfs/rdsosreport.txt > > > > -- > > For LINUX-390 subscribe / signoff / archive access instructions, > > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 > or visit > > http://www.marist.edu/htbin/wlvindex?LINUX-390 > > -- > > For more information on Linux on System z, visit > > http://wiki.linuxvm.org/ > > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > -- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Installing RHEL 7
Hello Mike, Here is the documentation for RHEL on z: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Installation_Guide/part-installation-system-z.html Let me know if you have any questions, Kind Regards, Filipe Miranda On Sep 16, 2014, at 12:41 PM, Michael MacIsaac wrote: > Hello list, > > 1) Has anyone been able to install RHEL 7 on z? > 2) Is there any documentation specific to System z? > > I was able to download the two ISO images from rhn.redhat.com. I did not > see any documentation on the Web nor on the mounted ISO (perhaps I'm > missing it). > > I tried the following steps, but got errors similar to what others have > reported in this forum: > > Thanks. > >-Mike M. > > -) Mount ISO image on an NFS server and export it > -) Copy kernel and RAMdisk from images/ directory to CMS disk > -) Update parmfile in the images/ directory with new first line: > # cat generic.prm > ro ramdisk_size=4 cio_ignore=all,!condev > -) Log on to Linux virtual machine > -) DEF STOR 1G > -) IPL CMS > -) run the RHEL7 EXEC - system starts booting: > ... > 7.280120 systemd-udevd: renamed network interface eth0 to enccw0.0.0600 > ... > > *really, systemd, I will miss the old sysVinit ... (sniff, sniff :))really, > enccw0.0.0600 is better than eth0? (not a good start systemd :))* > ... > OKMounted Configuration File System. > OKReached target System Initialization. > OKStarted Show Plymouth Boot Screen. > OKReached target Paths. > OKReached target Basic System. > ... > *install stops here for a couple of minutes, then:* > ... > dracut-initqueueÝ706¨: Warning: Could not boot. > OKStarted Show Plymouth Boot Screen. > OKReached target Paths. > OKReached target Basic System. > dracut-initqueue: Warning: Could not boot. > dracut-initqueue: Warning: /dev/root does not exist > ... > generating /run/initramfs/rdsosreport.txt > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > -- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ signature.asc Description: Message signed with OpenPGP using GPGMail
Re: Installing RHEL 7
Successfully installed it last week. Key for me was root=live:nfs://... The live was the important bit. Original message From: Michael MacIsaac Date:2014/09/16 15:42 (GMT-05:00) To: LINUX-390@VM.MARIST.EDU Cc: Subject: [LINUX-390] Installing RHEL 7 Hello list, 1) Has anyone been able to install RHEL 7 on z? 2) Is there any documentation specific to System z? I was able to download the two ISO images from rhn.redhat.com. I did not see any documentation on the Web nor on the mounted ISO (perhaps I'm missing it). I tried the following steps, but got errors similar to what others have reported in this forum: Thanks. -Mike M. -) Mount ISO image on an NFS server and export it -) Copy kernel and RAMdisk from images/ directory to CMS disk -) Update parmfile in the images/ directory with new first line: # cat generic.prm ro ramdisk_size=4 cio_ignore=all,!condev -) Log on to Linux virtual machine -) DEF STOR 1G -) IPL CMS -) run the RHEL7 EXEC - system starts booting: ... 7.280120 systemd-udevd: renamed network interface eth0 to enccw0.0.0600 ... *really, systemd, I will miss the old sysVinit ... (sniff, sniff :))really, enccw0.0.0600 is better than eth0? (not a good start systemd :))* ... OKMounted Configuration File System. OKReached target System Initialization. OKStarted Show Plymouth Boot Screen. OKReached target Paths. OKReached target Basic System. ... *install stops here for a couple of minutes, then:* ... dracut-initqueueÝ706¨: Warning: Could not boot. OKStarted Show Plymouth Boot Screen. OKReached target Paths. OKReached target Basic System. dracut-initqueue: Warning: Could not boot. dracut-initqueue: Warning: /dev/root does not exist ... generating /run/initramfs/rdsosreport.txt -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
