Bug 500185

Summary: Segfault while running Fedora 11 Preview guest
Product: [Fedora] Fedora Reporter: Frank Arnold <frank.arnold>
Component: kvmAssignee: Glauber Costa <gcosta>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: berrange, clalance, ehabkost, gcosta, markmc, quintela, virt-maint
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: 2009-05-11 17:41:14 UTC Type: ---
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
GDB backtrace none

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 ***