Skip to content

Reconcile NVIDIA state on every nspawn machine start - #589

Draft
hbc (bcho) with Copilot wants to merge 2 commits into
mainfrom
copilot/reconcile-nvidia-driver-state
Draft

Reconcile NVIDIA state on every nspawn machine start#589
hbc (bcho) with Copilot wants to merge 2 commits into
mainfrom
copilot/reconcile-nvidia-driver-state

Conversation

Copilot AI commented Aug 8, 2026

Copy link
Copy Markdown
Contributor

NVIDIA driver roots and CDI specifications could remain stale after host reboots or direct nspawn restarts, allowing containerd and kubelet to start before GPU runtime state was rebuilt.

  • Lifecycle reconciliation

    • Add an nspawn ExecStartPost hook for NVIDIA machines.
    • Reload the persisted machine configuration and reuse the existing idempotent SetupNVIDIA task.
    • Wait for machine D-Bus readiness before reconciliation.
  • Service readiness

    • Gate containerd and kubelet on unbounded-nvidia-ready.service.
    • Release the gate only after driver-root preparation and CDI generation succeed.
    • Keep initial bootstrap and repave on the existing managed setup path.
  • Failure handling

    • Propagate reconciliation failures to the nspawn unit so systemd retries the machine.
    • Leave non-NVIDIA machines unchanged.

Co-authored-by: bcho <1975118+bcho@users.noreply.github.com>
Copilot AI changed the title [WIP] Fix NVIDIA driver reconciliation on nspawn machine start Reconcile NVIDIA state on every nspawn machine start Aug 8, 2026
Copilot AI requested a review from hbc (bcho) August 8, 2026 02:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Reconcile NVIDIA driver root and CDI state on every nspawn machine start

2 participants