Description of problem: Following the setup instructions found here: https://aspiceodyssey.wordpress.com/2017/04/28/fedora25-3d-accelerated-guest, with the only change being I used a Fedora 26 host with an M2000 NIVIDIA card, my guest crashed with the following stack trace: Process 20868 (virt-manager) of user 1026 dumped core. Stack trace of thread 20868: #0 0x00007f9e25b4c69b raise (libc.so.6) #1 0x00007f9e25b4e4a0 abort (libc.so.6) #2 0x00007f9e0996ec9c gl_provider_resolver (libepoxy.so.0) #3 0x00007f9e09974bf1 gl_single_resolver (libepoxy.so.0) #4 0x00007f9e09979ada epoxy_glEGLImageTargetTexture2DOES_global_rewrite_ptr (libepoxy.so.0) #5 0x00007f9dd56c7851 spice_egl_update_scanout (libspice-client-gtk-3.0.so.5) #6 0x00007f9dd56c13ba spice_display_widget_gl_scanout (libspice-client-gtk-3.0.so.5) #7 0x00007f9dd56c6ac7 spice_egl_init (libspice-client-gtk-3.0.so.5) #8 0x00007f9dd56c135c spice_display_widget_gl_scanout (libspice-client-gtk-3.0.so.5) #9 0x00007f9e1d0d930d g_closure_invoke (libgobject-2.0.so.0) #10 0x00007f9e1d0eb98e signal_emit_unlocked_R (libgobject-2.0.so.0) #11 0x00007f9e1d0f41a5 g_signal_emit_valist (libgobject-2.0.so.0) #12 0x00007f9e1d0f4b0f g_signal_emit (libgobject-2.0.so.0) #13 0x00007f9e1d0dd594 g_object_dispatch_properties_changed (libgobject-2.0.so.0) #14 0x00007f9e1d0dfa19 g_object_notify (libgobject-2.0.so.0) #15 0x00007f9de6cfd030 notify_main_context (libspice-client-glib-2.0.so.8) #16 0x00007f9e1cdfdc27 g_idle_dispatch (libglib-2.0.so.0) #17 0x00007f9e1ce01247 g_main_context_dispatch (libglib-2.0.so.0) #18 0x00007f9e1ce015e8 g_main_context_iterate.isra.25 (libglib-2.0.so.0) #19 0x00007f9e1ce0167c g_main_context_iteration (libglib-2.0.so.0) #20 0x00007f9e1c43cebd g_application_run (libgio-2.0.so.0) #21 0x00007f9e1cbb4bde ffi_call_unix64 (libffi.so.6) #22 0x00007f9e1cbb454f ffi_call (libffi.so.6) #23 0x00007f9e1d77dce4 pygi_invoke_c_callable (_gi.so) #24 0x00007f9e1d77f838 pygi_function_cache_invoke (_gi.so) #25 0x00007f9e1d773c89 _callable_info_call (_gi.so) #26 0x00007f9e268bca53 PyObject_Call (libpython2.7.so.1.0) #27 0x00007f9e2699f454 PyEval_EvalFrameEx (libpython2.7.so.1.0) #28 0x00007f9e269a1d99 PyEval_EvalFrameEx (libpython2.7.so.1.0) #29 0x00007f9e269a43f8 PyEval_EvalCodeEx (libpython2.7.so.1.0) #30 0x00007f9e269a1433 PyEval_EvalFrameEx (libpython2.7.so.1.0) #31 0x00007f9e269a43f8 PyEval_EvalCodeEx (libpython2.7.so.1.0) #32 0x00007f9e269a4609 PyEval_EvalCode (libpython2.7.so.1.0) #33 0x00007f9e2697c81f run_mod (libpython2.7.so.1.0) #34 0x00007f9e2697c8ca PyRun_FileExFlags (libpython2.7.so.1.0) #35 0x00007f9e2697d8ce PyRun_SimpleFileExFlags (libpython2.7.so.1.0) #36 0x00007f9e2697061e Py_Main (libpython2.7.so.1.0) #37 0x00007f9e25b3650a __libc_start_main (libc.so.6) #38 0x00005560d5eac77a _start (python2.7) Version-Release number of selected component (if applicable): virt-manager-1.4.2-1.fc26.src.rpm libepoxy-1.4.3-1.fc26.src.rpm How reproducible: Follow the instructions in the link above. Also had to add `setsebool -P virt use_execmem 1`. Steps to Reproduce: 1. Enable 3D for the guest as indicated above 2. Launch the guest 3. There is no step 3 Actual results: Crash in GL Expected results: Somewhat variable, like semi-random results on the display, but no crash. Additional info:
This happens depending on this: <graphics type='spice'> <listen type='none'/> <gl enable='no'/> </graphics> If you set <gl enable='yes'/>, then you get the crash. Will attach the configuration file.
Created attachment 1331979 [details] Configuration file This is a working configuration file. If you change "<gl enable='yes'/>" in the <graphics> section, then it crashes.
Thanks for the report. Why is spice-gtk calling egl functions if gl enable='no' ? My guess is libepoxy is just hitting an assert here but full debuginfo trace is required to be sure. What spice-gtk version are you using?
*** Bug 1507290 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 '26'. 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 26 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.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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.