On 14.11.2016 11:02, Michael Tokarev wrote: > 10.11.2016 00:00, Andreas Cadhalpun wrote : >> If you want to use virgl with virt-manager you don't need to enable >> gtk3 or sdl2, only virglrenderer and opengl. > > This does not help, unfortunately. Yesterday I wrote a quick hack > to made gtk3 display modular, this works fine. However, linking > with virglrenderer brings half of the X/drm stack back again. > I've no idea how virglrenderer works and why it needs CLIENT > libs on a display-less program... :(
The only additional dependencies compared to the current qemu-system-x86 package are: libdrm2 libepoxy0 libexpat1 libgbm1 libvirglrenderer0 libwayland-client0 libwayland-server0 That doesn't seem excessive to me. > Anyone know how this is supposed to work or to be used? > As far as I can see, virglrenderer usage in qemu is "headless", > as in, it doesn't do actual displaying (when omitting gtk/sdl > display). Why it needs libwayland, libdrm and various drm-radeon > and similar? Maybe virglrenderer should be split up into two > parts, say, headless and headful? :) I've no idea how it works, but how to use it is described on various websites, e.g. [1]. >> However, you also need a newer libspice-server-dev (0.13.2). >> With qemu built that way virgl works fine for virt-manager and >> even gnome-boxes. > > 0.13 is a beta release, should it be pushed to Debian at this > time? I'm aware that it is a development release and I don't know what that implies for ABI/API stability. However, I'd be delighted to have qemu supporting virgl over spice in stretch. Best regards, Andreas 1: https://www.kraxel.org/blog/2016/09/using-virtio-gpu-with-libvirt-and-spice/
