Bug 595765 - KVM VM panicked
KVM VM panicked
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel (Show other bugs)
5.5
x86_64 Linux
low Severity medium
: rc
: ---
Assigned To: Virtualization Maintenance
Red Hat Kernel QE team
:
Depends On:
Blocks: 562808
  Show dependency treegraph
 
Reported: 2010-05-25 10:59 EDT by Steve Reichard
Modified: 2012-07-16 18:22 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-07-16 18:22:15 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Steve Reichard 2010-05-25 10:59:53 EDT
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



How reproducible:

At this point, this has not reproduced.

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 David Howells 2010-05-25 12:33:03 EDT
(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,
> http://irish.lab.bos.redhat.com/pub/bz_data/<BZ######>/virt-viewer_sat-vm_crash.png
> , 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.)

Note You need to log in before you can comment on or make changes to this bug.