Hi Willem,

The SLES 11 VM is a guest on a VMware host running ESXi 5.0.0, 623860.

SLES 11 SP2 64-bit. The ISO I used to install it was from the Novell downloads, and not VMware-specific.

Code:
myhost:~ # uname -a
Linux goat 3.0.13-0.27-default #1 SMP Wed Feb 15 13:33:49 UTC 2012 (d73692b) x86_64 x86_64 x86_64 GNU/Linux
Actually, the server was installed fresh with SLES 11 SP1, then an in-place upgrade to SP2 was done via Yast > Patch CD Upgrade. Here are my boot options:


Code:
myhost:~ # cat /boot/grub/menu.lst
# Modified by YaST2. Last modification on Wed Feb 29 11:31:23 EST 2012
default 0
timeout 8
##YaST - generic_mbr
gfxmenu (hd0,0)/boot/message
##YaST - activate

###Don't change this comment - YaST2 identifier: Original name: linux###
title SUSE Linux Enterprise Server 11 SP2 - 3.0.13-0.27 (default)
    root (hd0,0)
    kernel /boot/vmlinuz-3.0.13-0.27-default root=/dev/sda1 insmod=qla4xxx resume=/dev/sdb1 splash=silent crashkernel=256M-:128M showopts
    initrd /boot/initrd-3.0.13-0.27-default

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- SUSE Linux Enterprise Server 11 SP2 - 3.0.13-0.27
    root (hd0,0)
    kernel /boot/vmlinuz-3.0.13-0.27-default root=/dev/sda1 showopts ide=nodma apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe
    initrd /boot/initrd-3.0.13-0.27-default

###Don't change this comment - YaST2 identifier: Original name: linux###
title Trace -- SUSE Linux Enterprise Server 11 SP2 - 3.0.13-0.27
    root (hd0,0)
    kernel /boot/vmlinuz-3.0.13-0.27-trace root=/dev/sda1 insmod=qla4xxx resume=/dev/sdb1 splash=silent crashkernel=256M-:128M showopts
    initrd /boot/initrd-3.0.13-0.27-trace

###Don't change this comment - YaST2 identifier: Original name: floppy###
title Floppy
    rootnoverify (fd0)
    chainloader +1
This VM is used as a testing ground for proposed software in our SLES 11 environment, but it is currently not running any "extra" software. With that said, I've seen two other VMs crash that are actively used by our developers, then this same issue occurs when attempting to do a dump via Magic SysRq. The other two VMs run OpenLDAP and Shibboleth, but nothing else.