Red Hat Bugzilla – Bug 760165
[abrt] invalid free in vnc_dpy_resize
Last modified: 2013-02-11 17:25:48 EST
libreport version: 2.0.7
cmdline: /usr/bin/qemu-kvm -S -M pc-0.14 -enable-kvm -m 1024 -smp 1,sockets=1,cores=1,threads=1 -name exam -uuid c760ace8-d819-24be-2a89-c83141e644cb -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/exam.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -drive file=/pub/VM/exam-server,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 -netdev tap,fd=24,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:00:00:16,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 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
reason: Process /usr/bin/qemu-kvm was killed by signal 6 (SIGABRT)
time: 2011年12月05日 星期一 22时46分05秒
backtrace: Text file, 16402 bytes
build_ids: Text file, 3526 bytes
dso_list: Text file, 7381 bytes
event_log: Binary file, 24403 bytes
maps: Text file, 32897 bytes
:1. sudo service libvirtd restart
:2. open virt-manager
:3. open two virtual server in virt-manager
:Dec 4 21:59:18 localhost yum: Installed: 2:qemu-kvm-0.15.1-3.fc16.x86_64
:Dec 4 22:18:52 localhost yum: Installed: 2:qemu-kvm-tools-0.15.1-3.fc16.x86_64
:Dec 4 23:57:00 localhost qemu-kvm: Could not find keytab file: /etc/qemu/krb5.tab: No such file or directory
:Dec 5 00:01:43 localhost qemu-kvm: Could not find keytab file: /etc/qemu/krb5.tab: No such file or directory
:Dec 5 00:03:53 localhost qemu-kvm: Could not find keytab file: /etc/qemu/krb5.tab: No such file or directory
:Dec 5 22:41:32 localhost qemu-kvm: Could not find keytab file: /etc/qemu/krb5.tab: No such file or directory
:Dec 5 22:43:11 localhost qemu-kvm: Could not find keytab file: /etc/qemu/krb5.tab: No such file or directory
:Dec 5 22:45:12 localhost qemu-kvm: Could not find keytab file: /etc/qemu/krb5.tab: No such file or directory
:Dec 5 22:46:05 localhost qemu-kvm: Could not find keytab file: /etc/qemu/krb5.tab: No such file or directory
:Dec 5 22:46:10 localhost abrt: Saved core dump of pid 7593 (/usr/bin/qemu-kvm) to /var/spool/abrt/ccpp-2011-12-05-22:46:05-7593 (1118920704 bytes)
Created attachment 540954 [details]
Created attachment 540955 [details]
Created attachment 540956 [details]
Created attachment 540957 [details]
Created attachment 540958 [details]
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Converting vmdk image to qcow2.
OS Release: Fedora release 16 (Verne)
Created attachment 571192 [details]
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '16'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 16's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 16 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" and open it against that version of Fedora.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Hmm, I think that last backtrace attached is not the same as the original report.
If anyone can still reproduce on F18, please file a new bug with the updated backtrace. Closing this since F16 is going EOL soon