On Sat, 19 Mar 2011 23:10:16 -0300 Mauro Souza <thoriu...@gmail.com> wrote:
> I saw this problem some time ago with an Oracle RAC guest. It haven't set > the CP SET RUN ON, and as soon as the client issued some #CP Q SOMETHING, > the server froze down, and linux rebooted. Looks like Oracle RAC have some > kind of watchdog, and as CP MODE stops running Linux kernel for a little > moment, the watchdog thinks the system froze down, and reboots the system. > Setting RUN ON solved the problem. > You can try this, it won't hurt, and I think RUN ON should be the default. There is the important hint: if you have Oracle RAC and the watchdog is running the z/VM guest may not stop for longer periods of time. My guts feeling is that the large output of the #CP Q <xyz> command stopped the linux guest for too long. Once the output completed the guest continued and the Oracle watchdog did what it is programmed to do: reboot. -- blue skies, Martin. "Reality continues to ruin my life." - Calvin. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
