The guest may have been stuck in the Eligible list, that is, CP judged there is not enough memory available to let it run, CP wants to protect the system from excessive paging (try #CP IND Q, and look for E1, E2 and E3 values). You could have issued SET QUICKDSP LX004 ON, to tell CP that this can can run if it wants to. Beware however, giving too many guests this option may lead to thrashing, or other guests that get locked. I would have tried to see if it made the guest resurrect, if yes, you'd then know one has to take a good look at tuning parameters of the whole system. You could have taken a SNAPDUMP, and call the support center to have them look. A SNAPDUMP is non-disruptive, i.e. VM is not restarted, it will however slow the system down while the dump is being taken.
2008/8/7 Rempel, Horst <[EMAIL PROTECTED]>: > Hello, > one of our Linux sles9 SP4 DB2 databaseservers running under z/VM 5.3.0 > RSU0801 felt yesterday afternoon in a kind of coma. > > The linux stopped running. The putty-session got an timeout. I was no longer > able to ping. > The processor for this lpar was only 20% busy for other linux guests at this > time. > After that I tried to logon directly to the green screen. But I only got a > black screen with LOGON LX004 at the top. > The ind user lx004 shows no I/Os, no cpu consumtion. The performance toolkit > displayed only zeros for this LX004. > > After force/xautolog LX004 everything worked fine again. > Looking in the linux logs gave no hint what lead to the coma situation. > There is enough space free in the filesystems. > I have no idea what happened yesterday. > Has anybody an idea ? What can I do if the situation come back again ? > > This mail is crossposted to [EMAIL PROTECTED] and > [email protected] > > kind regards > Horst Rempel > > -- Kris Buelens, IBM Belgium, VM customer support
