Re: Linux 7.1 on z/VM 6.3

2015-07-24 Thread Grzegorz Powiedziuk 
have you sorted it out?
These kind of problems I was debugging by oppening another ssh session
(can't remember if it was just root with no password or another install or
something like that) and then, I could actually cd into directory where
anaconda dumps all the logs. You could tail these and see what it complains
about. In some cases, before it dies inside of the vnc session it may give
you a pop up window and if you click on 'details' you can see some good
info.

and btw
I used to have problems with dasd and edevs if they were not formatted with
ickdsf/cpfmtxa before.

Gregory Powiedziuk

2015-07-22 14:04 GMT-04:00 Filipe Miranda :

> Hi Rick,
>
> Could you please send me the RedHat Support Ticket number offline ?
> fmira...@redhat.com <mailto:fmira...@redhat.com>
> I want to track this ticket.
>
> Thank you,
>
> Kind Regards,
> Filipe Miranda
>
> > On Jul 22, 2015, at 10:56 AM, Beard, Rick (Atos) 
> wrote:
> >
> > Filipe,
> >
> > Same results using what you have below.  The only piece I added was the
> inst.vnc as it goes with the inst.vncpassword.  If you omit the inst.vnc
> the inst.vncpassword won't be used and when you ssh to the image and logon
> with install it will ask you if you want to use vnc or text mode and when
> you select vnc it will then ask for a password.  Coding both of these sets
> vnc up automatically.
> >
> > Rick
> >
> > -Original Message-
> > From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
> Filipe Miranda
> > Sent: Wednesday, July 22, 2015 12:29 PM
> > To: LINUX-390@VM.MARIST.EDU
> > Subject: Re: Linux 7.1 on z/VM 6.3
> >
> > Hello Rick,
> >
> > Everything seems to be in order on that PARM file.
> >
> > The only option I haven’t tried yet from this PARM is to force the
> resolution by using the  inst.resolution=1024x768 parameter, but I’m not
> sure if that maybe causing some weird behavior by the VNC client/server
> piece.
> > I know it sounds silly, but could you try with the following PARM file:
> >
> > ro ramdisk_size=4 cio_ignore=all,!condev
> ip=xxx.xxx.xxx.xxx::xxx.xxx.xxx.xxx:22:lnxmnt71.marriott.com:
> enccw0.0.0500:none
> > rd.znet=qeth,0.0.0500,0.0.0501,0.0.0502,layer2=0
> > nameserver=xxx.xxx.xxx.xxx
> > rd.dasd=0.0.0200 rd.dasd=0.0.0300 rd.dasd=0.0.0301 inst.vnc
> inst.vncpassword=
> > inst.repo=nfs:xxx.xxx.xxx.xxx:/var/opt/rhel71
> >
> > if that fails again, does the installer gives you any hint of what might
> have happened? Are you able to get a shell access ?
> >
> >
> > Thank you,
> >
> > Kind Regards,
> > Filipe Miranda
> >
> >
> >> On Jul 22, 2015, at 8:30 AM, Beard, Rick (Atos) 
> wrote:
> >>
> >> Filipe,
> >>
> >>
> >>
> >> I'm using ECKD DASD and it was formatted using CA's VMDIRECT software
> when it allocated it to the Linux image.
> >>
> >>
> >>
> >> Here is my PARM file.
> >>
> >>
> >>
> >> ro ramdisk_size=4 cio_ignore=all,!condev
> >>
> >> ip=xxx.xxx.xxx.xxx::xxx.xxx.xxx.xxx:22:lnxmnt71.marriott.com:enccw0.0.
> >> 0500:none
> >>
> >>
> >>
> >> rd.znet=qeth,0.0.0500,0.0.0501,0.0.0502,layer2=0
> >>
> >> nameserver=xxx.xxx.xxx.xxx
> >>
> >> rd.dasd=0.0.0200
> >>
> >> rd.dasd=0.0.0300
> >>
> >> rd.dasd=0.0.0301
> >>
> >> inst.resolution=1024x768
> >>
> >> inst.vnc
> >>
> >> inst.vncpassword=
> >>
> >> inst.repo=nfs:xxx.xxx.xxx.xxx:/var/opt/rhel71
> >>
> >>
> >>
> >>
> >>
> >> -Original Message-
> >> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
> >> Filipe Miranda
> >> Sent: Tuesday, July 21, 2015 1:59 PM
> >> To: LINUX-390@VM.MARIST.EDU
> >> Subject: Re: Linux 7.1 on z/VM 6.3
> >>
> >>
> >>
> >> 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

Re: Linux 7.1 on z/VM 6.3 - standard files

2015-07-22 Thread Filipe Miranda 
Hi Raymond,

INITRD.IMG, KERNEL.IMG, GENERIC.PRM and REDHAT.EXEC are the files required to 
install RHEL5, RHEL6 and RHEL7.

With RHEL5 and RHEL6 - optionally (but recommended) a CONF file was added to 
facilitate the installation process as described in this IBM Redbook: 
https://books.google.com/books?id=GHzJAgAAQBAJ&pg=PA151&source=gbs_toc_r&cad=4#v=onepage&q&f=false
 
<https://books.google.com/books?id=GHzJAgAAQBAJ&pg=PA151&source=gbs_toc_r&cad=4#v=onepage&q&f=false>

Now with RHEL7 you can still use the same method as RHEL6, I strongly recommend 
to use the new installation method described in this other IBM Redbook (because 
the old method will be deprecated): 
http://www.redbooks.ibm.com/redpieces/abstracts/sg248303.html?Open 
<http://www.redbooks.ibm.com/redpieces/abstracts/sg248303.html?Open>


Kind Regards,
Filipe Miranda


