Bug 762420 (GLUSTER-688) - Kernel crash message comes during installation in KVM/VirtualBox
Summary: Kernel crash message comes during installation in KVM/VirtualBox
Keywords:
Status: CLOSED WONTFIX
Alias: GLUSTER-688
Product: GlusterSP
Classification: Retired
Component: core
Version: unspecified
Hardware: x86_64
OS: Linux
low
low
Target Milestone: 3.2
Assignee: Harshavardhana
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-27 20:58 UTC by Balamurugan Arumugam
Modified: 2015-03-23 01:03 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Balamurugan Arumugam 2010-02-27 20:58:37 UTC 
Platform installation shows kernel crash popup with tux logo as guest OS in KVM/VirtualBox.  However it does not affect installation or functionality.
Comment 1 Harshavardhana 2010-02-28 05:55:42 UTC 
Can you post the kernel backtrace?. Let me see if its fixed. 

This might come due to "virtio" drivers giving backtrace. There is a daemon called kerneloops which is default enabled if there is a backtrace it shows up so that the users can provide the output.
Comment 2 Harshavardhana 2010-03-11 07:38:52 UTC 
This backtrace results from bug in "virtio" drivers from linux kernel. Kernel oops daemon we don't want to disable it as rather in future if we get kernel backtrace from backend filesystem there is an easy way to collect it.
Comment 3 Balamurugan Arumugam 2010-03-11 14:29:15 UTC 
Is it possible to fix virtio driver in Platform?
Comment 4 Harshavardhana 2010-03-31 22:09:43 UTC 
Its not possible at this point of time to look at virtIO drivers as there are no hard lined customer requirements or goals for it.
Note You need to log in before you can comment on or make changes to this bug.