Add the vendor VFIO vGPU device backend - #364

Open

yummybomb wants to merge 19 commits into

hypeship/hypervisor-livenessfrom

hypeship/vendor-vfio-backend

Commits on Aug 13, 2026

Support vendor VFIO vGPU devices
yummybomb
committed
e1e4ba0
Account for consumed vGPU profiles
yummybomb
committed
54fca6e
Reject unowned vendor VFIO releases
yummybomb
committed
fa88aff
Check all vendor VFIO device paths
yummybomb
committed
b133bfe
Require usable mdev types for discovery
yummybomb
committed
abc5cf6
Test retained vendor VFIO assignments
yummybomb
committed
9d4ca54
Always delete the test instance during vGPU cleanup
yummybomb
committed
7fa40aa
Fall back to passthrough status when vGPU discovery fails
yummybomb
committed
08fd6a4
Keep vGPU placement available when an allocated type is unknown
yummybomb
committed
b614ab9
Report vendor VFIO availability per parent GPU and thread instance ownership through releases
yummybomb
committed
fb863f1
Keep vendor VFIO out of the create path until lifecycle integration
yummybomb
committed
c4c6ca3
Report vendor VFIO profile availability per free VF
yummybomb
committed
e8aaa14
Clarify vGPU availability semantics
yummybomb
committed
35a2c2a
Report conservative per-GPU vGPU profile capacity
yummybomb
committed
019c5b2
Revert "Report conservative per-GPU vGPU profile capacity"
yummybomb
committed
3fdc3f2
Retain vendor vGPU assignments after rollback failure
yummybomb
committed
c1fc02e
Degrade vendor VFIO discovery per VF instead of failing the host
yummybomb
committed
c6182c4
Degrade listProfiles per VF and document deliberate probe strictness
yummybomb
committed
580f7c2
Skip unreadable VFs in create placement like listProfiles does
yummybomb
committed
40252f8

Navigation Menu

Uh oh!

Add the vendor VFIO vGPU device backend - #364

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

Commits on Aug 13, 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