Red Hat Bugzilla – Bug 904150
[abrt] qemu-system-x86-1.2.2-1.fc18: die2: Process /usr/bin/qemu-kvm was killed by signal 6 (SIGABRT)
Last modified: 2013-04-01 18:03:47 EDT
Description of problem:
Running the parallel mount test, part of the libguestfs test suite.
Version-Release number of selected component:
cmdline: /usr/bin/qemu-kvm -name guestfs-az1s839kb2mw68gv -S -M pc-1.2 -enable-kvm -m 500 -smp 1,sockets=1,cores=1,threads=1 -uuid 805a9441-0872-3af2-4826-65a210ea9c30 -nographic -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/home/rjones/.config/libvirt/qemu/lib/guestfs-az1s839kb2mw68gv.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-reboot -no-shutdown -no-acpi -kernel /home/rjones/d/libguestfs/tmp/.guestfs-1000/kernel.6839 -initrd /home/rjones/d/libguestfs/tmp/.guestfs-1000/initrd.6839 -append 'panic=1 console=ttyS0 udevtimeout=600 no_timer_check acpi=off printk.time=1 cgroup_disable=memory root=/dev/sdb selinux=0 TERM=xterm-256color' -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x3 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 -drive file=/home/rjones/d/libguestfs/tests/mount-local/test11.img,if=none,id=drive-scsi0-0-0-0,format=raw,cache=none -device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=1 -drive file=/home/rjones/d/libguestfs/tmp/libguestfsOLm2Zw/snapshot1,if=none,id=drive-scsi0-0-1-0,format=qcow2,cache=unsafe -device scsi-hd,bus=scsi0.0,channel=0,scsi-id=1,lun=0,drive=drive-scsi0-0-1-0,id=scsi0-0-1-0 -chardev socket,id=charserial0,path=/home/rjones/d/libguestfs/tmp/libguestfsOLm2Zw/console.sock -device isa-serial,chardev=charserial0,id=serial0 -chardev socket,id=charchannel0,path=/home/rjones/d/libguestfs/tmp/libguestfsOLm2Zw/guestfsd.sock -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.libguestfs.channel.0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5
Thread no. 1 (4 frames)
#2 die2 at posix-aio-compat.c:84
#3 thread_create at posix-aio-compat.c:122
#4 do_spawn_thread at posix-aio-compat.c:408
#5 aio_thread at posix-aio-compat.c:320
Created attachment 687508 [details]
Created attachment 687509 [details]
Created attachment 687510 [details]
Created attachment 687511 [details]
Created attachment 687512 [details]
Created attachment 687513 [details]
Created attachment 687514 [details]
Created attachment 687515 [details]
Created attachment 687516 [details]
Created attachment 687517 [details]
Created attachment 687518 [details]
Actually this crash happened twice.
Actually multiple times now.
Rich are you still seeing this on latest F18 packages?
pthread_create is failing. It should be showing strerror on stderr, but abrt didn't report it...
The answer is I've been using qemu 1.4.0 from Rawhide for
a while now, and it's been rock solid. I don't really
care about the F18 package.
This raises the side question of why we don't just upgrade
qemu to 1.4.0 in F18 too.
But in any case, I don't care about this bug and I've not
personally experienced it since January, so feel free to
close it unless anyone else has seen it.
(In reply to comment #15)
> The answer is I've been using qemu 1.4.0 from Rawhide for
> a while now, and it's been rock solid. I don't really
> care about the F18 package.
> This raises the side question of why we don't just upgrade
> qemu to 1.4.0 in F18 too.
Same reason to avoid any rebase of a critical component: risk of regressions and increased effort.
> But in any case, I don't care about this bug and I've not
> personally experienced it since January, so feel free to
> close it unless anyone else has seen it.
Thanks, closing then.