Bug 973153 - [abrt] qemu-system-x86-1.4.2-2.fc19: qemu_memalign: Process /usr/bin/qemu-system-x86_64 was killed by signal 6 (SIGABRT)
Summary: [abrt] qemu-system-x86-1.4.2-2.fc19: qemu_memalign: Process /usr/bin/qemu-sys...
Alias: None
Product: Fedora
Classification: Fedora
Component: qemu
Version: 19
Hardware: x86_64
OS: Unspecified
Target Milestone: ---
Assignee: Fedora Virtualization Maintainers
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:aa5846b8d2b389d6b3e8127052a...
Depends On:
TreeView+ depends on / blocked
Reported: 2013-06-11 11:41 UTC by Arkady L. Shane
Modified: 2013-06-11 19:57 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2013-06-11 19:57:32 UTC
Type: ---

Attachments (Terms of Use)

Description Arkady L. Shane 2013-06-11 11:41:39 UTC
Version-Release number of selected component:

Additional info:
reporter:       libreport-2.1.4
backtrace_rating: 4
cmdline:        /usr/bin/qemu-system-x86_64 -machine accel=kvm -m 2048 -vga qxl -soundhw ac97 -cdrom '/home/ashejn/\xd0\x97\xd0\xb0\xd0\xb3\xd1\x80\xd1\x83\xd0\xb7\xd0\xba\xd0\xb8/ROSA.FRESH.GNOME.R1.x86_64.iso' -hda '/home/ashejn/\xd0\x97\xd0\xb0\xd0\xb3\xd1\x80\xd1\x83\xd0\xb7\xd0\xba\xd0\xb8/rosa.img' -boot d
crash_function: qemu_memalign
executable:     /usr/bin/qemu-system-x86_64
kernel:         3.9.4-301.fc19.x86_64
runlevel:       N 5
uid:            1706

Truncated backtrace:
Thread no. 1 (9 frames)
 #2 qemu_memalign at util/oslib-posix.c:97
 #3 qemu_vmalloc at util/oslib-posix.c:126
 #4 kvm_vmalloc at /usr/src/debug/qemu-1.4.2/kvm-all.c:1747
 #5 qemu_ram_alloc_from_ptr at /usr/src/debug/qemu-1.4.2/exec.c:1050
 #6 qemu_ram_alloc at /usr/src/debug/qemu-1.4.2/exec.c:1092
 #7 memory_region_init_ram at /usr/src/debug/qemu-1.4.2/memory.c:944
 #8 pc_memory_init at /usr/src/debug/qemu-1.4.2/hw/pc.c:929
 #9 pc_init1 at /usr/src/debug/qemu-1.4.2/hw/pc_piix.c:115
 #10 pc_init_pci at /usr/src/debug/qemu-1.4.2/hw/pc_piix.c:229

Potential duplicate: bug 906947

Comment 1 Cole Robinson 2013-06-11 19:40:24 UTC
Is this reproducible or just a random occurrence? Was there any stderr output from qemu that might give us a hint here?

Comment 2 Cole Robinson 2013-06-11 19:57:32 UTC
Actually I think this is just an issue when qemu can't allocate enough memory to meet the -m request.

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