Re: RHEL8 Installation Problem

2021-01-05 Thread Neale Ferguson
I increased the relative SHARE of the guest and was able to get to the point of 
package installation where it then crapped out. I am going to try again and 
note the crash output.

Neale Ferguson

On 1/6/21, 03:28, "Linux on 390 Port on behalf of Mark Post" 
 wrote:

 
Did you ever get this resolved?



--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www2.marist.edu/htbin/wlvindex?LINUX-390


Re: RHEL8 Installation Problem

2021-01-04 Thread Jan Stodola
Hi Neale,
are you also able to reproduce this problem on RHEL-8.3? If yes, could you
please report it via https://bugzilla.redhat.com against anaconda for
further review? Please, attach log files from /tmp (you can ssh as root to
the installation environment).
Such problems (Anaconda DBus modules failed to start on time) usually
happen on very slow systems.

Regards,
Jan



On Tue, Dec 22, 2020 at 5:12 AM Neale Ferguson  wrote:

> When installing RHEL8 on my z/VM 7.1 system I get to the part where I am
> asked to ssh inst...@xx.xx.xx.xx where it
> then hangs before
>
>
>
> anaconda 29.19.2.17-1.el8 for Red Hat Enterprise Linux 8.2 started.
>
> * installation log files are stored in /tmp during the installation
>
> * shell is available in second TMUX pane (ctrl+b, then press 2)
>
> * when reporting a bug add logs from /tmp as separate text/plain
> attachments
>
>
>
> After several minutes the next message appears:
>
>
>
> 04:05:19 Anaconda DBus modules failed to start on time.
>
>
>
> Syslog shows that during this time…
>
>
>
> 04:05:29,355 INFO systemd:anaconda-shell@hvc1.service: Service has no
> hold-off time (RestartSec=0), scheduling restart.
>
> 04:05:29,365 INFO systemd:anaconda-shell@hvc1.service: Scheduled restart
> job, restart counter is at 90.
>
> 04:05:29,381 INFO systemd:Stopped Shell on hvc1.
>
> 04:05:29,424 INFO systemd:Started Shell on hvc1.
>
> 04:05:31,889 INFO dbus-daemon:Reloaded configuration
>
> 04:05:39,620 NOTICE kernel:audit: type=1131 audit(1608609939.607:315):
> pid=1 uid=0 auid=4294967295 ses=4294967295
> subj=system_u:system_r:kernel_t:s0 msg='unit=anaconda-shell@hvc1
> comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?
> res=success'
>
> 04:05:39,644 INFO systemd:anaconda-shell@hvc1.service: Service has no
> hold-off time (RestartSec=0), scheduling restart.
>
> 04:05:39,657 INFO systemd:anaconda-shell@hvc1.service: Scheduled restart
> job, restart counter is at 91.
>
> 04:05:39,677 INFO systemd:Stopped Shell on hvc1.
>
> 04:05:39,680 NOTICE kernel:audit: type=1130 audit(1608609939.667:316):
> pid=1 uid=0 auid=4294967295 ses=4294967295
> subj=system_u:system_r:kernel_t:s0 msg='unit=anaconda-shell@hvc1
> comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?
> res=success'
>
> 04:05:39,681 NOTICE kernel:audit: type=1131 audit(1608609939.667:317):
> pid=1 uid=0 auid=4294967295 ses=4294967295
> subj=system_u:system_r:kernel_t:s0 msg='unit=anaconda-shell@hvc1
> comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?
> res=success'
>
> 04:05:39,732 INFO systemd:Started Shell on hvc1.
>
> :
>
> :
>
>
>
> I am not sure what it’s complaining about or expecting.
>
>
>
> Neale
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www2.marist.edu/htbin/wlvindex?LINUX-390
>

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www2.marist.edu/htbin/wlvindex?LINUX-390


Re: RHEL8 Installation Problem

2020-12-26 Thread Sebastian Welton
Back in 2019 I had many problems trying to get RHEL 8.0 to install (you 
can check the archives) and eventually gave up and used Ubuntu for the 
install. I now have to build another RHEL 8 system and hit the same 
problems and have discovered many new ones. The system I am building is 
in fact under zPDT and needs to run on bare metal however I have now 
successfully installed it under z/VM using a GENERIC.PRM (even tried 
CMSCONFFILE and CMSDASD with no luck.) This is the one I used and 
hopefully it will work for you:



ro ramdisk_size=4 !condev
rd.znet=qeth,0.0.0400,0.0.0401,0.0.0402,layer2=1,portno=0
ip=linux_ip_address::z/VM_ip_address:24:hostname:enc400:none
inst.repo=ftp://userid:password@ftp_server_ip_address/directory_where_the_ISO_is 
mounted

rd.dasd=0.0.02d0 rd.dasd=0.0.02d1 rd.dasd=0.0.02d2


Each statement is on a separate line. It is quite a slow installation 
and I can say, I had absolutely no problems with SLES15 or Ubuntu and 
might start a separate post with the original problems that I have 
encountered as they are quite interesting and would like to somehow 
resolve them.


MfG / Best Regards
--
Sebastian Welton

On 12/24/2020 6:00 AM, LINUX-390 automatic digest system wrote:

Date:Wed, 23 Dec 2020 08:08:46 +
From:Neale Ferguson 
Subject: Re: RHEL8 Installation Problem

Would someone share a working “GENERIC PRM” for RHEL 8? Please sanitize any 
sensitive information of course.



