Since no one else has reported this, I would strongly suspect your GPU pass-through configuration. Is the issue reproducible when directly accessing the GPU without a VM?
On 8/21/19 9:11 PM, Sam wrote: > Hi. > > I'm running in to an issue where VirtualGL works flawlessly for a > while after booting the system, but then develops problems after a > short time (5 mins or so). Using glxgears as an example, these > problems manifests as either a black window or corrupted images being > displayed by the client. nvidia-smi shows glxgears running on the GPU > whilst the black/corrupted window is shown, though the framerate > reported by glxgears is very low (~0.3FPS). Other applications also > initially run perfectly, but then fail to start or show corrupted > graphics a few minutes following boot. > > My configuration: > - CentOS 7 > - Nvidia Quadro P2000, passed through to a VM running VirtualGL via VFIO. > - Latest VirtualGL dev version (2.6.80-20190717) > - Latest TurboVNC dev verison (2.2.80-20190803) > > Earlier versions of VirtualGL/TurboVNC show the same symptoms. A > variety of Nvidia driver versions also show the same symptoms. Running > vglrun with the +v verbose flag shows no errors. > This has been a bit of a tricky one to diagnose, so any thoughts would > be useful. > > Cheers > Sam. > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/virtualgl-users/221e98cb-694a-5df1-692c-ed317c785e12%40virtualgl.org.
