qemu-system-x86_64 crashed with SIGABRT

Bug #959964 reported by Mateusz Marzantowicz
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
qemu-kvm (Ubuntu)
Fix Released
Medium
Unassigned
whoopsie-daisy (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

This bug happened after opening Virtual Manager window. After seeing/reporting this bug, everything works fine.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: qemu-kvm 1.0+noroms-0ubuntu8
ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11
Uname: Linux 3.2.0-19-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Mon Mar 19 00:50:49 2012
ExecutablePath: /usr/bin/qemu-system-x86_64
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
KvmCmdLine:
 UID PID PPID C SZ RSS PSR STIME TTY TIME CMD
 114 2430 1 6 880903 160336 7 08:04 ? 00:00:10 /usr/bin/kvm -S -M pc-0.14 -cpu core2duo,+lahf_lm,+rdtscp,+aes,+popcnt,+x2apic,+sse4.2,+sse4.1,+xtpr,+cx16,+tm2,+est,+vmx,+ds_cpl,+pbe,+tm,+ht,+ss,+acpi,+ds -enable-kvm -m 512 -smp 1,sockets=1,cores=1,threads=1 -name Web -uuid 323eff9b-f63d-8092-9aac-55be2679a9ca -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/Web.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-shutdown -drive file=/dev/VgVirt/Web,if=none,id=drive-virtio-disk0,format=raw -device virtio-blk-pci,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=16,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:db:e7:42,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -usb -device usb-tablet,id=input0 -vnc 127.0.0.1:0 -vga cirrus -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6
 114 2614 1 6 1241431 179516 3 08:04 ? 00:00:10 /usr/bin/kvm -S -M pc-0.14 -enable-kvm -m 512 -smp 1,sockets=1,cores=1,threads=1 -name ztp-www -uuid 81d5dd82-07ab-f7dc-fa47-2e4272904ff0 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/ztp-www.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-shutdown -drive file=/srv/vm-images/www.img,if=none,id=drive-virtio-disk0,format=qcow2 -device virtio-blk-pci,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=16,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:75:44:79,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -usb -device usb-tablet,id=input0 -vnc 127.0.0.1:1 -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5
 114 2679 1 13 382191 539328 7 08:04 ? 00:00:21 /usr/bin/kvm -S -M pc-0.14 -cpu core2duo,+lahf_lm,+rdtscp,+aes,+popcnt,+x2apic,+sse4.2,+sse4.1,+xtpr,+cx16,+tm2,+est,+vmx,+ds_cpl,+pbe,+tm,+ht,+ss,+acpi,+ds -enable-kvm -m 512 -smp 1,sockets=1,cores=1,threads=1 -name Mail -uuid 6aea80e8-1524-9c33-dfa8-2c3fed9c3a98 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/Mail.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-shutdown -drive file=/dev/VgVirt/Mail,if=none,id=drive-virtio-disk0,format=raw -device virtio-blk-pci,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=16,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:90:9b:a6,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -usb -device usb-tablet,id=input0 -vnc 127.0.0.1:2 -vga cirrus -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6
MachineType: Dell Inc. XPS 8300
ProcCmdline: /usr/bin/kvm -S -M pc-0.14 -enable-kvm -m 1024 -smp 1,sockets=1,cores=1,threads=1 -name Windows-8 -uuid 426dbc77-f25f-23c9-cccc-3e58dbd79473 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/Windows-8.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-shutdown -drive file=/dev/VgVirt/Windows-8,if=none,id=drive-ide0-0-0,format=raw -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -drive if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=21,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:61:04:7c,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -usb -device usb-tablet,id=input0 -vnc 127.0.0.1:4 -vga std -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5
ProcEnviron: PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-19-generic root=/dev/mapper/VgSys-root ro vga=789 quiet splash vt.handoff=7
Signal: 6
SourcePackage: qemu-kvm
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: qemu-system-x86_64 crashed with SIGABRT
UpgradeStatus: Upgraded to precise on 2012-03-14 (5 days ago)
UserGroups:

dmi.bios.date: 10/17/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0Y2MRG
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA06:bd10/17/2011:svnDellInc.:pnXPS8300:pvr:rvnDellInc.:rn0Y2MRG:rvrA00:cvnDellInc.:ct3:cvr:
dmi.product.name: XPS 8300
dmi.sys.vendor: Dell Inc.

Revision history for this message
Mateusz Marzantowicz (mmarzantowicz) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 hw_error (fmt=<optimized out>) at /build/buildd/qemu-kvm-1.0+noroms/cpus.c:357
 register_ioport_read (start=<optimized out>, length=<optimized out>, size=<optimized out>, func=<optimized out>, opaque=<optimized out>) at /build/buildd/qemu-kvm-1.0+noroms/ioport.c:153
 ioport_register (ioport=0x7f8bb3dbb4a8) at /build/buildd/qemu-kvm-1.0+noroms/ioport.c:230
 address_space_update_topology_pass (as=0x7f8bb142cd80, adding=true, old_view=<optimized out>, new_view=<optimized out>) at /build/buildd/qemu-kvm-1.0+noroms/memory.c:731
 address_space_update_topology (as=0x7f8bb142cd80) at /build/buildd/qemu-kvm-1.0+noroms/memory.c:746

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in qemu-kvm (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

Note that whoopsie is getting many segvs, i.e.:

[ 155.840506] whoopsie[1784]: segfault at 0 ip 00000000004050a2 sp 00007fff367e5488 error 4 in whoopsie[400000+9000]
[ 155.965910] init: whoopsie main process (1784) killed by SEGV signal
[ 155.965953] init: whoopsie main process ended, respawning

visibility: private → public
Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

Thanks for reporting this bug.

Have you seen this happen again?

tags: added: crash libc
Changed in qemu-kvm (Ubuntu):
status: New → Incomplete
Revision history for this message
Mateusz Marzantowicz (mmarzantowicz) wrote :

I cannot reproduce this error anymore but I am not sure it is definitely resolved. It happened unexpectedly and I did not notice all my actions before and after. If there is something I can do to test/work on this bug, please inform me.

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

@Mateusz,

thanks for the info.

If it's not reproducible, I'm afraid we can't really debug.

I've marked the bug as affecting whoopsie to see if those developers have seen the segfault before. Perhaps it points to something on your system which caused this.

If not, I'll mark the bug Invalid (which means it can't be reproduced, not that it wasn't a real bug). If it does happen again, please mark this bug confirmed and hopefully you can start noticing a pattern in what caused it.

Revision history for this message
Evan (ev) wrote :

The segfault seen in the logs was fixed in whoopsie 0.1.22. It wont have affected the qemu crash here.

Changed in qemu-kvm (Ubuntu):
status: Incomplete → Fix Released
Changed in whoopsie-daisy (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.