Try
' set QIOASSIST off' on the Virtual Machine Profile.
I hope that help´s
----- Original Message -----
From: "Post, Mark K" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Tuesday, August 01, 2006 2:20 PM
Subject: SLES10 Abend During Install
I have a z/VM 4.4 64-bit guest on a z900 that I'm trying to install
SLES10 GA on. Things seem to go along fine, until I SSH in and start
YaST. At that point, I get a the following messages on my terminal,
followed by a kernel panic on the z/VM console:
# yast
*** Starting YaST2 ***
(-- fairly long pause ---)
*** Preparing SSH installation for reboot ***
*** NOTE: after reboot, you have to reconnect and call ***
*** /usr/lib/YaST2/startup/YaST2.ssh ***
illegal operation: 0001 [#1]
CPU: 0 Not tainted
Process init (pid: 1, task: 00000000007c1748, ksp: 00000000007c3ca0)
Krnl PSW : 0704200180000000 0000000000000002 (0x2)
Krnl GPRS: 0000000000000001 0000000000000000 0000000003cdb2a8
0000000000000085
00000000007c3cf0 0000000000000001 00000000010c6160
0000000000000001
0000000003cdb3c8 00000000000a3898 0000000003cdb3c8
0000000000000000
0000000000000085 0000000000446888 000000000025970c
00000000007c3b38
Krnl Code: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Call Trace:
([<0000000000259434>] mpage_writepages+0x23c/0xb40)
[<00000000001b07ca>] do_writepages+0x5a/0x74
[<0000000000256a8c>] sync_inodes+0x540/0x1204
[<00000000001fdad4>] sys_sync+0x30/0x84
[<000000000010f774>] sysc_noemu+0x10/0x16
[<00000200001464aa>] 0x200001464aa
<0>Kernel panic - not syncing: Attempted to kill init!
HCPGIR450W CP entered; disabled wait PSW 00020001 80000000 00000000
0014259E
Q CPLEVEL
z/VM Version 4 Release 4.0, service level 0403 (64-bit)
Generated at 11/19/04 15:43:15 CDT
IPL at 04/09/06 04:13:05 CDT
Q STOR
STORAGE = 256M
My network connections are via CTC to the z/VM TCP/IP SVM. (Which is no
longer officially supported in SLES, unfortunately. There's also a bug
in the installer regarding CTCs, but I doubt I'll be reporting the issue
because of that.)
Anyone have any ideas about this one? It looks like a S0C1 (illegal
opcode), but I don't know what might be causing it.
Mark Post
----------------------------------------------------------------------
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
