On Tue, 2 Dec 2025 09:48:50 -0500 Stephen Gallagher <[email protected]> wrote:
> On Tue, Dec 2, 2025 at 9:25 AM Dan Horák <[email protected]> wrote: > > > > On Tue, 2 Dec 2025 09:03:51 -0500 > > Stephen Gallagher <[email protected]> wrote: > > > > > On Tue, Dec 2, 2025 at 3:20 AM Dan Horák <[email protected]> wrote: > > > > > > > > On Mon, 1 Dec 2025 20:40:29 -0500 > > > > Stephen Gallagher <[email protected]> wrote: > > > > > > > > > On Wed, Aug 13, 2025 at 3:19 AM Marián Konček <[email protected]> > > > > > wrote: > > > > > > > > > > > > When I run `podman run --arch s390x --rm -it fedora:rawhide` as > > > > > > well as > > > > > > `mock -r fedora-rawhide-s390x --shell`, the shell prompt is missing > > > > > > but > > > > > > the shell is still working. > > > > > > > > > > > > On F41 shell looks correct. > > > > > > > > > > > > This seems like a bug somewhere in the container. > > > > > > > > > > > > > > > > Just wanted to bring this back up. It appears that something is broken > > > > > on the fedora:43-s390x and fedora:44-s390x containers, but > > > > > fedora:42-s390x works just fine. > > > > > > > > > > I'm trying to debug an issue on one of my projects that is appearing > > > > > only on s390x and it's certainly not easy when the shell is broken :( > > > > > > > > > > I think it's related to the TTY handling, because it doesn't matter > > > > > what shell is in use. > > > > > > > > hmm, I wonder if it could be related to the termios changes in glibc > > > > 2.42 that landed in F-43. But there have been reports about apps > > > > accessing serial ports being broken so far. There is an issue with > > > > screen (not echoing typed text or similar) that I still need to look at, > > > > but that came with the rebase to 5.0 in F-42 I believe. > > > > > > > > Stephen, do you have more details? Because on a F-42 host I am getting > > > > a working shell prompt when running > > > > "podman run --rm -it fedora:43-s390x" (same with fedora:44-s390x) > > > > > > > > > > > > > Hmm, I suppose it's possible that the host might matter as well. I'm > > > running podman-5.7.0-1.fc43.x86_64 and the following commands (the > > > `ls` is typed in by me and followed by <enter>`): > > > > ah, so it's cross-arch (non-native) use case as the original report. I > > have tried that natively. > > > > I have rechecked your > > podman run --rm --tty --interactive fedora:43-s390x /usr/bin/bash > > running from Rawhide/s390x and it works as expected. So it's an > > emulation issue (incorrect parameter translation?) most likely ... > > If it was an emulation issue, I'd expect the fedora:42-s390x issue to > be unusable as well, but it's perfectly fine and I was able to use > that image to debug and fix my issue. AFAIK the cross-arch emulation uses user-mode qemu that does translate syscalls between the "guest" and the "host" systems, which means endianess changes, translating parameters, etc. needs to happen. My theory is that something changed in F-43+ and qemu needs to adapt to that. Unless it's something like unknown $TERM or such. What is needed except having qemu-user-static-s390x installed to successfully run the podman command? It just hangs on any of my non-s390x systems (x86_64, aarch64, ppc64le). > > BTW s390x systems are easily available from (internal) Testing Farm. > > Your definition of "easily" and mine may differ :) > > I have no idea where to find documentation on how to reserve an > instance where I can compile and debug an upstream project on s390x in > Testing Farm. My stabs in the dark found naught but empty air. It was > far easier for me to just emulate it (slowly). that's probably for someone else to answer, but you can run testing-farm reserve --arch s390x and after a while you will get a shell prompt of a s390x system Dan -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
