Description of problem: It was installing Fedora 21 server. I was not in the room at the time of the crash. Version-Release number of selected component: qemu-system-x86-2.1.2-7.fc21 Additional info: reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/bin/qemu-system-x86_64 -machine accel=kvm -name server.foo -S -machine pc-i440fx-2.1,accel=kvm,usb=off -cpu core2duo -m 1024 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 1b5928cc-aab1-4a4a-97e5-7afa24c71394 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/server.foo.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-reboot -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x5.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x5 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x5.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x5.0x2 -device ahci,id=ahci0,bus=pci.0,addr=0x6 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x7 -drive file=/var/lib/libvirt/images/server.foo.qcow2,if=none,id=drive-sata0-0-0,format=qcow2 -device ide-hd,bus=ahci0.0,drive=drive-sata0-0-0,id=sata0-0-0,bootindex=2 -drive file=/home/tr/Download/Fedora-Server-netinst-x86_64-21.iso,if=none,id=drive-ide0-0-0,readonly=on,format=raw -device ide-cd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -netdev tap,fd=23,id=hostnet0,vhost=on,vhostfd=24 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:ec:30:ff,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/server.foo.org.qemu.guest_agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -chardev spicevmc,id=charchannel1,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=com.redhat.spice.0 -device usb-tablet,id=input0 -spice port=5900,addr=127.0.0.1,disable-ticketing,seamless-migration=on -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,bus=pci.0,addr=0x2 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -chardev spicevmc,id=charredir0,name=usbredir -device usb-redir,chardev=charredir0,id=redir0 -chardev spicevmc,id=charredir1,name=usbredir -device usb-redir,chardev=charredir1,id=redir1 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -msg timestamp=on crash_function: spice_logv executable: /usr/bin/qemu-system-x86_64 kernel: 3.17.7-300.fc21.x86_64 runlevel: N 5 type: CCpp uid: 107 Truncated backtrace: Thread no. 1 (6 frames) #2 spice_logv at log.c:109 #3 spice_log at log.c:123 #4 dev_destroy_primary_surface at red_worker.c:11201 #5 dispatcher_handle_single_read at dispatcher.c:139 #6 dispatcher_handle_recv_read at dispatcher.c:162 #7 red_worker_main at red_worker.c:12021
Created attachment 973996 [details] File: backtrace
Created attachment 973997 [details] File: cgroup
Created attachment 973998 [details] File: core_backtrace
Created attachment 973999 [details] File: dso_list
Created attachment 974000 [details] File: environ
Created attachment 974001 [details] File: limits
Created attachment 974002 [details] File: maps
Created attachment 974003 [details] File: open_fds
Created attachment 974004 [details] File: proc_pid_status
Created attachment 974005 [details] File: var_log_messages
Same backtrace as bug #1044734
*** Bug 1181589 has been marked as a duplicate of this bug. ***
Description of problem: Starting a operating system in Gnome Boxes Version-Release number of selected component: selinux-policy-3.13.1-105.11.fc21.noarch Additional info: reporter: libreport-2.3.0 hashmarkername: setroubleshoot kernel: 3.19.3-200.fc21.x86_64 type: libreport
Description of problem: Happend for the second time, I guess, while away from keyboard. Not sure what this report means exactly. Version-Release number of selected component: selinux-policy-3.13.1-105.13.fc21.noarch Additional info: reporter: libreport-2.3.0 hashmarkername: setroubleshoot kernel: 3.19.5-200.fc21.x86_64 type: libreport
Does this crash maybe happen when trying to resume from a previously saved VM state? To save a VM go to Shutdown > Save in virt-manager.
(In reply to Raphael Groner from comment #14) > Description of problem: > Happend for the second time, I guess, while away from keyboard. Not sure > what this report means exactly. > > Version-Release number of selected component: > selinux-policy-3.13.1-105.13.fc21.noarch > > Additional info: > reporter: libreport-2.3.0 > hashmarkername: setroubleshoot > kernel: 3.19.5-200.fc21.x86_64 > type: libreport Hi Raphael, is not clear why a crash on selinux-policy-3.13.1-105.13.fc21.noarch is related to qemu. If just a mistake, who did you manage to have the problem? Did you have virt-viewer opened while you had the crash? What was doing the guest? And the host?
(In reply to Frediano Ziglio from comment #16) … > Hi Raphael, is not clear why a crash on > selinux-policy-3.13.1-105.13.fc21.noarch > is related to qemu. I do not know. Abrt detected this bug as a dup. Originally, abrt said that gdb crashed somehow … > If just a mistake, who did you manage to have the problem? Did you have > virt-viewer opened while you had the crash? What was doing the guest? And > the host? Yes, virt-viewer (or virt-manager) is suspected to have caused the crash. I tried to resume a kvm machine from saved state but it failed with a weird error message.
*** Bug 1044734 has been marked as a duplicate of this bug. ***
I got the same qemu-system-x86_64 killed by SIGABRT on a Fedora 21 x86_64 box while trying to use the VM via the Virtual Machine Manager. In my case, the VM was up and running (Fedora 21 x86_64) when I connected my laptop to an external monitor at which point the guest's Gnome Classic session bottom panel disappeared and the Gnome session refused to resize when resizing the guest window. I attempted to run "gnome-shell --replace"---whether right or wrong---from a Gnome terminal in an attempt to recover my session because I didn't want to loose the VPN connection I was actively working in, which didn't work. I then pressed CTRL-C to terminate the gnome-shell process; which rightly caused all panels, title bars, etc. to disappear. Shortly after this the SIGABRT occurred. The QEMU guest agent is installed and running inside the guest.
Do you have additional data? A core dump would be very useful. Are you sure is a similar issue? Is spice_logv() related?
Fedora 21's built-in problem reporting stated the issue had already been reported and referenced this bug id and a duplicate. I went back into the problem reporting app and the report has disappeared so I can't provide any more info. Even if I could provide a core dump, it would not be safe for me to do so because I work on a project that involves ITAR and EAR controlled information.
Description of problem: Was working in a vm, that was in virt-manager Version-Release number of selected component: selinux-policy-3.13.1-105.21.fc21.noarch Additional info: reporter: libreport-2.3.0 hashmarkername: setroubleshoot kernel: 4.1.8-100.fc21.x86_64 type: libreport
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 EOL if it remains open with a Fedora 'version' of '21'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 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 change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
All faf hits are on f21 with older spice versions, so presumably this is fixed in f22+
Description of problem: reported while away from keyboard Version-Release number of selected component: selinux-policy-3.13.1-128.18.fc22.noarch Additional info: reporter: libreport-2.6.3 hashmarkername: setroubleshoot kernel: 4.2.5-201.fc22.x86_64 type: libreport