Currently, the creation and debugging of Communication Manager virtual machine core images created by the VM kernel is not supported. If you have to create a Communication Manager virtual machine core images to debug, for example, a reproducible problem, use the following steps.
Procedure
Install the kexec-tools rpm that provides the functionality to generate core files, for example, on kernel panics. You can install the Virtual Machine kernel dump service from the Virtual Machine kernel dump service documentation Web link. You can follow the CLI instructions for easier navigation. You must note the following points:
The Virtual Machine kernel dump service documentation Web link describes changes to the GRUB tool, which for Communication Manager is lilo, that is /etc/lilo.conf. It states to add crashkernel=128M on the kernel entry line but actually the string to add is crashkernel=128M@16M. Execute the lilo command and reboot the virtual machine.
Execute the service kdump status command to ensure that the kdump rc script is setup and running.
Execute the following to ensure that a virtual machine kernel core can be created
echo 1 > /proc/sys/kernel/sysrq
echo c > /proc/sysrq-trigger
After the Communication Manager virtual machine is rebooted ensure the core image is written to the virtual machine disk space in the /var/crash/_date_/vmcore directory. Use the RedHat Crash Utility to debug the core images in the /var/crash/_date_/vmcore directory. See VMware generated core images on Communication Manager virtual machine images.
