Bug 604014 - Whoops running in RHEL-6 kvm
Summary: Whoops running in RHEL-6 kvm
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel
Version: 5.7
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Virtualization Maintenance
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks: 562808
TreeView+ depends on / blocked
 
Reported: 2010-06-15 07:32 UTC by Matěj Cepl
Modified: 2013-02-28 12:08 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-28 12:08:41 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
screenshot of the error message (10.15 KB, image/png)
2010-06-15 07:32 UTC, Matěj Cepl 		no flags Details
/var/log/messages from the guest machine (RHEL-5) (92.29 KB, text/plain)
2010-06-15 07:33 UTC, Matěj Cepl 		no flags Details
/var/log/messages from the host machine (RHEL-6) (11.35 MB, text/plain)
2010-06-15 07:37 UTC, Matěj Cepl 		no flags Details
View All

Description Matěj Cepl 2010-06-15 07:32:14 UTC 
Created attachment 424058 [details]
screenshot of the error message

Description of problem:
When running RHEL-5 hosted in the RHEL-6 kvm I get from time to time (after couple of hours) whole guest crashes and i get attached whoops in virt-viewer

Version-Release number of selected component (if applicable):
guest: kernel 2.6.18-194.3.1.el5.i386
host: kernel 2.6.32-33.el6.x86_64

How reproducible:
happened twice in two days

Steps to Reproduce:
1.see above
2.
3.
  
Actual results:
crash and guest machine gone

Expected results:
RHEL running stable as rock

Additional info:
Comment 1 Matěj Cepl 2010-06-15 07:33:00 UTC 
Created attachment 424059 [details]
/var/log/messages from the guest machine (RHEL-5)
Comment 2 Matěj Cepl 2010-06-15 07:37:37 UTC 
Created attachment 424060 [details]
/var/log/messages from the host machine (RHEL-6)
Comment 3 Ronen Hod 2013-02-28 12:08:41 UTC 
Since we survived it so far, we can probably survive without fixing it in 5.10.
Closing.
Note You need to log in before you can comment on or make changes to this bug.