Bug 883596

Summary: GNOME Boxes causes a kernel panic on Dell Inspiron 530n 64 bits with Intel Core2Quad
Product: [Fedora] Fedora Reporter: Jean-François Fortin Tam <nekohayo>
Component: kernelAssignee: Christophe Fergeau <cfergeau>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 18CC: amit.shah, berrange, cfergeau, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, marcandre.lureau, mtosatti, virt-maint, zeenix
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-04-01 19:51:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
photo none

Description Jean-François Fortin Tam 2012-12-04 23:18:31 UTC 
Created attachment 657815 [details]
photo

Simply by pressing "create" after choosing an ISO image for Windows XP SP3, Boxes instantly takes down my entire machine and throws me in front of a kernel panic. See the attached photo.

Hardware:
Core2 Quad Q9300 CPU
AMD Radeon HD 5450 GPU
5 GB of RAM
Comment 1 Jean-François Fortin Tam 2012-12-06 02:43:38 UTC 
And of course, retrying just now with the same ISO image in gnome boxes, it works without crashing my kernel...
Comment 2 Josh Boyer 2012-12-06 15:06:38 UTC 
The photo is a bit helpful, but it doesn't show the first oops so we can't really see what the actual issue is.

Can you add 'pause_on_oops=100' to your kernel cmdline and capture the first oops displayed if this happens again?
Comment 3 Amit Shah 2012-12-07 18:52:11 UTC 
Do you also have virtualbox / vmware / other hypervisor installed / running?
Comment 4 Jean-François Fortin Tam 2012-12-07 22:22:28 UTC 
Nope, there was only gnome-boxes on a clean install... not sure how I'd add the pause_on_oops=100 in a permanent way given that I can't reproduce this everytime/it only happened that once time and I immediately took a photo...
Comment 5 Josh Boyer 2013-04-01 19:51:58 UTC 
We'll close this out for now due to the one-time nature as described in comment #4.  If you are still having this problem with 3.8.x, please reopen.