Bug 2229017

Created attachment 1981529 [details]
tar file of logs from f36 installation attempt

(In reply to Albert Stone from comment #1)
> Created attachment 1981529 [details]
> tar file of logs from f36 installation attempt

I'll attach f38 logs (or someone will) as soon as I can retrieve them.

Created attachment 1981671 [details]
tar file of logs from f38 installation attempt

For the record I can reproduce the issue when installing s390x rawhide ISO on a ppc64le host, but not for F-36 image. The full system emulation is used by people wanting access other platforms for development/debugging.

https://github.com/rhinstaller/anaconda/blob/master/data/dbus/anaconda-bus.conf#L115 is the location of the timeout definition

Not sure we want to change the default, but a way to override (eg. via some inst.foo parameter) it would be great.

a workaround could be using an updates image, please try adding inst.updates=http://fedora.danny.cz/s390/timeout.img to the kernel parameters when booting the installer ISO. The image contain an updated /usr/share/anaconda/dbus/anaconda-bus.conf file.

(In reply to Dan Horák from comment #6)
> a workaround could be using an updates image, please try adding
> inst.updates=http://fedora.danny.cz/s390/timeout.img to the kernel
> parameters when booting the installer ISO. The image contain an updated
> /usr/share/anaconda/dbus/anaconda-bus.conf file.

Forgive my ignorance here ... how does one do this?  Virt-manager is not providing access to a grub menu nor do I see anywhere to add it to boot options; do I need to extract the kernel and initrd from the ISO and then add the parameter so I can direct boot a kernel in virt-manager?  Or, just point me at a man page :).

Thanks.

Good question :-) And I am not sure there is an easy way with virt manager, but manually editing the XML definition before the installation start might allow it (there is a "review options" check box on the last screen of the wizard). Definitely it's possible when using virt-install (the command line tool) and its --extra-args.

something like: virt-install --name f38 --memory 4096 --vcpus 2 --disk size=10 --graphics none --location https://kojipkgs.fedoraproject.org/compose/38/latest-Fedora-38/compose/Everything/s390x/os/ --extra-args="inst.updates=http://fedora.danny.cz/s390/timeout.img"

it will need the proper "connection string" to your remote host

I believe direct boot with kernel/initrd extracted from the ISO (or downloaded) would be equivalent to what the virt-install is doing ...

(In reply to Dan Horák from comment #8)
> Good question :-) And I am not sure there is an easy way with virt manager,
> but manually editing the XML definition before the installation start might
> allow it (there is a "review options" check box on the last screen of the
> wizard). Definitely it's possible when using virt-install (the command line
> tool) and its --extra-args.
> 
> something like: virt-install --name f38 --memory 4096 --vcpus 2 --disk
> size=10 --graphics none --location
> https://kojipkgs.fedoraproject.org/compose/38/latest-Fedora-38/compose/
> Everything/s390x/os/
> --extra-args="inst.updates=http://fedora.danny.cz/s390/timeout.img"
> 
> it will need the proper "connection string" to your remote host

Confirmed.  The longer timeout lets the installer start properly.  Not
sure why it's so slow, but the workaround does work.

Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21.

Fedora Linux 38 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.