I've seen it on our VM 5.1 systems, but it works correctly on 5.2. I don't know if it is Linux or VM problem, but I figured out a workaround. Here is the long explanation I sent to a co-worker. (and which I had intended to post here but hadn't gotten to it yet!)
S390 linux has always had 2 kernel parameters, "vmhalt" and "vmpoff" that can specify a CP command to issue after a halt, or a halt with poweroff. But on the shutdown command, I see only "halt" and "reboot" options, nothing about a poweroff. But actually, all the shutdown command does with the -h or -r options is switch to runlevel 0 (halt) or 6 (reboot), after sending messages and maybe starting a timer. Looking in the /etc/init.d/rc0.d or /etc/init.d/rc6.d runlevel directories, there is 1 script which runs the /etc/init.d/halt script as either "halt" or "reboot". In that script, a halt runs the command "halt -p" (halt with poweroff) at the end (with other options), and a reboot runs "reboot". As a test, I removed the -p and did a shutdown. Instead of the final message being "poweroff", it said "system halted". (A ha!) Next, I changed the kernel parameters in zipl.conf to have "vmhalt=IPL" in the string (and nothing for vmpoff) and ran zipl. I shut down (with halt), IPLed to make this change active, then tried a reboot. This time, when it said "system halted" it then did an IPL! So, the work around fix for LPARs that need it, is to add "vmhalt=IPL" to zipl.conf (and run zipl), and change /etc/init.d/halt to run "halt" instead of "reboot" when a reboot is requested. And then it reboots like you'd expect! (And specifying a command of just "IPL" works because this is documented to IPL the last device IPLed.) On 1/31/06, Lee Stewart <[EMAIL PROTECTED]> wrote: > Hi... > > It seems like (aka: I haven't had the opportunity to definitively prove > it) after I've upgraded SLES9 systems to SP3 that reboot (or init 6, or > shutdown -r now) all shutdown cleanly, but don't restart. From the 3270 > console these are the last messages: > > Please stand by while rebooting the system... > md: stopping all md devices. > md: md0 switched to read-only mode. > Restarting system. > > The virtual machine does seem to burn some cycles after, but it never > restarts until you manually re-IPL it. > > Has anyone else seen this? Anyone know of a fix? > Thanks, > Lee > > -- > > Lee Stewart, Senior SE > Sirius Enterprise Systems Group > Phone: (303) 798-2954 > Fax: (720) 228-2321 > [EMAIL PROTECTED] > www.siriuscom.com > > ---------------------------------------------------------------------- > 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 > -- Bruce Hayden IBM Global Services zSeries Linux Endicott, NY ---------------------------------------------------------------------- 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