> On Jul 22, 2015, at 10:47 AM, Chu, Raymond  wrote:
> 
> Filipe,
> 
> I have the following standard files "INITRD.IMG, KERNEL.IMG,GENERIC.PRM and 
> REDHAT.EXEC when working Redhat 6. Can they still be used for Redhat 7?
> 
> Thanks,
> Ray
> 
> 
> 
> -Original Message-
> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Filipe 
> Miranda
> Sent: Wednesday, July 22, 2015 12:29 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: Linux 7.1 on z/VM 6.3
> 
> Email sent from outside of PSEG. Use caution before using links/attachments.
> 
> 
> Hello Rick,
> 
> Everything seems to be in order on that PARM file.
> 
> The only option I haven’t tried yet from this PARM is to force the resolution 
> by using the  inst.resolution=1024x768 parameter, but I’m not sure if that 
> maybe causing some weird behavior by the VNC client/server piece.
> I know it sounds silly, but could you try with the following PARM file:
> 
> ro ramdisk_size=4 cio_ignore=all,!condev 
> ip=xxx.xxx.xxx.xxx::xxx.xxx.xxx.xxx:22:lnxmnt71.marriott.com:enccw0.0.0500:none
> rd.znet=qeth,0.0.0500,0.0.0501,0.0.0502,layer2=0
> nameserver=xxx.xxx.xxx.xxx
> rd.dasd=0.0.0200 rd.dasd=0.0.0300 rd.dasd=0.0.0301 inst.vnc 
> inst.vncpassword=
> inst.repo=nfs:xxx.xxx.xxx.xxx:/var/opt/rhel71
> 
> if that fails again, does the installer gives you any hint of what might have 
> happened? Are you able to get a shell access ?
> 
> 
> Thank you,
> 
> Kind Regards,
> Filipe Miranda
> 
> 
>> On Jul 22, 2015, at 8:30 AM, Beard, Rick (Atos)  wrote:
>> 
>> Filipe,
>> 
>> 
>> 
>> I'm using ECKD DASD and it was formatted using CA's VMDIRECT software when 
>> it allocated it to the Linux image.
>> 
>> 
>> 
>> Here is my PARM file.
>> 
>> 
>> 
>> ro ramdisk_size=4 cio_ignore=all,!condev
>> 
>> ip=xxx.xxx.xxx.xxx::xxx.xxx.xxx.xxx:22:lnxmnt71.marriott.com:enccw0.0.
>> 0500:none
>> 
>> 
>> 
>> rd.znet=qeth,0.0.0500,0.0.0501,0.0.0502,layer2=0
>> 
>> nameserver=xxx.xxx.xxx.xxx
>> 
>> rd.dasd=0.0.0200
>> 
>> rd.dasd=0.0.0300
>> 
>> rd.dasd=0.0.0301
>> 
>> inst.resolution=1024x768
>> 
>> inst.vnc
>> 
>> inst.vncpassword=
>> 
>> inst.repo=nfs:xxx.xxx.xxx.xxx:/var/opt/rhel71
>> 
>> 
>> 
>> 
>> 
>> -Original Message-
>> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
>> Filipe Miranda
>> Sent: Tuesday, July 21, 2015 1:59 PM
>> To: LINUX-390@VM.MARIST.EDU
>> Subject: Re: Linux 7.1 on z/VM 6.3
>> 
>> 
>> 
>> 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) 
>>> mailto: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

Re: Linux 7.1 on z/VM 6.3

2015-07-22 Thread Filipe Miranda 
Hi Rick,

Could you please send me the RedHat Support Ticket number offline ? 
fmira...@redhat.com <mailto:fmira...@redhat.com>
I want to track this ticket.

Thank you,

Kind Regards,
Filipe Miranda

> On Jul 22, 2015, at 10:56 AM, Beard, Rick (Atos)  wrote:
> 
> Filipe,
> 
> Same results using what you have below.  The only piece I added was the 
> inst.vnc as it goes with the inst.vncpassword.  If you omit the inst.vnc the 
> inst.vncpassword won't be used and when you ssh to the image and logon with 
> install it will ask you if you want to use vnc or text mode and when you 
> select vnc it will then ask for a password.  Coding both of these sets vnc up 
> automatically.
> 
> Rick
> 
> -Original Message-
> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Filipe 
> Miranda
> Sent: Wednesday, July 22, 2015 12:29 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: Linux 7.1 on z/VM 6.3
> 
> Hello Rick,
> 
> Everything seems to be in order on that PARM file.
> 
> The only option I haven’t tried yet from this PARM is to force the resolution 
> by using the  inst.resolution=1024x768 parameter, but I’m not sure if that 
> maybe causing some weird behavior by the VNC client/server piece.
> I know it sounds silly, but could you try with the following PARM file:
> 
> ro ramdisk_size=4 cio_ignore=all,!condev 
> ip=xxx.xxx.xxx.xxx::xxx.xxx.xxx.xxx:22:lnxmnt71.marriott.com:enccw0.0.0500:none
> rd.znet=qeth,0.0.0500,0.0.0501,0.0.0502,layer2=0
> nameserver=xxx.xxx.xxx.xxx
> rd.dasd=0.0.0200 rd.dasd=0.0.0300 rd.dasd=0.0.0301 inst.vnc 
> inst.vncpassword=
> inst.repo=nfs:xxx.xxx.xxx.xxx:/var/opt/rhel71
> 
> if that fails again, does the installer gives you any hint of what might have 
> happened? Are you able to get a shell access ?
> 
> 
> Thank you,
> 
> Kind Regards,
> Filipe Miranda
> 
> 
>> On Jul 22, 2015, at 8:30 AM, Beard, Rick (Atos)  wrote:
>> 
>> Filipe,
>> 
>> 
>> 
>> I'm using ECKD DASD and it was formatted using CA's VMDIRECT software when 
>> it allocated it to the Linux image.
>> 
>> 
>> 
>> Here is my PARM file.
>> 
>> 
>> 
>> ro ramdisk_size=4 cio_ignore=all,!condev
>> 
>> ip=xxx.xxx.xxx.xxx::xxx.xxx.xxx.xxx:22:lnxmnt71.marriott.com:enccw0.0.
>> 0500:none
>> 
>> 
>> 
>> rd.znet=qeth,0.0.0500,0.0.0501,0.0.0502,layer2=0
>> 
>> nameserver=xxx.xxx.xxx.xxx
>> 
>> rd.dasd=0.0.0200
>> 
>> rd.dasd=0.0.0300
>> 
>> rd.dasd=0.0.0301
>> 
>> inst.resolution=1024x768
>> 
>> inst.vnc
>> 
>> inst.vncpassword=
>> 
>> inst.repo=nfs:xxx.xxx.xxx.xxx:/var/opt/rhel71
>> 
>> 
>> 
>> 
>> 
>> -Original Message-
>> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
>> Filipe Miranda
>> Sent: Tuesday, July 21, 2015 1:59 PM
>> To: LINUX-390@VM.MARIST.EDU
>> Subject: Re: Linux 7.1 on z/VM 6.3
>> 
>> 
>> 
>> 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) 
>>> mailto: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<mailto: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 try

