Skip to content

feat(zone): build new zone kernel for kvm builds - #255

Open
marly-edera wants to merge 4 commits into
mainfrom
msalazar/kvm-zone-kernel
Open

marly-edera wants to merge 4 commits into
mainfrom
msalazar/kvm-zone-kernel

Conversation

@marly-edera

@marly-edera marly-edera commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

https://linear.app/edera/issue/ENGINFR-13/enable-action-runners-on-the-edera-cluster

Adding the following kernel build flags:

  • CONFIG_KVM=y
  • CONFIG_KVM_AMD=y
  • CONFIG_BLK_DEV_NBD=y

These are required for migrating the e2e builds for protect.

kaniini
kaniini previously approved these changes Sep 16, 2026

@kaniini kaniini left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

approved, but i am not sure why a zone kernel would need its own instance of the KVM hypervisor...

@alexandermerritt

alexandermerritt commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

@marly-edera please reason about this before merging, I agree with @kaniini.

Additional kernel configs and builds add to the work we put in to trim them down, and to testing.

Is there a linear issue associated with this? Other context?

@marly-edera

Copy link
Copy Markdown
Contributor Author

@kaniini

The e2e tests in the protect repo can't be run on our dogfood cluster because the current zone kernel doesn't include the necessary kvm or nbd kernel... stuff sorry I'm not really well versed in linux kernel dev I don't know what to call it. This is to close out the last set of jobs in that repo that run on github hosted runners.

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.

3 participants