Description of problem: O Fedora 20 with a recompiled kernel 3.13 the command below did work fine, although the virtual machine often got blue screen when de r9 290 driver was loaded. PCI-Assign was not working well on FC20. With Rawhide 3.14 kernel, pci-assign did work well until I set up vfio to run the command below which generated the segmentation fault. # qemu-system-x86_64 -enable-kvm -M q35 -m 1024 -cpu host -smp 6,sockets=1,cores=6,threads=1 -bios /usr/share/qemu/bios.bin -vga none -device ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1 -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on -device vfio-pci,host=01:00.1,bus=root.1,addr=00.1 -device vfio-pci,host=00:1a.0,bus=pcie.0 -drive file=/opt/kvm/images/BATMAN.img,id=disk,format=qcow2 -device ide-hd,bus=ide.0,drive=disk Segmentation fault (core dumped) # ls /sys/bus/pci/drivers/vfio-pci/ 0000:00:1a.0 0000:00:1b.0 0000:01:00.0 0000:01:00.1 bind module new_id remove_id uevent unbind # lspci 00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06) 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 04) 00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04) 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-V (rev 04) 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 04) 00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d4) 00:1c.1 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #2 (rev d4) 00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d4) 00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 (rev d4) 00:1c.4 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #5 (rev d4) 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation Z87 Express LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 04) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii PRO [Radeon R9 290] 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device aac8 04:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 01) 05:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03) 06:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 01) Version-Release number of selected component: qemu-system-x86-2.0.0-0.2.rc0.fc21 Additional info: reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: qemu-system-x86_64 -enable-kvm -M q35 -m 1024 -cpu host -smp 6,sockets=1,cores=6,threads=1 -bios /usr/share/qemu/bios.bin -vga none -device ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1 -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on -device vfio-pci,host=01:00.1,bus=root.1,addr=00.1 -device vfio-pci,host=00:1a.0,bus=pcie.0 -drive file=/opt/kvm/images/BATMAN.img,id=disk,format=qcow2 -device ide-hd,bus=ide.0,drive=disk crash_function: memcpy executable: /usr/bin/qemu-system-x86_64 kernel: 3.15.0-0.rc0.git9.1.fc21.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #0 memcpy at /usr/include/bits/string3.h:51 #1 vte_terminal_get_rgb_from_index at vte.c:6321 #2 vte_terminal_get_text_range_maybe_wrapped at vte.c:6428 #3 vte_terminal_get_text_maybe_wrapped at vte.c:6533 #4 vte_terminal_get_text_include_trailing_spaces at vte.c:6599 #5 vte_terminal_accessible_update_private_data_if_needed at vteaccess.c:334 #6 vte_terminal_accessible_text_modified at vteaccess.c:446 #7 _g_closure_invoke_va at gclosure.c:831 #9 g_signal_emit_by_name at gsignal.c:3403 #10 _vte_terminal_emit_text_inserted at vte.c:971
Created attachment 882971 [details] File: backtrace
Created attachment 882972 [details] File: cgroup
Created attachment 882973 [details] File: core_backtrace
Created attachment 882974 [details] File: dso_list
Created attachment 882975 [details] File: environ
Created attachment 882976 [details] File: exploitable
Created attachment 882977 [details] File: limits
Created attachment 882978 [details] File: maps
Created attachment 882979 [details] File: open_fds
Created attachment 882980 [details] File: proc_pid_status
Created attachment 882981 [details] File: var_log_messages
Looks like a vte crash. Carlos, you can work around it by using -display sdl
Carlos, can you recompile vte-0.36 with the patch from https://bugzilla.gnome.org/show_bug.cgi?id=728051#c3 ? I see a chance that it fixes the problem, but I'm really not sure. Can you please help me reproduce the problem? I'm using ubuntu trusty, and I'm not familiar with qemu at all. Where do I get BATMAN.img (or any other suitable image file)?
vte-0.36.1 (already available in Rawhide) should fix it.
Sorry for the delay in answering. You may close the issue because I migrated my system back to Fedora 20, when the kernel 3.14 was released. The problem occurred when I explicitly added the GPU to vfio driver. But if I configure the device to use PCI-STUB and configure PCI assign on virt-manager, everything works fine. Before starting the VM: lrwxrwxrwx. 1 root root 0 May 22 09:30 driver -> ../../../../bus/pci/drivers/pci-stub After starting the VM: lrwxrwxrwx. 1 root root 0 May 22 20:25 driver -> ../../../../bus/pci/drivers/vfio-pci I'm still learning about all these so not sure if I did something wrong in the first place by explicitly associating the driver to vfio. Thank you for the great support.
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.