We are running z/VM 5.3 which is a 64-bit system. Plus, if I re-ipl the guest machine it's OK.
From: "Riedel, Alexander" <alexander.rie...@f-i-ts.de> To: IBMVM@LISTSERV.UARK.EDU Date: 06/28/2010 08:07 AM Subject: Re: PSW 000A0000 00000100 Sent by: The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU> It seems, that a 64bit kernel was ipled in an 31 bit system. Because the PSW is a 31-Bit PSW but SLES_10 is only available as a 64bit version. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Karl Kingston Sent: Monday, June 28, 2010 1:49 PM To: IBMVM@LISTSERV.UARK.EDU Subject: PSW 000A0000 00000100 Got a call from one of our operators over the weekend. Apparently one of our linux machines failed to start. So, looking at the log, I see the guest machine went into a disabled wait state. 00: zIPL v1.6.0 interactive boot menu 00: 00: 0. default (SLES_10_SP1) 00: 00: 1. SLES_10_SP1 00: 2. SLES_10_SP1_2 00: 3. ipl 00: 00: Note: VM users please use '#cp vi vmsg <number> <kernel-parameters>' 00: 00: Please choose (default will boot in 10 seconds): 00: Booting default (SLES_10_SP1)... 00: HCPGIR450W CP entered; disabled wait PSW 000A0000 00000100 I've been able to IPL the guest machine into Linux with no issues. Nothing I know of has been changed. I'm seeing a lot of messages related to the 000A0000 but none for 00000100. What's going on? Is the linux guest somehow getting corrupted? Do I need to run a zipl to rebuild the boot record information? Thanks
