Bug 1036841

Summary: [abrt] qemu-system-x86-1.4.2-9.fc19: Process /usr/bin/qemu-system-x86_64 was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Jacek Wielemborek <d33tah>
Component: qemuAssignee: Fedora Virtualization Maintainers <virt-maint>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: amit.shah, berrange, cfergeau, crobinso, dwmw2, itamar, pbonzini, rjones, scottt.tw, virt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:0577be452edf14e0447a8b21ab3126931f9114f2
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-04 23:10:29 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Jacek Wielemborek 2013-12-02 18:03:07 UTC 
Version-Release number of selected component:
qemu-system-x86-1.4.2-9.fc19

Additional info:
reporter:       libreport-2.1.7
backtrace_rating: 3
cmdline:        /usr/bin/qemu-system-x86_64 -machine accel=kvm -redir tcp:2249::22 -redir tcp:8049::80 -net nic -net user debian.img
executable:     /usr/bin/qemu-system-x86_64
kernel:         3.9.6-200.fc18.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (4 frames)
 #0 ??
 #1 ide_bus_reset
 #2 piix3_reset
 #3 qemu_system_reset
Comment 1 Jacek Wielemborek 2013-12-02 18:03:14 UTC 
Created attachment 831702 [details]
File: backtrace
Comment 2 Jacek Wielemborek 2013-12-02 18:03:20 UTC 
Created attachment 831703 [details]
File: cgroup
Comment 3 Jacek Wielemborek 2013-12-02 18:03:34 UTC 
Created attachment 831704 [details]
File: core_backtrace
Comment 4 Jacek Wielemborek 2013-12-02 18:03:41 UTC 
Created attachment 831705 [details]
File: dso_list
Comment 5 Jacek Wielemborek 2013-12-02 18:03:47 UTC 
Created attachment 831706 [details]
File: environ
Comment 6 Jacek Wielemborek 2013-12-02 18:03:54 UTC 
Created attachment 831707 [details]
File: exploitable
Comment 7 Jacek Wielemborek 2013-12-02 18:04:01 UTC 
Created attachment 831708 [details]
File: limits
Comment 8 Jacek Wielemborek 2013-12-02 18:04:07 UTC 
Created attachment 831709 [details]
File: maps
Comment 9 Jacek Wielemborek 2013-12-02 18:04:13 UTC 
Created attachment 831710 [details]
File: open_fds
Comment 10 Jacek Wielemborek 2013-12-02 18:04:20 UTC 
Created attachment 831711 [details]
File: proc_pid_status
Comment 11 Jacek Wielemborek 2013-12-02 18:04:26 UTC 
Created attachment 831712 [details]
File: var_log_messages
Comment 12 Cole Robinson 2013-12-04 23:10:29 UTC 
That backtrace isn't too useful, and there isn't much info besides a command line, so closing.

If you can reliably reproduce, please try to get a full backtrace and describe what you do to reproduce it, and reopen this bug.