[Bug 958333] New: GNOME doesn't start up on KVM/QEMU in Wayland mode
http://bugzilla.opensuse.org/show_bug.cgi?id=958333 Bug ID: 958333 Summary: GNOME doesn't start up on KVM/QEMU in Wayland mode Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome@forge.provo.novell.com Reporter: tiwai@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- While installing TW 20151201, I noticed that GNOME desktop doesn't work at all with QEMU/KVM. With the default cirrus graphics (-vga=cirrus), it ends up with the blank screen. With Bochs std VGA (-vga=std), GDM screen appears but the mouse cursor is invisible. Both problem come from the GDM being invoked in Wayland mode -- which is enabled as default on TW. Editing /etc/gdm/custom.conf to disable Wayland makes both working... well, partially. I'm going to open another report for the rest issue. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=958333
Dominique Leuenberger
http://bugzilla.opensuse.org/show_bug.cgi?id=958333
http://bugzilla.opensuse.org/show_bug.cgi?id=958333#c1
Dominique Leuenberger
While installing TW 20151201, I noticed that GNOME desktop doesn't work at all with QEMU/KVM. With the default cirrus graphics (-vga=cirrus), it ends up with the blank screen. With Bochs std VGA (-vga=std), GDM screen appears but the mouse cursor is invisible.
qemu by default uses cirrus vga (from the 90ies) - this won't ever work with Wayland. Maybe qemu one day moves with the time and switches their VGA implementation to 'std' (which is SO weird by the name that one would expect this to be the standard/default) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=958333
http://bugzilla.opensuse.org/show_bug.cgi?id=958333#c2
Vasilis Liaskovitis
http://bugzilla.opensuse.org/show_bug.cgi?id=958333
http://bugzilla.opensuse.org/show_bug.cgi?id=958333#c3
--- Comment #3 from Vasilis Liaskovitis
http://bugzilla.opensuse.org/show_bug.cgi?id=958333
http://bugzilla.opensuse.org/show_bug.cgi?id=958333#c4
Vasilis Liaskovitis
http://bugzilla.opensuse.org/show_bug.cgi?id=958333
http://bugzilla.opensuse.org/show_bug.cgi?id=958333#c5
--- Comment #5 from Stefan Dirsch
http://bugzilla.opensuse.org/show_bug.cgi?id=958333
http://bugzilla.opensuse.org/show_bug.cgi?id=958333#c6
--- Comment #6 from Vasilis Liaskovitis
Well, I believe you cannot expect glamor support, i.e. 2D acceleration via Mesa's DRI driver in Qemu. This is more for real hardware. ;-)
As far as i understand the virgl driver for qemu is supposed to passthrough 3D capabilities of the host. virgl consists of a Linux kernel KMS driver, X.org 2D DDX driver and Mesa 3D driver. So glamor/egl and the virgl driver *do* work on SLES12SP2 qemu VM (exact same Leap 42.2 host used for both machines): [ 5.391] (II) LoadModule: "glamoregl" [ 5.391] (II) Loading /usr/lib64/xorg/modules/libglamoregl.so [ 5.394] (II) Module glamoregl: vendor="X.Org Foundation" [ 5.394] compiled for 1.18.3, module version = 1.0.0 [ 5.394] ABI class: X.Org ANSI C Emulation, version 0.4 [ 5.394] (II) glamor: OpenGL accelerated X.org driver based. [ 5.464] (II) glamor: EGL version 1.4 (DRI2): [ 5.465] (II) modeset(0): glamor initialized glxinfo | grep -i renderer OpenGL renderer string: Gallium 0.4 on virgl On Tumbleweed VM, I get the egl/glamor errors mentioned in previous comments, and mesa reverts to software rasterizer (llvmpipe). So there must be something that causes this. The linux KMS module (virtio-gpu) works on both distributions, dmesg on both TW and SLES12SP2 shows: [drm] pci: virtio-vga detected [drm] virgl 3d acceleration enabled so perhaps the problem lies in TW Xorg or mesa. Mesa build is using --with-gallium-drivers=virgl on x86_64 so it definitely has virgl support. Note: Testing virgl VMs on opensuse/SLES host requires using sdl/gtk hacks in libvirt: https://www.kraxel.org/blog/2015/10/virtio-gpu-and-libvirt/, because afaik spice support is not there. The libspice server versions in openSUSE/SLES (host systems) are unfortunately old. even on TW (but this is more subject for a FATE or virt team, not part of this ticket) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=958333
http://bugzilla.opensuse.org/show_bug.cgi?id=958333#c7
Stefan Dirsch
http://bugzilla.opensuse.org/show_bug.cgi?id=958333
http://bugzilla.opensuse.org/show_bug.cgi?id=958333#c8
Vasilis Liaskovitis
Ok. Can be that the requirements for glamor are higher now with Xserver version of TW. Are the extensions
EGL_KHR_platform_gbm EGL_EXT_device_base available on Leap 42.2? Check this via glxinfo.
I don't see either of these extensions on my Leap 42.2 desktop (using nouveau). I can check another Leap 42.2 i915 system tomorrow. Leap system uses Mesa-11.2.2-166.1. Maybe the combination of old mesa on Leap host and the new mesa on TW guest is causing an issue. It would be good to test with a TW host, but I don't have one atm... If I set one up, I will share the results. TW guest VM is using TW build 20170407, but I also tested with latest Mesa-17.0.3-663.1.x86_64.rpm and libglvnd0-0.1.1~20161222~dc16f8c-7.1.x86_64.rpm from http://download.opensuse.org/repositories/X11:/XOrg/openSUSE_Tumbleweed/x86_... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=958333
http://bugzilla.opensuse.org/show_bug.cgi?id=958333#c9
Stefan Dirsch
(In reply to Stefan Dirsch from comment #7)
Ok. Can be that the requirements for glamor are higher now with Xserver version of TW. Are the extensions
EGL_KHR_platform_gbm EGL_EXT_device_base available on Leap 42.2? Check this via glxinfo.
I don't see either of these extensions on my Leap 42.2 desktop (using nouveau). I can check another Leap 42.2 i915 system tomorrow. Leap system uses Mesa-11.2.2-166.1.
Then you can easily test, whether glamor of Leap 42.2 doesn't need these extensions, by using modeset driver for NVIDIA and Intel card. Just uninstall xf86-video-nouveau/intel driver. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=958333
http://bugzilla.opensuse.org/show_bug.cgi?id=958333#c10
--- Comment #10 from Vasilis Liaskovitis
(In reply to Vasilis Liaskovitis from comment #8)
(In reply to Stefan Dirsch from comment #7)
Ok. Can be that the requirements for glamor are higher now with Xserver version of TW. Are the extensions
EGL_KHR_platform_gbm EGL_EXT_device_base available on Leap 42.2? Check this via glxinfo.
I don't see either of these extensions on my Leap 42.2 desktop (using nouveau). Then you can easily test, whether glamor of Leap 42.2 doesn't need these extensions, by using modeset driver for NVIDIA and Intel card. Just uninstall xf86-video-nouveau/intel driver.
Testing on i915 Leap host: glamor initialization in the TW guest fails with same messages, both with xf86-video-intel, and without xf86-video-intel (modeset driver) in the Leap host. Just to clarify: glamor initialization succeeds on the Leap host both with and without xf86-video-intel. The glamor/egl errors of comment#4 happen only for the TW guest. Perhaps I misunderstood the experiment you suggested though. I hope to also test on a TW host soon. And I'll try to understand the virgl architecture a bit more. xserver commits f4a41155 and 05e19644 might be relevant. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=958333
http://bugzilla.opensuse.org/show_bug.cgi?id=958333#c11
--- Comment #11 from Stefan Dirsch
http://bugzilla.opensuse.org/show_bug.cgi?id=958333
http://bugzilla.opensuse.org/show_bug.cgi?id=958333#c12
--- Comment #12 from Stefan Dirsch
xserver commits f4a41155 and 05e19644 might be relevant.
Both patches are in xserver 1.19.3. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=958333
http://bugzilla.opensuse.org/show_bug.cgi?id=958333#c13
--- Comment #13 from Vasilis Liaskovitis
http://bugzilla.opensuse.org/show_bug.cgi?id=958333
http://bugzilla.opensuse.org/show_bug.cgi?id=958333#c14
--- Comment #14 from Vasilis Liaskovitis
http://bugzilla.opensuse.org/show_bug.cgi?id=958333
http://bugzilla.opensuse.org/show_bug.cgi?id=958333#c15
Vasilis Liaskovitis
http://bugzilla.opensuse.org/show_bug.cgi?id=958333
http://bugzilla.opensuse.org/show_bug.cgi?id=958333#c16
Stefan Dirsch
http://bugzilla.opensuse.org/show_bug.cgi?id=958333
http://bugzilla.opensuse.org/show_bug.cgi?id=958333#c17
Vasilis Liaskovitis
Thanks. I believe this is a dup of boo#1034832. Could you please verify by installing Mesa-libEGL1 package on the guest in the VM?
thanks, I confirm that installing Mesa-libEGL1 in the guest solves the issue. libglamor initializes correctly and I can have a wayland session using virgl driver and renderer. /usr/lib/gdm/gdm-x-session[1927]: (II) glamor: EGL version 1.4 (DRI2): /usr/lib/gdm/gdm-x-session[1927]: (II) modeset(0): glamor initialized ~ # lspci | grep VGA 00:02.0 VGA compatible controller: Red Hat, Inc Virtio GPU (rev 01) ~ # glxinfo | grep -i renderer OpenGL renderer string: Gallium 0.4 on virgl ~ # echo $XDG_SESSION_TYPE wayland If qemu QXL driver is used instead of the qemu virgl driver, a wayland session can also work. In this case with sw, but I think this is expected with the QXL driver: org.gnome.Shell.desktop[1526]: Disabling glamor and dri3, EGL setup failed org.gnome.Shell.desktop[1526]: Failed to initialize glamor, falling back to sw ~ # lspci | grep VGA 00:02.0 VGA compatible controller: Red Hat, Inc. QXL paravirtual graphic card (rev 04) ~ # glxinfo | grep -i renderer OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.9, 356 bits) ~ # echo $XDG_SESSION_TYPE wayland -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=958333
http://bugzilla.opensuse.org/show_bug.cgi?id=958333#c18
Stefan Dirsch
participants (1)
-
bugzilla_noreply@novell.com