Re: Linux 7.1 on z/VM 6.3

2015-07-22 Thread Beard, Rick (Atos) 
Filipe,

Same results using what you have below.  The only piece I added was the 
inst.vnc as it goes with the inst.vncpassword.  If you omit the inst.vnc the 
inst.vncpassword won't be used and when you ssh to the image and logon with 
install it will ask you if you want to use vnc or text mode and when you select 
vnc it will then ask for a password.  Coding both of these sets vnc up 
automatically.

Rick

-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Filipe 
Miranda
Sent: Wednesday, July 22, 2015 12:29 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Linux 7.1 on z/VM 6.3

Hello Rick,

Everything seems to be in order on that PARM file.

The only option I haven’t tried yet from this PARM is to force the resolution 
by using the  inst.resolution=1024x768 parameter, but I’m not sure if that 
maybe causing some weird behavior by the VNC client/server piece.
I know it sounds silly, but could you try with the following PARM file:

ro ramdisk_size=4 cio_ignore=all,!condev 
ip=xxx.xxx.xxx.xxx::xxx.xxx.xxx.xxx:22:lnxmnt71.marriott.com:enccw0.0.0500:none
rd.znet=qeth,0.0.0500,0.0.0501,0.0.0502,layer2=0
nameserver=xxx.xxx.xxx.xxx
rd.dasd=0.0.0200 rd.dasd=0.0.0300 rd.dasd=0.0.0301 inst.vnc 
inst.vncpassword=
inst.repo=nfs:xxx.xxx.xxx.xxx:/var/opt/rhel71

if that fails again, does the installer gives you any hint of what might have 
happened? Are you able to get a shell access ?


Thank you,

Kind Regards,
Filipe Miranda


> On Jul 22, 2015, at 8:30 AM, Beard, Rick (Atos)  wrote:
> 
> Filipe,
> 
> 
> 
> I'm using ECKD DASD and it was formatted using CA's VMDIRECT software when it 
> allocated it to the Linux image.
> 
> 
> 
> Here is my PARM file.
> 
> 
> 
> ro ramdisk_size=4 cio_ignore=all,!condev
> 
> ip=xxx.xxx.xxx.xxx::xxx.xxx.xxx.xxx:22:lnxmnt71.marriott.com:enccw0.0.
> 0500:none
> 
> 
> 
> rd.znet=qeth,0.0.0500,0.0.0501,0.0.0502,layer2=0
> 
> nameserver=xxx.xxx.xxx.xxx
> 
> rd.dasd=0.0.0200
> 
> rd.dasd=0.0.0300
> 
> rd.dasd=0.0.0301
> 
> inst.resolution=1024x768
> 
> inst.vnc
> 
> inst.vncpassword=
> 
> inst.repo=nfs:xxx.xxx.xxx.xxx:/var/opt/rhel71
> 
> 
> 
> 
> 
> -Original Message-
> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of 
> Filipe Miranda
> Sent: Tuesday, July 21, 2015 1:59 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: Linux 7.1 on z/VM 6.3
> 
> 
> 
> 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) 
>> mailto: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<mailto: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) 
>>> mailto: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

Re: Linux 7.1 on z/VM 6.3 - standard files

2015-07-22 Thread Chu, Raymond 
Filipe,

I have the following standard files "INITRD.IMG, KERNEL.IMG,GENERIC.PRM and 
REDHAT.EXEC when working Redhat 6. Can they still be used for Redhat 7?

Thanks,
Ray



-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Filipe 
Miranda
Sent: Wednesday, July 22, 2015 12:29 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Linux 7.1 on z/VM 6.3

Email sent from outside of PSEG. Use caution before using links/attachments.


Hello Rick,

Everything seems to be in order on that PARM file.

The only option I haven’t tried yet from this PARM is to force the resolution 
by using the  inst.resolution=1024x768 parameter, but I’m not sure if that 
maybe causing some weird behavior by the VNC client/server piece.
I know it sounds silly, but could you try with the following PARM file:

ro ramdisk_size=4 cio_ignore=all,!condev 
ip=xxx.xxx.xxx.xxx::xxx.xxx.xxx.xxx:22:lnxmnt71.marriott.com:enccw0.0.0500:none
rd.znet=qeth,0.0.0500,0.0.0501,0.0.0502,layer2=0
nameserver=xxx.xxx.xxx.xxx
rd.dasd=0.0.0200 rd.dasd=0.0.0300 rd.dasd=0.0.0301 inst.vnc 
inst.vncpassword=
inst.repo=nfs:xxx.xxx.xxx.xxx:/var/opt/rhel71

