Add the vendor VFIO vGPU device backend - #364

Open

yummybomb wants to merge 24 commits into

hypeship/hypervisor-livenessfrom

hypeship/vendor-vfio-backend

Commits on Aug 21, 2026

Support vendor VFIO vGPU devices
yummybomb
authored
58bbeb8
Account for consumed vGPU profiles
yummybomb
authored
e2cbf6c
Reject unowned vendor VFIO releases
yummybomb
authored
4b8fbaf
Check all vendor VFIO device paths
yummybomb
authored
8d84cbd
Require usable mdev types for discovery
yummybomb
authored
6fb8cdc
Test retained vendor VFIO assignments
yummybomb
authored
a924f15
Always delete the test instance during vGPU cleanup
yummybomb
authored
e2d7010
Fall back to passthrough status when vGPU discovery fails
yummybomb
authored
f17f215
Keep vGPU placement available when an allocated type is unknown
yummybomb
authored
820552c
Report vendor VFIO availability per parent GPU and thread instance ownership through releases
yummybomb
authored
3a331f8
Keep vendor VFIO out of the create path until lifecycle integration
yummybomb
authored
a19a35f
Report vendor VFIO profile availability per free VF
yummybomb
authored
99467d5
Clarify vGPU availability semantics
yummybomb
authored
748b9b6
Report conservative per-GPU vGPU profile capacity
yummybomb
authored
a21fa19
Revert "Report conservative per-GPU vGPU profile capacity"
yummybomb
authored
7f4a8bc
Retain vendor vGPU assignments after rollback failure
yummybomb
authored
5dcf26b
Degrade vendor VFIO discovery per VF instead of failing the host
yummybomb
authored
3de1649
Degrade listProfiles per VF and document deliberate probe strictness
yummybomb
authored
46476c4
Skip unreadable VFs in create placement like listProfiles does
yummybomb
authored
b68c2c3
Degrade mdev discovery per VF instead of failing the host
yummybomb
authored
821d177
Warn when reconcile preserves an unclaimed in-use vGPU
yummybomb
authored
283be51
Document wedged-VF forensics and SR-IOV cycle remediation
yummybomb
authored
00bf116
Tolerate processes exiting mid-scan in the open-VFIO-handle scan
yummybomb
authored
227e687
Skip mdev release for an assignment with no device
yummybomb
authored
6f98055

Navigation Menu

Uh oh!

Add the vendor VFIO vGPU device backend - #364

Add the vendor VFIO vGPU device backend#364
yummybomb wants to merge 24 commits into
hypeship/hypervisor-livenessfrom
hypeship/vendor-vfio-backend

Commits on Aug 21, 2026

Support vendor VFIO vGPU devices

Account for consumed vGPU profiles

Reject unowned vendor VFIO releases

Check all vendor VFIO device paths

Require usable mdev types for discovery

Test retained vendor VFIO assignments

Always delete the test instance during vGPU cleanup

Fall back to passthrough status when vGPU discovery fails

Keep vGPU placement available when an allocated type is unknown

Report vendor VFIO availability per parent GPU and thread instance ownership through releases

Keep vendor VFIO out of the create path until lifecycle integration

Report vendor VFIO profile availability per free VF

Clarify vGPU availability semantics

Report conservative per-GPU vGPU profile capacity

Revert "Report conservative per-GPU vGPU profile capacity"

Retain vendor vGPU assignments after rollback failure

Degrade vendor VFIO discovery per VF instead of failing the host

Degrade listProfiles per VF and document deliberate probe strictness

Skip unreadable VFs in create placement like listProfiles does

Degrade mdev discovery per VF instead of failing the host

Warn when reconcile preserves an unclaimed in-use vGPU

Document wedged-VF forensics and SR-IOV cycle remediation

Tolerate processes exiting mid-scan in the open-VFIO-handle scan

Skip mdev release for an assignment with no device