Bug 883596 - GNOME Boxes causes a kernel panic on Dell Inspiron 530n 64 bits with Intel Core2Quad
Summary: GNOME Boxes causes a kernel panic on Dell Inspiron 530n 64 bits with Intel Co...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 18
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Christophe Fergeau
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-04 23:18 UTC by Jean-François Fortin Tam
Modified: 2013-04-01 19:51 UTC (History)
12 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-04-01 19:51:58 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
photo (548.88 KB, image/jpeg)
2012-12-04 23:18 UTC, Jean-François Fortin Tam
no flags Details

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.


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