if that fails again, does the installer gives you any hint of what might have 
happened? Are you able to get a shell access ?


Thank you,

Kind Regards,
Filipe Miranda


> On Jul 22, 2015, at 8:30 AM, Beard, Rick (Atos)  wrote:
> 
> Filipe,
> 
> 
> 
> I'm using ECKD DASD and it was formatted using CA's VMDIRECT software when it 
> allocated it to the Linux image.
> 
> 
> 
> Here is my PARM file.
> 
> 
> 
> ro ramdisk_size=4 cio_ignore=all,!condev
> 
> ip=xxx.xxx.xxx.xxx::xxx.xxx.xxx.xxx:22:lnxmnt71.marriott.com:enccw0.0.
> 0500:none
> 
> 
> 
> rd.znet=qeth,0.0.0500,0.0.0501,0.0.0502,layer2=0
> 
> nameserver=xxx.xxx.xxx.xxx
> 
> rd.dasd=0.0.0200
> 
> rd.dasd=0.0.0300
> 
> rd.dasd=0.0.0301
> 
> inst.resolution=1024x768
> 
> inst.vnc
> 
> inst.vncpassword=
> 
> inst.repo=nfs:xxx.xxx.xxx.xxx:/var/opt/rhel71
> 
> 
> 
> 
> 
> -Original Message-
> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of 
> Filipe Miranda
> Sent: Tuesday, July 21, 2015 1:59 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: Linux 7.1 on z/VM 6.3
> 
> 
> 
> 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) 
>> mailto: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<mailto: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) 
>>> mailto: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 3

Re: Linux 7.1 on z/VM 6.3

2015-07-22 Thread Beard, Rick (Atos) 
Filipe,

Red Hat suggested I add the resolution PARM, but I'll try what you sent and let 
you know.

Thanks,

Rick

-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Filipe 
Miranda
Sent: Wednesday, July 22, 2015 12:29 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Linux 7.1 on z/VM 6.3

Hello Rick,

Everything seems to be in order on that PARM file.

The only option I haven’t tried yet from this PARM is to force the resolution 
by using the  inst.resolution=1024x768 parameter, but I’m not sure if that 
maybe causing some weird behavior by the VNC client/server piece.
I know it sounds silly, but could you try with the following PARM file:

ro ramdisk_size=4 cio_ignore=all,!condev 
ip=xxx.xxx.xxx.xxx::xxx.xxx.xxx.xxx:22:lnxmnt71.marriott.com:enccw0.0.0500:none
rd.znet=qeth,0.0.0500,0.0.0501,0.0.0502,layer2=0
nameserver=xxx.xxx.xxx.xxx
rd.dasd=0.0.0200 rd.dasd=0.0.0300 rd.dasd=0.0.0301 inst.vnc 
inst.vncpassword=
inst.repo=nfs:xxx.xxx.xxx.xxx:/var/opt/rhel71

if that fails again, does the installer gives you any hint of what might have 
happened? Are you able to get a shell access ?


Thank you,

Kind Regards,
Filipe Miranda


> On Jul 22, 2015, at 8:30 AM, Beard, Rick (Atos)  wrote:
> 
> Filipe,
> 
> 
> 
> I'm using ECKD DASD and it was formatted using CA's VMDIRECT software when it 
> allocated it to the Linux image.
> 
> 
> 
> Here is my PARM file.
> 
> 
> 
> ro ramdisk_size=4 cio_ignore=all,!condev
> 
> ip=xxx.xxx.xxx.xxx::xxx.xxx.xxx.xxx:22:lnxmnt71.marriott.com:enccw0.0.
> 0500:none
> 
> 
> 
> rd.znet=qeth,0.0.0500,0.0.0501,0.0.0502,layer2=0
> 
> nameserver=xxx.xxx.xxx.xxx
> 
> rd.dasd=0.0.0200
> 
> rd.dasd=0.0.0300
> 
> rd.dasd=0.0.0301
> 
> inst.resolution=1024x768
> 
> inst.vnc
> 
> inst.vncpassword=
> 
> inst.repo=nfs:xxx.xxx.xxx.xxx:/var/opt/rhel71
> 
> 
> 
> 
> 
> -Original Message-
> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of 
> Filipe Miranda
> Sent: Tuesday, July 21, 2015 1:59 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: Linux 7.1 on z/VM 6.3
> 
> 
> 
> 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) 
>> mailto: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<mailto: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) 
>>> mailto: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

Re: Linux 7.1 on z/VM 6.3

2015-07-22 Thread Filipe Miranda 
Hello Rick,

Everything seems to be in order on that PARM file.

The only option I haven’t tried yet from this PARM is to force the resolution 
by using the  inst.resolution=1024x768 parameter, but I’m not sure if that 
maybe causing some weird behavior by the VNC client/server piece.
I know it sounds silly, but could you try with the following PARM file:

ro ramdisk_size=4 cio_ignore=all,!condev
ip=xxx.xxx.xxx.xxx::xxx.xxx.xxx.xxx:22:lnxmnt71.marriott.com:enccw0.0.0500:none
rd.znet=qeth,0.0.0500,0.0.0501,0.0.0502,layer2=0
nameserver=xxx.xxx.xxx.xxx
rd.dasd=0.0.0200 rd.dasd=0.0.0300 rd.dasd=0.0.0301
inst.vnc
inst.vncpassword=
inst.repo=nfs:xxx.xxx.xxx.xxx:/var/opt/rhel71

if that fails again, does the installer gives you any hint of what might have 
happened? Are you able to get a shell access ?


Thank you,

Kind Regards,
Filipe Miranda


