We are running in an LPAR in production. Actually soon to be TWO LPARS. You
are not alone. We have a few unique issues running in LPAR mode.
|---------+---------------------------->
| | David Boyes |
| | <[EMAIL PROTECTED]|
| | e.net> |
| | Sent by: Linux on|
| | 390 Port |
| | <[EMAIL PROTECTED]|
| | IST.EDU> |
| | |
| | |
| | 09/09/2003 11:12 |
| | AM |
| | Please respond to|
| | Linux on 390 Port|
| | |
|---------+---------------------------->
>------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| Subject: Re: size of distributions (redux) - "The button"
|
>------------------------------------------------------------------------------------------------------------------------------|
> All my systems are built to run under VM or MVS w/o
> change. I do have the extint module in so that I can
> shut them down cleanly under VM, so that is not a
> problem. [...]
> However, if anyone uses the HMC reset button or IPL
> button or activate/deactivate button on the HMC, the
> LPAR Linuxes often are damaged.
>
Shutting down an LPAR generates the same architectural signal as a VM
SIGNAL
SHUTDOWN command (in fact, the hardware "feature" is what the command
emulates). You may want to check that the use of the external signal trap
is
enabled in both your configurations -- it should work in both, and that's
at
least one more dumb human trick that you can try to prevent.
> I starting to believe that we may be the only shop in
> the world running Linux under an LPAR!
You're the only one I know of who does so in production (and is willing to
admit it). There are undoubtedly good reasons to do it, but it does
introduce a more than fair amount of inconvenience.
-- db
