From:Tom Duerbusch
Subject:Re: question about sleep setting for linux virtual server start
automatically
Plan on the worse case of each server needing to do a file system check. Uggg.
This is the primary reason we switched to the XFS
Thanks for all your suggestion which all helps me :)
From: Tom Duerbusch
To: IBMVM@LISTSERV.UARK.EDU
Date: 11/04/2009 11:37 AM
Subject:Re: question about sleep setting for linux virtual server
start automatically
Sent by:The IBM z/VM Operating System
I think the 15
Bringing up a Linux guest is a resource intensive process: Linux touches every
page of it’s memory allocation and does a lot of fairly dumb things trying to
figure out it’s environment. If you have a lot of guests all trying to come up
at once, you will likely overtax the capability of CP to ser
I think the 15 seconds comes from the CMS server side. CMS servers come up
much faster than a full operating system (such as Linux).
I don't have much delay between each Linux startup, however, I do start the
production servers such as NFS first, then delay 5 minutes (sometimes a file
system c
Actually - I shouldn't say 'they will all come up eventually' so
casually things can go wrong if processing bogs down too much --
things time out, device waits occur, etc... So spreading out the Linux
guest startup might help if you're running into such issues.
Scott
On Wed, Nov 4, 2009
Probably trying to spread the starting of guests a little so it doesn't
overwhelm the system at zVM IPL time. Opinions vary on what the spread
should be if one is used... 3 every 15 secs - 10 every 1 minute - etc.
I've seen several installations with over 100+ Linux guests not use any
delay -- an
What is the reasonable setting for sleep time after issue xautolog server?
On the planning and Administration "Steps for automatically starting linux
virtual servers and other virtal machines" say:
1. After every third XAUTOLOG statement that starts a Linux virtual
server, add this stateme