> On Jul 22, 2015, at 8:30 AM, Beard, Rick (Atos)  wrote:
> 
> Filipe,
> 
> 
> 
> I'm using ECKD DASD and it was formatted using CA's VMDIRECT software when it 
> allocated it to the Linux image.
> 
> 
> 
> Here is my PARM file.
> 
> 
> 
> ro ramdisk_size=4 cio_ignore=all,!condev
> 
> ip=xxx.xxx.xxx.xxx::xxx.xxx.xxx.xxx:22:lnxmnt71.marriott.com:enccw0.0.0500:none
> 
> 
> 
> rd.znet=qeth,0.0.0500,0.0.0501,0.0.0502,layer2=0
> 
> nameserver=xxx.xxx.xxx.xxx
> 
> rd.dasd=0.0.0200
> 
> rd.dasd=0.0.0300
> 
> rd.dasd=0.0.0301
> 
> inst.resolution=1024x768
> 
> inst.vnc
> 
> inst.vncpassword=
> 
> inst.repo=nfs:xxx.xxx.xxx.xxx:/var/opt/rhel71
> 
> 
> 
> 
> 
> -Original Message-
> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Filipe 
> Miranda
> Sent: Tuesday, July 21, 2015 1:59 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: Linux 7.1 on z/VM 6.3
> 
> 
> 
> 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) 
>> mailto: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<mailto: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) 
>>> mailto: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<mailto: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

Re: Linux 7.1 on z/VM 6.3

2015-07-22 Thread Beard, Rick (Atos) 
Filipe,



I'm using ECKD DASD and it was formatted using CA's VMDIRECT software when it 
allocated it to the Linux image.



Here is my PARM file.



ro ramdisk_size=4 cio_ignore=all,!condev

ip=xxx.xxx.xxx.xxx::xxx.xxx.xxx.xxx:22:lnxmnt71.marriott.com:enccw0.0.0500:none



rd.znet=qeth,0.0.0500,0.0.0501,0.0.0502,layer2=0

nameserver=xxx.xxx.xxx.xxx

rd.dasd=0.0.0200

rd.dasd=0.0.0300

rd.dasd=0.0.0301

inst.resolution=1024x768

inst.vnc

inst.vncpassword=

inst.repo=nfs:xxx.xxx.xxx.xxx:/var/opt/rhel71





-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Filipe 
Miranda
Sent: Tuesday, July 21, 2015 1:59 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Linux 7.1 on z/VM 6.3



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) 
> mailto: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<mailto: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) 
>> mailto: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<mailto: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%20Event

>> s /IBM%20T3%20Bobligen%20Germany%202015%20v2.pdf

>> <http://people.redhat.com/fmiranda/systemz/slide_decks/Special%20Even

>> t s/IBM%20T3%20Bobligen%20Germany%202015%20v2.pdf>

>>

>> Kind Regards,

>>

>> Filipe Miranda

>> fmira...@redhat.com<mailto:fmira...@redhat.com>

>>

>>> On Jul 17, 2015, at 7:17 AM, Grzegorz Powiedziuk 
>>> mailto:gpowiedz...@gmail.com>> wrote:

>>>

>>> 2015-07-17 9:55 GMT-04:00 Beard, Rick (Atos) 
>>> mailto: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=4

>>>> CMSDASD=191 CMSCONFFILE=xx.CONF-RH7

>>

Re: Linux 7.1 on z/VM 6.3

2015-07-21 Thread Filipe Miranda 
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)  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)  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  
>>> wrote:
>>> 
>>> 2015-07-17 9:55 GMT-04:00 Beard, Rick (Atos) :
>>> 
>>>> 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=4
>>>> CMSDASD=191 CMSCONFFILE=xx.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=4 cio_ignore=all,!condev
>>> CMSDASD=191
>>> CMSCONFFILE=xxx.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 .CONF-RH7 file:
>>>> 
>>>> DASD=200,204
>>>> HOSTNAME=..com
>>>> NETTYPE=qeth
>>>> IPADDR=xxx.xxx.xxx.xxx
>>>> SUBCHANNELS=0.0.0500,0.0.0501,0.0.0502
>>>> NETMASK=xxx.xxx.xxx.xxx
>>>> SEARCHDNS=.com
>>>> METHOD=nfs:x:/var/opt/rhel71
>>>> GATEWAY=xxx.xxx.xxx.xxx
>>>> DNS=xxx.xxx.xxx.xxx
>>>> MTU=1492
>>>> PORTNAME=
>>>> PORTNO=0
>>>> LAYER2=0
&g

Re: Linux 7.1 on z/VM 6.3

2015-07-21 Thread Beard, Rick (Atos) 
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)  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  
>> wrote:
>> 
>> 2015-07-17 9:55 GMT-04:00 Beard, Rick (Atos) :
>> 
>>> 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=4
>>> CMSDASD=191 CMSCONFFILE=xx.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=4 cio_ignore=all,!condev
>> CMSDASD=191
>> CMSCONFFILE=xxx.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 .CONF-RH7 file:
>>> 
>>> DASD=200,204
>>> HOSTNAME=..com
>>> NETTYPE=qeth
>>> IPADDR=xxx.xxx.xxx.xxx
>>> SUBCHANNELS=0.0.0500,0.0.0501,0.0.0502
>>> NETMASK=xxx.xxx.xxx.xxx
>>> SEARCHDNS=.com
>>> METHOD=nfs:x:/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/

Re: Linux 7.1 on z/VM 6.3

