Using WSL as a VirtualGL server platform isn't officially supported, because it doesn't make sense in production VirtualGL environments to use a Windows workstation as a virtual Linux server. However, there is no technical reason why it shouldn't work.
Issue #65 (the necessity to use LightDM on Ubuntu 16.04 and later) was worked around in VirtualGL 2.6.2, so that issue is no longer relevant in the latest releases of VirtualGL.
I need to reproduce the issue before we
can proceed, so please specify the version of Ubuntu you are
using. Also, please make sure you are using the latest release
of VirtualGL.
--
You received this message because you are subscribed to the Google Groups "VirtualGL User Discussion/Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to virtualgl-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/virtualgl-users/34f961d5-dcad-4a07-9624-1c36512faf88n%40googlegroups.com.
If systemctl doesn't exist, then that's
not exactly a standard Ubuntu configuration, and it doesn't
surprise me that multiple things are broken from VirtualGL's
point of view. I'm also suspicious of your DISPLAY environment
variable. It's uncommon in this day and age for X servers to
allow TCP communications, so your DISPLAY should be something
like :0.0 rather than <IP_address>:0.0. I'm happy to
investigate this further on a paid support basis, but since I don't personally use WSL, there
unfortunately isn't anything else I can do within the context of
community support unless I can reproduce the issue using a
standard Ubuntu 20.04 installation (which I can't.)
DRC
To view this discussion on the web visit https://groups.google.com/d/msgid/virtualgl-users/acd857f4-1af3-4ed2-9b71-41aa4ac57d60n%40googlegroups.com.
You can e-mail me directly from here:
To view this discussion on the web visit https://groups.google.com/d/msgid/virtualgl-users/c7fd341e-f0b6-46db-88f7-466196c60ab1n%40googlegroups.com.