> We're trying to research an issue with our kickstarting that cropped up in > RHEL6.4 (worked perfectly in RHEL6.2). RedHat support has asked us to > wait till the kickstart fails then issue "CNTL+ALT+F1" to get into "pdb" mode > so they can debug the anaconda stuff, but since we boot in z/VM, the > terminal doesn't appear to translate those keys correctly--at least, I issue > them and nothing happens.
Call RH back and insist on talking to someone who can understand "This is not an Intel system. Those keys don't exist on System z". > Does anyone know how to send those to the > host operating system through a tn3270e console? Or know of a different > way that we could get an ascii-based terminal for the automated kickstart if > needed? When I ssh into the guest at the failure time, I can hop on as root > but I'm not "breaking into" the install process--I can't enter anything that'd > change the flow of the install. > > Really hoping someone on this forum might have an idea, since IBM won't > respond (not a "zVM issue", apparently, that their console doesn't work) and > RedHat doesn't seem to know... The only way you could get an ASCII console that early in the process would be from the HMC, and it's still not going to help you. Try adding the "cmdline" option to the kickstart parm line. That will take you through the install line by line, which should help you find the problem. If this is 6.4, there are known bugs in kickstart. Have them search for "kickstart RHEL6.4" in their issue tracker. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] 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/
