Timing was a poor choice of words with techies. I ment that the initial
stages of Sles installation doesn't use swap disks.
1. IPL from tape, cards, CD....whatever, no swap used.
2. Initial setup, where install media is, and some of Linux is loaded,
swap not used. A large RAM disk is defined (hence the need for more
than 128MB of real storage).
3. Specify language, timezone, dasd (with activating and formatting
dasd), specify packages to use, swap not used.
4. CD1 is loaded, swap not used.
5. Reboot and other CDs may be loaded, swap is used if defined.
This has nothing to do with any activity on your processor (VM or
otherwise, VM paging or other I/O)
Tom Duerbusch
THD Consulting
>>> [EMAIL PROTECTED] 03/28/05 4:34 PM >>>
Just so I am clear, you are saying if I do any VM swapping it causes
the
timing issue? My guests were defined at 512MB and I also tried 728MB.
I also can rule out linux swapping because a couple of times I tried
telneting into the installer after the network came up but before the
setup began, manually brought swap disks online to the installer and
it
still failed ..
This is a bit scary to me regarding SLES9 as it seems to me it just
shouldn't know or care what VM is doing under the covers, that's kinda
the
whole point. Since it would always seem to crash during some dasd
operation, format/partition/etc. then to me this would indicate that
the
timing issue you mention must be somewhere within the dasd drivers.
I think I will test out the adding/removing dynamic dasd to a running
machine fairly heavily before we move this over..
Thanks!
Jeremy
"Tom Duerbusch" <[EMAIL PROTECTED]>
03/28/2005 05:12 PM
To: <[EMAIL PROTECTED]>, <[email protected]>
cc:
Subject: Re: Sles9 Install Memory Issue
The problem is one of timing.
During the install, you don't use swap files. An incore RAM disk is
created in which SLES9 is laid down. Then that is IPL'ed and you go
into
yast to format drives, specify software, etc, and that is installed on
your dasd. When that IPL is done, then the swap disks are used.
I've gotten by with 512MB for installation when using ssh. But 768MB
seems to be needed if you use VNC.
Once installed, you can bring the partition down to 64MBs. Any
futher,
and SLES9 will start using your swap disk, just for booting. Anything
else you run would cause swapping also.
Tom Duerbusch
THD Consulting
>>> [EMAIL PROTECTED] 03/28/05 3:51 PM >>>
This is less a question than it is a description of a weird problem I
had
during SLES9 install just in case anyone else runs into it.
We have a "micro" lpar with z/VM 5.1 on it. This LPAR only has 128MB
of
memory, 64MB of xstore, one mod9 for swap. It's intended to be a
quarantine area that we can do new installs on before moving them over
to
the real test system.
I was trying to lay down sles9 minimal install and kept getting the
dreaded crash which contains these messages:
illegal operation: 0001 [#1]
CPU: 0 Not tainted
.
.
.
<debug data goes here>
.
.
>From the archives I found that the work around to this is to allocate
more
memory to the guest during install.
Here is what's interesting, I had already setup the guest with 512MB,
(I
went as high as 728) it's the ONLY guest running except the VM
services,
so there seems to be more than enough swap available to fulfill this
request. Even with that it STILL won't install. I tried every install
combination: NFS, FTP and SAMBA over VNC, X-Windows, SSH all with the
same
results, sometimes getting a bit farther than others but always
blowing
up.
So during a quiet time I swung the packs over to the test LPAR with
actual
real memory and sure enough first try everything installs just fine.
It seems to me that if there is enough virtual backing the request it
should have installed fine, albeit slowly, but that appears not to be
the
case.
No assistance is really required at this point from the list as I have
it
laid down, was able to swing it back over to the quarantine area and
it
works just fine over there, however I can reproduce the problem at
will
if
anyone wants me to try anything.
Thanks!
Jeremy
-----------------------------------
Jeremy Warren
Manager of Open Systems
KB Toy Stores
mailto:[EMAIL PROTECTED]@kbtoys.com
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390
or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390
or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
