Just to clarify, i want to pass the second card (P2000) to an LXD container. Thus I dont want VirtualGL to touch this card.
--
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/ed565d1d-253e-4b78-aa7a-63a43903cf35%40googlegroups.com.
--
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/ed4f6846-665a-ffb8-56d2-da8c753b0208%40virtualgl.org.
The problem is that the device permissions are ultimately controlled by the kernel module. That means that they'll be reset whenever the module is loaded or unloaded, which can happen whenever the 3D X server starts or someone logs in/out locally. I'm not sure if there is a way to reliably override that. The only reasonable approach seems to be to grant system-wide permission to the devices while restricting the 3D X server to vglusers only. That's a pretty common way of configuring VirtualGL, actually.
To view this discussion on the web visit https://groups.google.com/d/msgid/virtualgl-users/CAAR6MGCbFwUeSmX%3D%2BKPC0jCrH368qJPTMMhGtz9FajchJ%2BcGmg%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/virtualgl-users/d34c63f0-e054-d897-ee4b-cde2be01a3a6%40virtualgl.org.
Try it, and let me know if you are able to make it work. I was not.
DRC
To view this discussion on the web visit https://groups.google.com/d/msgid/virtualgl-users/CAAR6MGDDmrmLaMSM14Rz8TCWZ8WSh-3GLv%3DUAmR1vrcJMxt%3DwA%40mail.gmail.com.