[BUG]: GPU runner VM loses access to attached GPU

[justinthelaw]

Select Topic Area

Bug

Body

There seems to be times when the GPU runner fails to gain access to the passthrough or virtual T4 NVIDIA GPU.

Has anyone else run into this multiple times a day? Is there a better way to debug this to find a solution?

Snippet of my on-failure debug log:

Run echo "NVIDIA GPU Statistics:"; nvidia-smi
  echo "NVIDIA GPU Statistics:"; nvidia-smi
  echo ""; echo ""
  echo "K3S Node Statistics:"; sudo uds zarf tools kubectl describe nodes || true
  echo ""; echo ""
  echo "K3S Pod Statistics:"; sudo uds zarf tools kubectl get Pods --all-namespaces -o wide || true
  echo ""; echo ""
  echo "Memory Usage:"; free -h
  echo ""; echo ""
  echo "Top Processes by Memory:"; ps aux --sort=-%mem | head -n 10
  echo ""; echo ""
  echo "CPU Usage: $(top -bn1 | grep "Cpu(s)" | awk '{print $[2](https://github.com/defenseunicorns/uds-ai/actions/runs/12287402005/job/34289361194#step:10:2) + $4"%"}')"
  echo ""; echo ""
  echo "Top Processes by CPU:"; ps aux --sort=-%cpu | head -n 10
  echo "Disk Usage:"; df -h
  echo ""; echo ""
  shell: /usr/bin/bash -e {0}

NVIDIA GPU Statistics:
No devices were found

Censored snippet of my entire workflow file:

name: Test

on: <CENSORED>

# Permissions for the GITHUB_TOKEN used by the workflow.
permissions: <CENSORED>

# Abort prior jobs in the same workflow / PR
concurrency: <CENSORED>

jobs:
  test:
    runs-on: <CENSORED>-linux-x64-gpu
    timeout-minutes: 60

    # NOTE: all steps must be run with `sudo` permissions due to a) the need for standing up a K3S cluster and
    #       b) <CENSORED>
    steps:
      - name: Checkout Repository
        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2

      - name: Setup Node
        uses: actions/setup-node@39370e3970a6d050c480ffad4ff0ed4d3fdee5af # v4.1.0
        with:
          node-version-file: "<CENSORED>"
          cache-dependency-path: "<CENSORED>"

      - name: <CENSORED>
     
      - name: Setup NVIDIA Container Toolkit and <CENSORED>
        run: |
          sudo <CENSORED> nvidia-ctk --no-progress


      - name: <CENSORED>

      - name: Log System Statistics
        if: ${{ failure() }}
        run: |
          echo "NVIDIA GPU Statistics:"; nvidia-smi
          echo ""; echo ""
          echo "K3S Node Statistics:"; sudo uds zarf tools kubectl describe nodes || true
          echo ""; echo ""
          echo "K3S Pod Statistics:"; kubectl get Pods --all-namespaces -o wide || true
          echo ""; echo ""
          echo "Memory Usage:"; free -h
          echo ""; echo ""
          echo "Top Processes by Memory:"; ps aux --sort=-%mem | head -n 10
          echo ""; echo ""
          echo "CPU Usage: $(top -bn1 | grep "Cpu(s)" | awk '{print $2 + $4"%"}')"
          echo ""; echo ""
          echo "Top Processes by CPU:"; ps aux --sort=-%cpu | head -n 10
          echo "Disk Usage:"; df -h
          echo ""; echo ""

      - name: Setup SSH Debugging Session
        uses: mxschmitt/action-tmate@e5c7151931ca95bad1c6f4190c730ecf8c7dde48 # v3.19
        if: ${{ failure() }}
        with: <CENSORED>

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