Skip to content

feat(compute): CPU overcommit and public bridge IFNAMSIZ fix - #20

Merged
Matheus-Thurler merged 2 commits into
mainfrom
fix/cpu-overcommit-requests
Aug 10, 2026
Merged

feat(compute): CPU overcommit and public bridge IFNAMSIZ fix#20
Matheus-Thurler merged 2 commits into
mainfrom
fix/cpu-overcommit-requests

Conversation

@Matheus-Thurler

Copy link
Copy Markdown
Contributor

Summary

  • Shared offerings omit full-core CPU requests so KubeVirt cpuAllocationRatio overcommits vCPUs; dedicated offerings keep Guaranteed QoS (request=limit=cores)
  • UI + seed offerings expose dedicated_cpu; deploy can opt into dedicated placement
  • Default public bridge renamed to vf-pub0 (IFNAMSIZ ≤15) so Multus can attach the shared network

Test plan

  • Create VM with shared offering on a busy worker — schedules without ErrorUnschedulable CPU pressure
  • Create VM / offering with dedicated_cpu — pod requests equal guest cores
  • Public network NAD uses vf-pub0; VM with public NIC reaches Running
  • Unit tests for CPU resource mapping pass

Shared VMs omit CPU request so KubeVirt cpuAllocationRatio
schedules denser; dedicated_cpu / *-dedicated offerings keep
Guaranteed QoS. UI checkbox + catalog seeds included.
virtfoundry-pub0 exceeds Linux IFNAMSIZ (15), so Multus cannot
create the shared bridge. Align bootstrap default with Helm.

SECURITY: wrong bridge name prevents public NAD attach and
leaves guests without the intended shared network path.
@Matheus-Thurler
Matheus-Thurler merged commit c83b04a into main Aug 10, 2026
3 checks passed
@Matheus-Thurler
Matheus-Thurler deleted the fix/cpu-overcommit-requests branch August 10, 2026 13:16
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