I kill vglclient and start it explicitly in a terminal with performance measurement VGL_PROFILE=1 vglclientĪfter connecting to the container, I run vglrun +pr steamĬompress 0 - 50.35 Mpixels/sec- 28.54 fps Step one is to measure the performance of different steps, to find the bottleneck. When there is a lot going on there is some lag and stuttering, so I will do some tweaking. There is no sound, so I will have to forward that myself. $(xauth list the-big-one/unix:0 | awk '')Īnd now it works! It takes a while before I’m able to start games, for some reason. I solve this by adding it manually (kudos to this xauth add test-system1/unix:0. This is caused by the cookie having an identifier that includes the hostname ( the-big-one), so the container ( test-system1) doesn’t realize it can be used for its own display :0. Xauthority link and link the other lxc config device remove test-system1 lxc config device add test-system1 vgl_xauth_key disk path=/etc/opt/VirtualGL/vgl_xauth_key source=/etc/opt/VirtualGL/vgl_xauth_key I install VirtualGL and LightDM on the host, and configure LightDM as before. Then vglrun copies it into ~/.Xauthority. If I understand it correctly (from reading this exchange), the cookie required for accessing display :0 is supposed to be copied to /etc/opt/VirtualGL/vgl_xauth_key by LightDM when it starts.
X11 connection rejected because of wrong authentication.Įrror: couldn't open display localhost:10.0 Xauth: unable to link authority file /home/ubuntu/.Xauthority, use /home/ubuntu/.Xauthority-n I link the cookie and try lxc config device add test-system1 Xauthority disk path=/home/ubuntu/.Xauthority vglrun glxgears VirtualGL needs display :0 because it has access to the hardware. Invalid MIT-MAGIC-COOKIE-1 key ERROR: Could not open display :0. 192.168.1.126, the IP address of your SSH client. NOTICE: Automatically setting VGL_CLIENT environment variable to This page has instructions I will follow.įirst, I install VirtualGL on my local machine as well, to get vglconnect, then I try to run sudo dpkg -i vglconnect vglrun glxgears I had assumed that it would be too slow, but I will try it out. Instead, I will try to use plain X11 forwarding (with VirtualGL). I am not able to start a dummy X server and have NoMachine connect to it either. Try as I might, I cannot find a way to configure the embedded X server in NoMachine to have multiple monitors.
Today I will get multiple monitors working, but my solution to that turns out to be switching to X11 forwarding. Last time I managed to run Steam games with VirtualGL in my container that I access with NoMachine.
0 kommentar(er)