2015-07-21 Thread Filipe Miranda 
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)  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%20Events/IBM%20T3%20Bobligen%20Germany%202015%20v2.pdf>
> 
> Kind Regards,
> 
> Filipe Miranda
> fmira...@redhat.com
> 
>> On Jul 17, 2015, at 7:17 AM, Grzegorz Powiedziuk  
>> wrote:
>> 
>> 2015-07-17 9:55 GMT-04:00 Beard, Rick (Atos) :
>> 
>>> 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=4
>>> CMSDASD=191 CMSCONFFILE=xx.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=4 cio_ignore=all,!condev
>> CMSDASD=191
>> CMSCONFFILE=xxx.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 .CONF-RH7 file:
>>> 
>>> DASD=200,204
>>> HOSTNAME=..com
>>> NETTYPE=qeth
>>> IPADDR=xxx.xxx.xxx.xxx
>>> SUBCHANNELS=0.0.0500,0.0.0501,0.0.0502
>>> NETMASK=xxx.xxx.xxx.xxx
>>> SEARCHDNS=.com
>>> METHOD=nfs:x:/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/

Re: Linux 7.1 on z/VM 6.3

2015-07-21 Thread Beard, Rick (Atos) 
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%20Events/IBM%20T3%20Bobligen%20Germany%202015%20v2.pdf>

Kind Regards,

Filipe Miranda
fmira...@redhat.com

> On Jul 17, 2015, at 7:17 AM, Grzegorz Powiedziuk  
> wrote:
> 
> 2015-07-17 9:55 GMT-04:00 Beard, Rick (Atos) :
> 
>> 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=4
>> CMSDASD=191 CMSCONFFILE=xx.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=4 cio_ignore=all,!condev
> CMSDASD=191
> CMSCONFFILE=xxx.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 .CONF-RH7 file:
>> 
>> DASD=200,204
>> HOSTNAME=..com
>> NETTYPE=qeth
>> IPADDR=xxx.xxx.xxx.xxx
>> SUBCHANNELS=0.0.0500,0.0.0501,0.0.0502
>> NETMASK=xxx.xxx.xxx.xxx
>> SEARCHDNS=.com
>> METHOD=nfs:x:/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/

Re: Linux 7.1 on z/VM 6.3

2015-07-20 Thread Filipe Miranda 
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
 


Kind Regards,

Filipe Miranda
fmira...@redhat.com

> On Jul 17, 2015, at 7:17 AM, Grzegorz Powiedziuk  
> wrote:
> 
> 2015-07-17 9:55 GMT-04:00 Beard, Rick (Atos) :
> 
>> 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=4
>> CMSDASD=191 CMSCONFFILE=xx.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=4 cio_ignore=all,!condev
> CMSDASD=191
> CMSCONFFILE=xxx.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 .CONF-RH7 file:
>> 
>> DASD=200,204
>> HOSTNAME=..com
>> NETTYPE=qeth
>> IPADDR=xxx.xxx.xxx.xxx
>> SUBCHANNELS=0.0.0500,0.0.0501,0.0.0502
>> NETMASK=xxx.xxx.xxx.xxx
>> SEARCHDNS=.com
>> METHOD=nfs:x:/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/


signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: Linux 7.1 on z/VM 6.3

2015-07-17 Thread Grzegorz Powiedziuk 
2015-07-17 9:55 GMT-04:00 Beard, Rick (Atos) :

> 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=4
> CMSDASD=191 CMSCONFFILE=xx.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=4 cio_ignore=all,!condev
CMSDASD=191
CMSCONFFILE=xxx.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 .CONF-RH7 file:
>
> DASD=200,204
> HOSTNAME=..com
> NETTYPE=qeth
> IPADDR=xxx.xxx.xxx.xxx
> SUBCHANNELS=0.0.0500,0.0.0501,0.0.0502
> NETMASK=xxx.xxx.xxx.xxx
> SEARCHDNS=.com
> METHOD=nfs:x:/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/

Re: Linux 7.1 on z/VM 6.3

2015-07-17 Thread Grzegorz Powiedziuk 
Oh yes, these @@@ are just being used by linux scripts for finding the
right string before doing sed on them. The final output that goes to a cms
disk has real values and is being translated to ebdic.

Gregory Powiedziuk

2015-07-17 9:56 GMT-04:00 Alan Altmark :

> On Friday, 07/17/2015 at 09:33 EDT, Grzegorz Powiedziuk
>  wrote:
> > I've installed dozens of rhel70 and rhel71
> > here are my templates fot 71 (I am using my own homegrown web interface
> for
> > auto and easy virtual machines creation and rhel installation without
> even
> > touching 3270 )
>
> When I hear hoofbeats, I always think 'zebras!'  Since your config files
> are coming from CMS, make sure that the @ symbol is being translated
> correctly by cmsfs.  There are a lot of EBCDIC code pages that do not have
> @ as 0x7C.
>
> Of course, if you've ssh'd into the Linux guest, looked at the config
> file, and have seen '@', then you're ok in that respect.
>
> Alan Altmark
>
> Senior Managing z/VM and Linux Consultant
> Lab Services System z Delivery Practice
> IBM Systems & Technology Group
> ibm.com/systems/services/labservices
> office: 607.429.3323
> mobile; 607.321.7556
> alan_altm...@us.ibm.com
> IBM Endicott
>
> --
> 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: Linux 7.1 on z/VM 6.3

2015-07-17 Thread Alan Altmark 
On Friday, 07/17/2015 at 09:33 EDT, Grzegorz Powiedziuk
 wrote:
> I've installed dozens of rhel70 and rhel71
> here are my templates fot 71 (I am using my own homegrown web interface
for
> auto and easy virtual machines creation and rhel installation without
even
> touching 3270 )

When I hear hoofbeats, I always think 'zebras!'  Since your config files
are coming from CMS, make sure that the @ symbol is being translated
correctly by cmsfs.  There are a lot of EBCDIC code pages that do not have
@ as 0x7C.

Of course, if you've ssh'd into the Linux guest, looked at the config
file, and have seen '@', then you're ok in that respect.

Alan Altmark

Senior Managing z/VM and Linux Consultant
Lab Services System z Delivery Practice
IBM Systems & Technology Group
ibm.com/systems/services/labservices
office: 607.429.3323
mobile; 607.321.7556
alan_altm...@us.ibm.com
IBM Endicott

