Skip to content

Support vendor VFIO vGPU devices - #321

Draft
yummybomb wants to merge 1 commit into
hypeship/generalize-vgpu-devicefrom
hypeship/vendor-vfio-vgpu
Draft

Support vendor VFIO vGPU devices#321
yummybomb wants to merge 1 commit into
hypeship/generalize-vgpu-devicefrom
hypeship/vendor-vfio-vgpu

Conversation

@yummybomb

@yummybomb yummybomb commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

summary

  • detect NVIDIA's mdev and vendor-specific VFIO frameworks at runtime
  • discover vendor VFIO virtual functions and parse creatable_vgpu_types
  • assign and release profiles through current_vgpu_type with least-loaded-GPU placement
  • preserve active assignments and clear orphaned assignments by checking vendor VFIO device handles
  • document both frameworks and verify that vendor VFIO vGPUs retain the existing standby rejection

Stacked on #322, which contains the framework-neutral lifecycle refactor. Live host validation will follow after host provisioning supports vendor-specific VFIO.

tests

  • go test -race ./lib/devices ./lib/instances -run 'VendorVFIO|CreatableVGPU|StoredVGPU|StandbyRejectsVendorVFIO' -count=1
  • go test ./lib/devices ./lib/hypervisor/qemu ./lib/resources -count=1
  • go test ./cmd/api ./cmd/api/api ./lib/instances ./integration -run '^$' -count=1
  • go vet ./cmd/api ./lib/devices ./lib/hypervisor/qemu ./lib/instances ./lib/resources

@yummybomb
yummybomb force-pushed the hypeship/vendor-vfio-vgpu branch from 199b1d1 to a93d009 Compare July 28, 2026 21:32
@yummybomb
yummybomb changed the base branch from main to hypeship/generalize-vgpu-device July 28, 2026 21:32
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.

1 participant