| Summary: | Kernel crash message comes during installation in KVM/VirtualBox | ||
|---|---|---|---|
| Product: | [Retired] GlusterSP | Reporter: | Balamurugan Arumugam <bala> |
| Component: | core | Assignee: | Harshavardhana <fharshav> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | unspecified | CC: | cww, fharshav, platform, shireesh, webteam |
| Target Milestone: | 3.2 | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Balamurugan Arumugam
2010-02-27 20:58:37 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. 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. Is it possible to fix virtio driver in Platform? 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. |