All excellent suggestions. Thank you all, extremely helpful.
Joe Joseph Vitale Technology Services Group Mainframe Operating Systems Pershing Plaza 95 Christopher Columbus Drive Floor 14 Jersey City, N.J. 07302 Work 201-395-1509 Cell 917-903-0102 -----Original Message----- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Marcy Cortes Sent: Tuesday, October 06, 2015 2:28 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: How to force crash dump from hung Red Hat guest I think it was worse than 30 minutes for 16G the last time I tried! And it is non-interruptible. If you are on a problem call, you may have people screaming at you to get their server back sooner and you have no control at that point. Best imho to make yourself a volume with zipl -d . You can attach that to whatever guest as needed and simply do from the console: #cp stop cpu all #cp store status #cp ipl xxxx It's very fast and always works. It’s a good practice to always have one ready. -----Original Message----- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Robert J Brenneman Sent: Tuesday, October 06, 2015 10:02 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] How to force crash dump from hung Red Hat guest from the guest's console issue #CP VMDUMP to trigger a CP managed dump of the virtual machine. This dumps to spool space and it shows up in the guest's rdr device. You can then 'vmur receive --convert <spoolid> /path/to/where/dump/goes' to import the vmcore to the Linux file system when you IPL after the dump completes. Make sure you have enough spool space to contain however much virtual memory the guest is defined with. Also make sure you have time - a VMDUMP of a 16 GB virtual machine can take on the order of 30 minutes - dumping to spool is slow but it will save your bacon when the kdump function does not work for whatever reason. http://www-01.ibm.com/support/knowledgecenter/linuxonibm/com.ibm.linux.z.lgdt/lgdt_c_intro.html On Tue, Oct 6, 2015 at 11:41 AM, Vitale, Joseph <joseph.vit...@bnymellon.com > wrote: > Hello, > > Running Red Hat 6.6 under zVM 6.3. I had a guest hang and unable to > issue linux commands to force a kernel crash dump( echo c > > /proc/sysrq-trigger ). > > Any suggestions how that can be accomplished? > > Thanks > Joe > > > Joseph Vitale > Technology Services Group > Mainframe Operating Systems > > Pershing Plaza > 95 Christopher Columbus Drive > Floor 14 > Jersey City, N.J. 07302 > Work 201-395-1509 > Cell 917-903-0102 > > > The information contained in this e-mail, and any attachment, is > confidential and is intended solely for the use of the intended recipient. > Access, copying or re-use of the e-mail or any attachment, or any > information contained therein, by any other person is not authorized. > If you are not the intended recipient please return the e-mail to the > sender and delete it from your computer. Although we attempt to sweep > e-mail and attachments for viruses, we do not guarantee that either > are virus-free and accept no liability for any damage sustained as a result > of viruses. > > Please refer to http://disclaimer.bnymellon.com/eu.htm for certain > disclosures relating to European legal entities. > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, send > email to lists...@vm.marist.edu with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > -- Jay Brenneman ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/ The information contained in this e-mail, and any attachment, is confidential and is intended solely for the use of the intended recipient. Access, copying or re-use of the e-mail or any attachment, or any information contained therein, by any other person is not authorized. If you are not the intended recipient please return the e-mail to the sender and delete it from your computer. Although we attempt to sweep e-mail and attachments for viruses, we do not guarantee that either are virus-free and accept no liability for any damage sustained as a result of viruses. Please refer to http://disclaimer.bnymellon.com/eu.htm for certain disclosures relating to European legal entities.
