* RHEL5.3-Server-20081020.1 s390x * regression from 5.2 * Anaconda / Arch / Installation using LPAR (native) account * anaconda-11.1.2.145-1 , kernel-2.6.18-120.el5.s390x During installation, a system call error using vnc occurs and the install aborts: > The VNC server is now running. > Please connect to mistymarie.z900.redhat.com:1 to begin the install... > Press <enter> for a shell > Starting graphical installation... > pcilib: Cannot open /proc/bus/pci > lspci: Cannot find any working access method. > Traceback (most recent call last): > File "/usr/bin/anaconda", line 893, in ? > runVNC(vncpassword, vncconnecthost, vncconnectport, doStartupX11Actions) > File "/usr/bin/anaconda", line 405, in runVNC > sys.stdin.readline() > IOError: [Errno 4] Interrupted system call > The application 'anaconda' lost its connection to the display :1.0; > most likely the X server was shut down or you killed/destroyed > the application. > Connection to mistymarie.z900.redhat.com closed. The error has occurred the first time testing lpar installations on s390x; the error does not occur for the same installation using z/VM guests, I will try to reproduce the error again to see if it is consistent.
Created attachment 321218 [details] updates.img to test with Please test with the attached updates.img
Created attachment 321224 [details] updates.img to test with Actually, try this one instead.
What I expect is happening here is that vncserver is dying and we're getting a SIGCHILD while we're waiting for the command line input. If so, the attached image will probably fix the traceback, but you won't be able to connect to vnc afterwards.
We tried reproduce this bug with Brock but we are not successful. So this doesn't look like beta blocker candidate for me.
I'll re-open this issue if I can reliably reproduce it ...