= Test procedure =

The procedure starts after recovery of the VM snapshot, on the running VM.

== RHEL5 : crashdc ==

1) Prepare the environment

   1. Get the crashdc bits on the server
   2. # chmod 750 /usr/bin/*crashdc*
   3. # mv /etc/sysconfig/crashdc.rhel5 /etc/sysconfig/crashdc
   4. # mkdir /var/crash/scripts
   5. # uncomment kdump_post /var/crash/scripts/kdump-post.sh in /etc/kdump.conf
   6. # ln -s /usr/bin/run-crashdc-rhel5.sh /var/crash/scripts/kdump-post.sh 

2) Execute the test

# echo c > /proc/sysrq-trigger
crashdc.localdomain login: SysRq : Trigger a crashdump
Memory for crash kernel (0x0 to 0x0) notwithin permissible range
PCI: BIOS Bug: MCFG area at e0000000 is not E820-reserved
PCI: Not using MMCONFIG.
Mounting proc filesystem
Mounting sysfs filesystem
Creating /dev
Creating initial device nodes
...
Starting VMware Tools services in the virtual machine:
   Switching to guest configuration:[  OK  ]
   Guest memory manager:[  OK  ]
   Guest vmxnet fast network device:[  OK  ]
   VM communication interface:[  OK  ]
   VM communication interface socket family:[  OK  ]
   Blocking file system:[  OK  ]
   Guest operating system daemon:[  OK  ]
   Virtual Printing daemon:[  OK  ]
[  OK  ]
File /var/crash/2009-10-09-14:25/crash-data-200910091426.txt has been generated
INIT: Switching to runlevel: 6
INIT: Sending processes the TERM signal


== SLES10 : crashdcSLES10 ==

1) Prepare the environment

   1. Get the crashdc bits on the server
   2. # chmod 750 /usr/bin/*crashdc*
   3. # mv /etc/sysconfig/crashdc.sles10 /etc/sysconfig/crashdc
   4. # Modify /etc/sysconfig/kdump' 

KDUMP_TRANSFER="/usr/bin/run-crashdc-sles10.sh"

   1. Reboot the server with the crashkernel= parameter to 128M@16M 

2) Execute the test

# echo c > /proc/sysrq-trigger
SysRq : Trigger a crashdump
Linux version 2.6.16.60-0.21-kdump (geeko@buildhost) (gcc version 4.1.2 20070115 (SUSE Linux)) #1 Tue May 6 12:41:02 UTC 2008
BIOS-provided physical RAM map:
...
Master Resource Control: previous runlevel: N, switching to runlevel: 1
|##-------------------------------------|      23 MB of 383 MB (6.2%)
...
|########################################|     383 MB of 383 MB (100.0%)
done
File /var/log/dump/2009-10-09-15:57/crash-data-200910091558.txt has been generated
generated a crash-data file to /var/log/dump/2009-10-09-15:57
done
INIT: Switching to runlevel: 6
INIT: Sending processes the TERM signal


== SLES11 : crashdcSLES11 ==

1) Prepare the environment

   1. Get the crashdc bits on the server
   2. # chmod 750 /usr/bin/*crashdc*
   3. # mv /etc/sysconfig/crashdc.sles11 /etc/sysconfig/crashdc
   4. # Modify /etc/sysconfig/kdump' 

KDUMP_REQUIRED_PROGRAMS="/etc/sysconfig/crashdc /bin/basename /usr/bin/strings /bin/echo /usr/bin/crash /usr/bin/crashdc /usr/bin/run-crashdc-sles11.sh /etc/rc.status /bin/logger /usr/bin/gdb /lib/libpthread.so.0 /lib/libthread_db.so.1"
KDUMP_POSTSCRIPT="/usr/bin/run-crashdc-sles11.sh"

   1. service boot.kdump restart
   2. Reboot the server with the crashkernel= parameter to 256M-:128M@16M 

2) Execute the test

# echo c > /proc/sysrq-trigger