Neale




--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www2.marist.edu/htbin/wlvindex?LINUX-390


Re: RHEL8 Installation Problem

2020-12-23 Thread munif sadek
Hi Neale, Vic


generic.prm is

\RHEL\8.3\images

ro ramdisk_size=4 cio_ignore=all,!condev



and generic.ins is

\RHEL\8.3

* minimal lpar ins file

images/kernel.img 0x

images/initrd.img 0x0200

images/genericdvd.prm 0x00010480

images/initrd.addrsize 0x00010408


Regards
Munif

On Wed, 23 Dec 2020, 4:14 pm Vic Cross,  wrote:

> Hi Neale,
>
> This one comes from an Ansible playbook, so forgive the Jinja fields (but
> I guess it's sanitised, lol)
>
> ro ramdisk_size=4 cio_ignore=all,!condev
> rd.dasd={{ guest_install_dasd }}
> rd.znet={{ guest_install_znet }}
> rd.znet={{ guest_internal_znet }}
> ip={{ guest_temp_ipaddr }}::{{ guest_install_gateway }}:{{
> guest_install_netmask }}:{{ guest_install_hostname }}:{{
> guest_install_nicid }}:none
> nameserver={{ guest_install_nameserver }}
> inst.repo={{ guest_install_baseurl }}/
> inst.ks={{ guest_install_ksurl }}/{{guest_install_hostname }}.ks
>
> Regards,
> Vic
>
>
> Vic Cross
> Solutions Engineer, Z Acceleration Team
> IBM Z (Worldwide)
> E-mail: viccr...@au1.ibm.com Twitter: @viccross
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www2.marist.edu/htbin/wlvindex?LINUX-390
>

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www2.marist.edu/htbin/wlvindex?LINUX-390


Re: RHEL8 Installation Problem

2020-12-23 Thread Vic Cross
Hi Neale,

This one comes from an Ansible playbook, so forgive the Jinja fields (but I 
guess it's sanitised, lol)

ro ramdisk_size=4 cio_ignore=all,!condev
rd.dasd={{ guest_install_dasd }}
rd.znet={{ guest_install_znet }}
rd.znet={{ guest_internal_znet }}
ip={{ guest_temp_ipaddr }}::{{ guest_install_gateway }}:{{ 
guest_install_netmask }}:{{ guest_install_hostname }}:{{ guest_install_nicid 
}}:none
nameserver={{ guest_install_nameserver }}
inst.repo={{ guest_install_baseurl }}/
inst.ks={{ guest_install_ksurl }}/{{guest_install_hostname }}.ks

Regards,
Vic


Vic Cross
Solutions Engineer, Z Acceleration Team
IBM Z (Worldwide)
E-mail: viccr...@au1.ibm.com Twitter: @viccross

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www2.marist.edu/htbin/wlvindex?LINUX-390


Re: RHEL8 Installation Problem

2020-12-23 Thread Neale Ferguson
Would someone share a working “GENERIC PRM” for RHEL 8? Please sanitize any 
sensitive information of course.



Neale

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www2.marist.edu/htbin/wlvindex?LINUX-390


RHEL8 Installation Problem

2020-12-21 Thread Neale Ferguson
When installing RHEL8 on my z/VM 7.1 system I get to the part where I am asked 
to ssh inst...@xx.xx.xx.xx where it then hangs 
before



anaconda 29.19.2.17-1.el8 for Red Hat Enterprise Linux 8.2 started.

* installation log files are stored in /tmp during the installation

* shell is available in second TMUX pane (ctrl+b, then press 2)

* when reporting a bug add logs from /tmp as separate text/plain attachments



After several minutes the next message appears:



04:05:19 Anaconda DBus modules failed to start on time.



Syslog shows that during this time…



04:05:29,355 INFO systemd:anaconda-shell@hvc1.service: Service has no hold-off 
time (RestartSec=0), scheduling restart.

04:05:29,365 INFO systemd:anaconda-shell@hvc1.service: Scheduled restart job, 
restart counter is at 90.

04:05:29,381 INFO systemd:Stopped Shell on hvc1.

04:05:29,424 INFO systemd:Started Shell on hvc1.

04:05:31,889 INFO dbus-daemon:Reloaded configuration

04:05:39,620 NOTICE kernel:audit: type=1131 audit(1608609939.607:315): pid=1 
uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:kernel_t:s0 
msg='unit=anaconda-shell@hvc1 comm="systemd" exe="/usr/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'

04:05:39,644 INFO systemd:anaconda-shell@hvc1.service: Service has no hold-off 
time (RestartSec=0), scheduling restart.

04:05:39,657 INFO systemd:anaconda-shell@hvc1.service: Scheduled restart job, 
restart counter is at 91.

04:05:39,677 INFO systemd:Stopped Shell on hvc1.

04:05:39,680 NOTICE kernel:audit: type=1130 audit(1608609939.667:316): pid=1 
uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:kernel_t:s0 
msg='unit=anaconda-shell@hvc1 comm="systemd" exe="/usr/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'

04:05:39,681 NOTICE kernel:audit: type=1131 audit(1608609939.667:317): pid=1 
uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:kernel_t:s0 
msg='unit=anaconda-shell@hvc1 comm="systemd" exe="/usr/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'

04:05:39,732 INFO systemd:Started Shell on hvc1.

:

:



I am not sure what it’s complaining about or expecting.



Neale

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www2.marist.edu/htbin/wlvindex?LINUX-390