VirtualGL with NVIDIA GPU Operator in EKS (Invalid EGL device) #2171
Replies: 4 comments
-
|
@Mohamed-ben-khemis Can you run "kubectl get pods -n gpu-operator" to confirm that the driver is run from the operator? We don't install openGL libraries today from the driver-container. @elezar do you see any issues with the container-toolkit injecting necessary config files in this case? |
Beta Was this translation helpful? Give feedback.
-
|
@shivamerla Here are the results from running kubectl get pods -n gpu-operator: |
Beta Was this translation helpful? Give feedback.
-
|
This issue is stale because it has been open 90 days with no activity. This issue will be closed in 30 days unless new comments are made or the stale label is removed. To skip these checks, apply the "lifecycle/frozen" label. |
Beta Was this translation helpful? Give feedback.
-
|
This issue is stale because it has been open 90 days with no activity. This issue will be closed in 30 days unless new comments are made or the stale label is removed. To skip these checks, apply the "lifecycle/frozen" label. |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
-
Troubleshooting VirtualGL with NVIDIA GPU Operator in EKS
Issue Summary
Encountering issues with VirtualGL failing to detect GPUs within my EKS (Amazon Elastic Kubernetes Service) cluster using the NVIDIA GPU Operator. Despite confirming GPU presence with
nvidia-smi, runningglxgearswith GPU acceleration usingvglrunresults in the following error:Details
vglrun -d /dev/nvidia0 glxgearsIssue
VirtualGL (vglrun) fails to initialize the 3D environment (
glxgears) with an "Invalid EGL device" error when attempting GPU acceleration.Questions
Additional Information
nvidia-smiwithin the container confirms GPU presence and functionality.Beta Was this translation helpful? Give feedback.
All reactions