I didn't say so, but it also happened before with 512M defined. As it turns out, the problem was related to the DISPLAY variable. I use PuTTY, which does X forwarding. I wasn't running an X server on my desktop when starting YaST. Normally, this just results in a error message, and YaST exits. For whatever reason, it was causing the kernel panic in this case. (Neale Ferguson noted off-list that the PSW indicated something in kernel space was taking a WAB (Wild Branch) into location 0.) Doing an "unset DISPLAY" then starting YaST seems to have corrected the problem.
Pretty bizarre that an X error could cause this. Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Kyle Smith Sent: Tuesday, August 01, 2006 2:26 PM To: [email protected] Subject: Re: SLES10 Abend During Install You'll want to up the storage for your guest to 512M. I've seen it panic fairly easily with less than that. Full reqs are listed in the preparation guide (docu/en/preparation.pdf). ks ---------------------------------------------------------------------- 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