--
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: Linux 7.1 on z/VM 6.3

2015-07-17 Thread Beard, Rick (Atos) 
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=4
CMSDASD=191 CMSCONFFILE=xx.CONF-RH7  

And here is the .CONF-RH7 file:

DASD=200,204  
HOSTNAME=..com
NETTYPE=qeth  
IPADDR=xxx.xxx.xxx.xxx  
SUBCHANNELS=0.0.0500,0.0.0501,0.0.0502
NETMASK=xxx.xxx.xxx.xxx 
SEARCHDNS=.com
METHOD=nfs:x:/var/opt/rhel71   
GATEWAY=xxx.xxx.xxx.xxx  
DNS=xxx.xxx.xxx.xxx 
MTU=1492  
PORTNAME= 
PORTNO=0  
LAYER2=0  

-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Grzegorz 
Powiedziuk
Sent: Friday, July 17, 2015 9:33 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Linux 7.1 on z/VM 6.3

I've installed dozens of rhel70 and rhel71 here are my templates fot 71 (I am 
using my own homegrown web interface for auto and easy virtual machines 
creation and rhel installation without even touching 3270 )

conf file template:
HOSTNAME="@@@hostname@@@"
DASD="200"
NETTYPE="qeth"
SUBCHANNELS="0.0.2000,0.0.2001,0.0.2002"
IPADDR="@@@ip_address@@@"
NETMASK="@@@netmask@@@"
GATEWAY="@@@gw@@@"
PORTNO="0"
LAYER2="1"
VSWITCH="0"
DNS="@@@dns1@@@:@@@dns2@@@"
MTU="1500"

parm file template:
ro ramdisk_size=4 cio_ignore=all,!condev CMSDASD=192 
CMSCONFFILE=@@@hostname@@@.conf RUNKS=1 
inst.ks=http://10.50.223.250/vmwiz/punch_files/@@@hostname@@@.ks

kickstart file (which is hosted on 10.50.223.250vmwiz/punch_files in my
case) :

#version=RHEL7.1
# System authorization information
auth --enableshadow --passalgo=sha512
cmdline
reboot
# Use network installation
url --url="http://10.50.223.250/rhel71";
# Run the Setup Agent on first boot
firstboot --enable
ignoredisk --only-use=dasda
# Keyboard layouts
keyboard --vckeymap=us --xlayouts='us'
# System language
lang en_US.UTF-8

# Network information
network  --bootproto=static --device=enccw0.0.2000 --gateway=@@@gw@@@ 
--ip=@@@ip_address@@@ --mtu=1500 --nameserver=@@@dns1@@@,@@@dns2@@@
--netmask=@@@netmask@@@ --noipv6 --activate network  --hostname=@@@hostname@@@ 
# Root password rootpw --iscrypted BLABLABLA # System timezone timezone 
America/New_York # System bootloader configuration bootloader --location=mbr 
--boot-drive=dasda # Partition clearing information clearpart --all --initlabel 
zerombr # Disk partitioning information # part pv.23 --fstype="lvmpv" 
--ondisk=dasda --size=3071

part /boot --fstype="ext4" --ondisk=dasda --size=120 part pv.23 
--fstype="lvmpv" --ondisk=dasda --size=1 --grow #  /boot no longer works in LVM 
in Redhat 7.1 volgroup rhel_@@@hostname@@@ --pesize=4096 pv.23 logvol /  
--fstype="ext4" --size=2946 --name=root --vgname=rhel_@@@hostname@ @@

%packages
@core
wget
%end

Gregory Powiedziuk



2015-07-17 8:38 GMT-04:00 Beard, Rick (Atos) :

> It's got plenty of memory and CPU.  I have built a new z/VM 6.3 SSI 
> system and only have one guest running in it so far on Red Hat Linux version 
> 6.5.
> I wanted to see about running version 7.1, but it appears Red Hat must 
> have made some changes on how to install it as my PARM file, that I 
> have been using for years on multiple versions, is not working on this 
> version.  I have a case open with them and will let you what I find out.
>
> Rick
>
> -Original Message-
> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of 
> Mark Post
> Sent: Thursday, July 16, 2015 1:56 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: Linux 7.1 on z/VM 6.3
>
> >>> On 7/16/2015 at 01:41 PM, Rick Troth  wrote:
> > How much memory?
>
> I would be more interested in knowing how much CPU is available.  It 
> sounds like the guest isn't getting much, if any, of a time slice to run in.
>
>
> Mark Post
>
> --
> 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
> --
&g

Re: Linux 7.1 on z/VM 6.3

2015-07-17 Thread Grzegorz Powiedziuk 
I've installed dozens of rhel70 and rhel71
here are my templates fot 71 (I am using my own homegrown web interface for
auto and easy virtual machines creation and rhel installation without even
touching 3270 )

conf file template:
HOSTNAME="@@@hostname@@@"
DASD="200"
NETTYPE="qeth"
SUBCHANNELS="0.0.2000,0.0.2001,0.0.2002"
IPADDR="@@@ip_address@@@"
NETMASK="@@@netmask@@@"
GATEWAY="@@@gw@@@"
PORTNO="0"
LAYER2="1"
VSWITCH="0"
DNS="@@@dns1@@@:@@@dns2@@@"
MTU="1500"

parm file template:
ro ramdisk_size=4 cio_ignore=all,!condev CMSDASD=192
CMSCONFFILE=@@@hostname@@@.conf RUNKS=1
inst.ks=http://10.50.223.250/vmwiz/punch_files/@@@hostname@@@.ks

kickstart file (which is hosted on 10.50.223.250vmwiz/punch_files in my
case) :

