Bug 500185 - Segfault while running Fedora 11 Preview guest
Summary: Segfault while running Fedora 11 Preview guest
Keywords:
Status: CLOSED DUPLICATE of bug 497170
Alias: None
Product: Fedora
Classification: Fedora
Component: kvm
Version: rawhide
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Glauber Costa
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-05-11 15:03 UTC by Frank Arnold
Modified: 2009-05-11 17:41 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-05-11 17:41:14 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
GDB backtrace (5.05 KB, text/plain)
2009-05-11 15:03 UTC, Frank Arnold
no flags Details

Description Frank Arnold 2009-05-11 15:03:08 UTC
Created attachment 343465 [details]
GDB backtrace

Description of problem:
I get a segfault while running a 32-bit non-PAE Fedora 11 Preview guest on a Fedora 11 Preview host. The guest is running CTCS stress test. I was able to reproduce it 3 times. It takes about 2 hours until the guest process dies.

Version-Release number of selected component (if applicable):
kernel-2.6.29.1-102.fc11.x86_64
qemu-common-0.10-16.fc11.x86_64
qemu-debuginfo-0.10-16.fc11.x86_64
qemu-kvm-0.10-16.fc11.x86_64
qemu-kvm-tools-0.10-16.fc11.x86_64
qemu-system-x86-0.10-16.fc11.x86_64

Guest flags:
-name 002-CTCS -k de -monitor pty -vnc :1 -usbdevice tablet -m 1280 -smp 3 -hda /xen/images/fedora_11_preview_32b_qcow.img -hdb /xen/images/002.img -serial file:/tmp/guest2.fifo -net nic,model=e1000 -net tap,ifname=tap1

How reproducible:
Takes about 2 hours to reproduce.

Additional info:
Just an unqualified guess, but it's probably this issue...
http://git.kernel.org/?p=virt/kvm/qemu-kvm.git;a=commit;h=7403b14eeb4670d54497284b110ca3e3be4a99a4

Comment 1 Mark McLoughlin 2009-05-11 17:41:14 UTC
Thanks Frank, this is a dup of bug #497170

We'll either cherry-pick the fix into a qemu update soon, or if upstream releases 0.10.3 we'll jump to that

*** This bug has been marked as a duplicate of bug 497170 ***


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