Bug 863385 - 'service libvirtd start' is causing kernel oops and reboot
'service libvirtd start' is causing kernel oops and reboot
Status: CLOSED CURRENTRELEASE
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel (Show other bugs)
6.4
Unspecified Unspecified
unspecified Severity high
: rc
: ---
Assigned To: Red Hat Kernel Manager
Red Hat Kernel QE team
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-10-05 06:15 EDT by Jaroslav Škarvada
Modified: 2012-11-19 03:22 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-11-19 03:22:05 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
oops (5.03 KB, text/plain)
2012-10-05 06:15 EDT, Jaroslav Škarvada
no flags Details
dmidecode (28.74 KB, text/plain)
2012-10-05 06:19 EDT, Jaroslav Škarvada
no flags Details
dmesg (54.86 KB, text/plain)
2012-10-05 06:19 EDT, Jaroslav Škarvada
no flags Details

  None (edit)
Description Jaroslav Škarvada 2012-10-05 06:15:13 EDT
Description of problem:
'service libvirtd start' is causing kernel oops and reboot

Version-Release number of selected component (if applicable):
libvirt-0.10.2-1.el6.x86_64
kernel-2.6.32-315.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1. service libvirtd start
  
Actual results:
Kernel oops and reboot.

Expected results:
No oops and no reboot.

Additional info:
Comment 1 Jaroslav Škarvada 2012-10-05 06:15:54 EDT
Created attachment 622076 [details]
oops

oops
Comment 2 Jaroslav Škarvada 2012-10-05 06:19:15 EDT
Created attachment 622086 [details]
dmidecode

dmidecode
Comment 3 Jaroslav Škarvada 2012-10-05 06:19:58 EDT
Created attachment 622087 [details]
dmesg

dmesg
Comment 4 Jaroslav Škarvada 2012-11-19 03:22:05 EST
I cannot see the problem with new packages:
libvirt-0.10.2-8.el6.x86_64
kernel-2.6.32-340.el6_867027.x86_64

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