#version=RHEL7.1
# System authorization information
auth --enableshadow --passalgo=sha512
cmdline
reboot
# Use network installation
url --url="http://10.50.223.250/rhel71";
# Run the Setup Agent on first boot
firstboot --enable
ignoredisk --only-use=dasda
# Keyboard layouts
keyboard --vckeymap=us --xlayouts='us'
# System language
lang en_US.UTF-8

# Network information
network  --bootproto=static --device=enccw0.0.2000 --gateway=@@@gw@@@
--ip=@@@ip_address@@@ --mtu=1500 --nameserver=@@@dns1@@@,@@@dns2@@@
--netmask=@@@netmask@@@ --noipv6 --activate
network  --hostname=@@@hostname@@@
# Root password
rootpw --iscrypted BLABLABLA
# System timezone
timezone America/New_York
# System bootloader configuration
bootloader --location=mbr --boot-drive=dasda
# Partition clearing information
clearpart --all --initlabel
zerombr
# Disk partitioning information
# part pv.23 --fstype="lvmpv" --ondisk=dasda --size=3071

part /boot --fstype="ext4" --ondisk=dasda --size=120
part pv.23 --fstype="lvmpv" --ondisk=dasda --size=1 --grow
#  /boot no longer works in LVM in Redhat 7.1
volgroup rhel_@@@hostname@@@ --pesize=4096 pv.23
logvol /  --fstype="ext4" --size=2946 --name=root --vgname=rhel_@@@hostname@
@@

%packages
@core
wget
%end

Gregory Powiedziuk



2015-07-17 8:38 GMT-04:00 Beard, Rick (Atos) :

> It's got plenty of memory and CPU.  I have built a new z/VM 6.3 SSI system
> and only have one guest running in it so far on Red Hat Linux version 6.5.
> I wanted to see about running version 7.1, but it appears Red Hat must have
> made some changes on how to install it as my PARM file, that I have been
> using for years on multiple versions, is not working on this version.  I
> have a case open with them and will let you what I find out.
>
> Rick
>
> -Original Message-
> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
> Mark Post
> Sent: Thursday, July 16, 2015 1:56 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: Linux 7.1 on z/VM 6.3
>
> >>> On 7/16/2015 at 01:41 PM, Rick Troth  wrote:
> > How much memory?
>
> I would be more interested in knowing how much CPU is available.  It
> sounds like the guest isn't getting much, if any, of a time slice to run in.
>
>
> Mark Post
>
> --
> 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: Linux 7.1 on z/VM 6.3

2015-07-17 Thread Beard, Rick (Atos) 
It's got plenty of memory and CPU.  I have built a new z/VM 6.3 SSI system and 
only have one guest running in it so far on Red Hat Linux version 6.5.  I 
wanted to see about running version 7.1, but it appears Red Hat must have made 
some changes on how to install it as my PARM file, that I have been using for 
years on multiple versions, is not working on this version.  I have a case open 
with them and will let you what I find out.

Rick

-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post
Sent: Thursday, July 16, 2015 1:56 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Linux 7.1 on z/VM 6.3

>>> On 7/16/2015 at 01:41 PM, Rick Troth  wrote: 
> How much memory?

I would be more interested in knowing how much CPU is available.  It sounds 
like the guest isn't getting much, if any, of a time slice to run in.


Mark Post

--
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: Linux 7.1 on z/VM 6.3

2015-07-16 Thread Mark Post 
>>> On 7/16/2015 at 01:41 PM, Rick Troth  wrote: 
> How much memory?

I would be more interested in knowing how much CPU is available.  It sounds 
like the guest isn't getting much, if any, of a time slice to run in.


Mark Post

--
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: Linux 7.1 on z/VM 6.3

2015-07-16 Thread Rick Troth 
On 07/16/2015 01:28 PM, Beard, Rick (Atos) wrote:
> Anyone try to install Linux version 7.1 on z/VM 6.3 yet? 

Mr. Pedantic here.
You meah RHEL 7.1 for situations where it matters. (Or just "RHEL 7".)


>  I tried too, but when I punch the reader to start the install I get the 
> following ugly messages:

Just to confirm, you punched three files, kernel, parm line(s), and
INITRD. Yes? (but guessing you did, so read on)


> Ý  122.518597¨ INFO: rcu_sched self-detected stall on CPU { 1
> Ý  149.846203¨ INFO: rcu_sched detected stalls on CPUs/tasks:}
> Ý  149.846205¨  { 1} Ý  149.846210¨  (t=14692 jiffies g=18446744073709551434 
> c=18446744073709551433 q=194)
> (detected by 0, t=14692 jiffies, g=18446744073709551434, 
> c=18446744073709551433, q=194)
> Ý  149.846212¨ Task dump for CPU 1:
> Ý  149.846214¨ CPU: 1 PID: 0 Comm: swapper/1 Not tainted 3.10.0-229.el7.s390x 
> #1
>
> Ý  149.846219¨3f887b40 3f887b50 0002 
> 
> Ý  149.846219¨3f887be0 3f887b58 3f887b58 
> 0112018
> Ý  149.846219¨003c9642 0073ee10 00722ffe 
> 000b
> Ý  149.846219¨3f887ba0 3f887b40  
> 
> Ý  149.846219¨036f1c60 00112018 3f887b40 
> 3f887ba0
> Ý  149.846219¨ Call Trace:
> Ý  149.846224¨ (Ý<00111f5a>¨ show_trace+0x12a/0x130)
> Ý  149.846225¨  Ý<00111fcc>¨ show_stack+0x6c/0xe801: HCPGSP2629I The 
> virtual machine is placed in CP mode due to a SIGP stop from
>  CPU 00.
> 00: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop 
> from CPU 00.

How much memory?
What machine setting? (#CP Q SET should show "MACHINE XA" and *not*
"MACHINE XC".)

-- R; <><

--
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/