On Monday, 09/23/2002 at 10:39 EST, Paul Dieffenbach <[EMAIL PROTECTED]> wrote: > Mark, > > Hopefully you saw my previous response to Jeff Davis. Yes, the guest is > logged off. We see no error messages on the VM console when this happens. > We are in the process of setting up RTM, but otherwise are not far enough > along yet to have other tools in place. I've been in touch with Velocity > and hope to begin a trial of their product next month. I should say we only > have 4 guests created so far and have ample memory allocated to the VM LPAR > - 6 GB. I of course was hoping this might be a known issue that someone > else had already encountered or that we were doing something incorrectly > just due to inexperience.
Paul, here's a set of events which are plausible (unlikely with 6GB and only 4 guests) 1. The system or I/O subsystem is under stress, things are getting slower and slower 2. Something take too long (e.g. I/O interrupts) and Linux gets upset and halts 3. Guest goes into CP READ, starting the default 15-minute "timebomb" 4. After 15 minutes, FORCED BY SYSTEM The only other case of FORCED BY SYSTEM I've seen is when a network connection to the virtual console (e.g. telnet) is broken unexpectedly, causing CP READ. I don't know of anything other than CP READ which will cause FORCED BY SYSTEM. The question is: How did the gueset it get into CP READ? Alan Altmark Sr. Software Engineer IBM z/VM Development
