Hmm, the other possibility (?) is that Sue is using an "LPAR" kernel, and not the one with VM support.
Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Rob van der Heij Sent: Wednesday, February 04, 2004 2:47 AM To: [EMAIL PROTECTED] Subject: Re: Ipl problem after instal on vm mdisk On Wed, 2004-02-04 at 08:08, Sue Sivets wrote: > I just finished installing Suse Linux on a VM mini disk (previous installs were > in standalone lpars). When I tried to ipl the system for the first time I > received the following message: > HCPGIR453W CP entered; program interrupt loop > Since I wasn't at all sure the ipl text really was written, I linked the new mini > disk to another linux guest and re-ran zipl. The system still doesn't ipl. > Has anyone run into something like this before? Does anyone have any ideas about > what I can or should do next? Could it be that the userid is in XC mode (Q SET) now, or maybe short of storage? If zipl did not write the IPL records you'd get different ones. One option could be that the contents of /boot changed after zipl and it now points the wrong way. You could make sure and start from the ramdisk system again, load the dasd driver and re-run zipl. If nothing else you could run TRACE I during IPL and see where it gets. Rob
