Rick, Could you send us the complete parm file ? Are you installing on ECKD or FCP? Were the disks used for this Linux install in use before or are they brand new? Maybe something old from a previous use of the disk is causing some weird behave by the installer, have you tried to low format the disks from a terminal and then tried the installation again? I haven' t seem any issues like that on RHEL 7.x..... Yet :-)
Kind Regards, Filipe Miranda > On Jul 21, 2015, at 10:49 AM, Beard, Rick (Atos) <rick.be...@xerox.com> wrote: > > Well, I was already at 1GB and I tried 2GB, but still have the same issue. I > have an open issue with Red Hat, so will see what they come up with. > > Rick > > -----Original Message----- > From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Filipe > Miranda > Sent: Tuesday, July 21, 2015 11:16 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: Linux 7.1 on z/VM 6.3 > > Rick, > > Please make sure that the VM have at least 1GB of RAM. (I had similar > problems when trying to install using less than one GB of RAM) > > > Kind Regards, > > Filipe Miranda >> On Jul 21, 2015, at 7:35 AM, Beard, Rick (Atos) <rick.be...@xerox.com> wrote: >> >> OK, I created a new PARM file and did away with the call to a configuration >> file and was able to get VNC working to get the GUI into the install >> screens, but now the problem is when I click on the option to setup my >> partitions manually, I get a box that comes up and says my connection was >> gracefully closed and everything dies. Has anyone ran into this issue? >> For grins I reloaded everything and left the partitioning set to auto and it >> successfully installed, but I need to be able to setup my own partitioning, >> so this is not an option for me. >> >> Rick >> >> -----Original Message----- >> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of >> Filipe Miranda >> Sent: Monday, July 20, 2015 10:44 AM >> To: LINUX-390@VM.MARIST.EDU >> Subject: Re: Linux 7.1 on z/VM 6.3 >> >> Hello, >> >> RHEL7.x can use the same “installation style” (parm file and conf file) as >> before with a few minor changes (keep in mind that this will be deprecated >> in the future), or the new “installation layout” (just the parm file). >> The following slide deck shows examples of how the new parm file >> should look like: >> http://people.redhat.com/fmiranda/systemz/slide_decks/Special%20Events >> /IBM%20T3%20Bobligen%20Germany%202015%20v2.pdf >> <http://people.redhat.com/fmiranda/systemz/slide_decks/Special%20Event >> s/IBM%20T3%20Bobligen%20Germany%202015%20v2.pdf> >> >> Kind Regards, >> >> Filipe Miranda >> fmira...@redhat.com >> >>> On Jul 17, 2015, at 7:17 AM, Grzegorz Powiedziuk <gpowiedz...@gmail.com> >>> wrote: >>> >>> 2015-07-17 9:55 GMT-04:00 Beard, Rick (Atos) <rick.be...@xerox.com>: >>> >>>> Gregory, >>>> >>>> Looks like your using the kick start method to install. I just load >>>> the install into memory then SSH into the new image and issue >>>> install at the logon which then allows me to pick the language and >>>> then point to the NFS where the packages exists. The next step is >>>> does is have me connect to the new image using VNC and I do the >>>> install configurations via a gui then reboot when the install is >>>> done. For years I have been using the following PARM file. >>>> >>>> root=/dev/ram0 ro ip=off ramdisk_size=40000 >>>> CMSDASD=191 CMSCONFFILE=xxxxxxxxxx.CONF-RH7 >>> >>> That is correct. I think you should be able to modify my parmfile for >>> you needs. So in your case, the following parmfile should work: >>> >>> ro ramdisk_size=40000 cio_ignore=all,!condev >>> CMSDASD=191 >>> CMSCONFFILE=xxxxxxx.conf >>> inst.repo=http://xxx.xxx.xxx.xxx (I guess you can skip it if you >>> specify it cond file ) vnc vncpassword=redhat >>> >>> >>> >>> >>>> And here is the xxxxxxxxxxxx.CONF-RH7 file: >>>> >>>> DASD=200,204 >>>> HOSTNAME=xxxxxxxxxxxx.xxxx.com >>>> NETTYPE=qeth >>>> IPADDR=xxx.xxx.xxx.xxx >>>> SUBCHANNELS=0.0.0500,0.0.0501,0.0.0502 >>>> NETMASK=xxx.xxx.xxx.xxx >>>> SEARCHDNS=xxxx.com >>>> METHOD=nfs:xxxxxxxxx:/var/opt/rhel71 >>>> GATEWAY=xxx.xxx.xxx.xxx >>>> DNS=xxx.xxx.xxx.xxx >>>> MTU=1492 >>>> PORTNAME= >>>> PORTNO=0 >>>> LAYER2=0 >>> that looks fine. I have double quotes but that shouldn't matter >>> >>> Is there anything else you are getting before the error output you've >>> presented? Does it even load kernel and print kernel parameters? >>> >>> Gregory Powiedziuk >>> >>> --------------------------------------------------------------------- >>> - 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/
