Description of problem:
In our environment we have a RHEL 5.5 host run a RHEL 5.5 VM. The VM is mostly used to run RHN Satellite 5.3.
At the time of the panic, no one was actively performing actions on either the system or VM, it happened over the weekend. People may have been logged in but idle.
The issue was noticed by not being able to log into the VM. Using the virt-viewer, this stack trace, http://irish.lab.bos.redhat.com/pub/bz_data/<BZ######>/virt-viewer_sat-vm_crash.png , was seen on the console.
On the host a virsh dump was performed and the memory file is in
http://irish.lab.bos.redhat.com/pub/bz_data/<BZ######>/sat_crash. The two kernels that were on the VM are also in this directory. I assume it was using the latest,but not sure if the sytstem had been restarted since the last update.
Version-Release number of selected component (if applicable):
Linux sat-vm.cloud.lab.eng.bos.redhat.com 2.6.18-194.3.1.el5 #1 SMP Sun May 2 04:17:42 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
At this point, this has not reproduced.
Steps to Reproduce:
(In reply to comment #0)
> The issue was noticed by not being able to log into the VM. Using the
> virt-viewer, this stack trace,
> , was seen on the console.
This BZ doesn't seem to be represented there.
There is one for bug 595765 which shows what you might be talking about.
Is there any way you can retrieve the panic message or at least the EIP value? It's impossible to say for certain which function actually panicked without that since there's certainly at least one obsolete function pointer on the stack.
(Note that the code in RHEL-5 is prior to my implementation of COW credentials.)