Bugzilla – Bug 1227129
libva/cvirtio_gpu_drv_video.so: Chromium GPU errors on kvm/virtio
Last modified: 2024-07-18 12:44:30 UTC
Fresh Tumbleweed GNOME install in KVM. Chromium hangs before any GUI shows up. # chromium libva error: /usr/lib64/dri/virtio_gpu_drv_video.so init failed [28135:28135:0626/115134.122807:ERROR:viz_main_impl.cc(166)] Exiting GPU process due to errors during initialization # /usr/bin/chromium --enable-features=UseOzonePlatform --ozone-platform=wayland --force-dark-mode --enable-features=WebUIDarkMode libEGL warning: egl: failed to create dri2 screen libEGL warning: egl: failed to create dri2 screen libEGL warning: NEEDS EXTENSION: falling back to kms\_swrast libva error: /usr/lib64/dri/virtio\_gpu\_drv\_video.so init failed \[28226:28226:0626/115232.941494:ERROR:viz\_main\_impl.cc(166)\] Exiting GPU process due to errors during initialization
Re-assign to libva maintainer Chromium looks fine here
I'm wondering if less demanding apps like eglinfo are working on Wayland. Package to install is Mesa-demo-egl.
Can't reproduce now. /usr/bin/chromium --enable-features=UseOzonePlatform --ozone-platform=wayland --force-dark-mode --enable-features=WebUIDarkMode libEGL warning: egl: failed to create dri2 screen libEGL warning: egl: failed to create dri2 screen libEGL warning: NEEDS EXTENSION: falling back to kms_swrast libva error: /usr/lib64/dri/virtio_gpu_drv_video.so init failed [28717:28717:0709/132034.681158:ERROR:viz_main_impl.cc(166)] Exiting GPU process due to errors during initialization [28672:28672:0709/132034.950985:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.ScreenSaver.GetActive: object_path= /org/freedesktop/ScreenSaver: org.freedesktop.DBus.Error.NotSupported: This method is not part of the idle inhibition specification: https://specifications.freedesktop.org/idle-inhibit-spec/latest/ libEGL warning: egl: failed to create dri2 screen libEGL warning: egl: failed to create dri2 screen libEGL warning: NEEDS EXTENSION: falling back to kms_swrast libva error: /usr/lib64/dri/virtio_gpu_drv_video.so init failed [28820:28820:0709/132035.004726:ERROR:viz_main_impl.cc(166)] Exiting GPU process due to errors during initialization libva error: /usr/lib64/dri/virtio_gpu_drv_video.so init failed [28757:8:0709/132035.062300:ERROR:command_buffer_proxy_impl.cc(131)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
Well, this doesn't answer my question of comment#2
(In reply to Stefan Dirsch from comment #2) > I'm wondering if less demanding apps like eglinfo are working on Wayland. > Package to install is Mesa-demo-egl. Mesa-demo-egl is a package and I'm not sure which bin from it you want tested however eglgears_x11 works using xWayland (not directly from Wayland).
No, I've meant 'eglinfo'.
Created attachment 875972 [details] eglinfo
Created attachment 875973 [details] eglinfo.txt
Thanks. Many errors: [...] MESA: error: ZINK: vkCreateInstance failed (VK_ERROR_INCOMPATIBLE_DRIVER) libEGL warning: egl: failed to create dri2 screen EGL client extensions string: [...] GBM platform: eglinfo: eglInitialize failed [...] 0x0c 30 0 10 10 10 0 16 0 0 0 0x00-- y y y win 0x0dMESA: error: ZINK: vkCreateInstance failed (VK_ERROR_INCOMPATIBLE_DRIVER) libEGL warning: egl: failed to create dri2 screen 30 0 10 10 10 0 24 0 0 0 0x00-- y y y win [...] 0x29 32 0 8 8 8 8 0 0 0 0 0x56TC a y y y win,pb,pix 0x2a 32 0 8 8 8 8 16 0 0 0 0x56TC a y y y libEGL warning: egl: failed to create dri2 screen libEGL warning: egl: failed to create dri2 screen win,pb,pix 0x2b 32 0 8 8 8 8 24 0 0 0 0x56TC a y y y win,pb,pix [...] 0x0a 32 0 10 10 10 2 32 0 4 1 0x00-- a y y y pb 0x0b 30 0 10 10 10 0 0 0 0 0 0x00-- y y y y libEGL warning: egl: failed to create dri2 screen libEGL warning: egl: failed to create dri2 screen libEGL warning: NEEDS EXTENSION: falling back to kms_swrast pb 0x0c 30 0 10 10 10 0 16 0 0 0 0x00-- y y y y pb
Maybe the /usr/lib64/dri/virtio_gpu_drv_video.so libva/VA-API driver is just broken and we should disable the build. You could try to rename it temporarily to test if then chromium starts falling back to software rendering hopefully. /usr/lib64/dri/virtio_gpu_dri.so seems also to be problematic. You could try to workaround the issue by using dri_driver=kms_swrast chromium ... dri_driver=kms_swrast eglinfo
(In reply to Stefan Dirsch from comment #11) > Maybe the /usr/lib64/dri/virtio_gpu_drv_video.so libva/VA-API driver is just > broken and we should disable the build. You could try to rename it > temporarily to test if then chromium starts falling back to software > rendering hopefully. > > /usr/lib64/dri/virtio_gpu_dri.so seems also to be problematic. You could try > to workaround the issue by using > > dri_driver=kms_swrast chromium ... > > dri_driver=kms_swrast eglinfo @L Any update you can provide about that?