Repository navigation
feat(zone-kvm): enable Intel KVM in the zone-kvm kernel - #287
Merged
Merged
Conversation
The zone-kvm fragment only enabled CONFIG_KVM_AMD, so on Intel hosts zones running this kernel have no /dev/kvm. Edera's CI runners are moving from AMD to Intel nodes because nested KVM under Hyper-V is broken on AMD EPYC, and the KVM runners pin this kernel. CONFIG_KVM_INTEL depends on IA32_FEAT_CTL, which CPU_SUP_INTEL=y in zone.config already selects. Refs ENGINFR-56 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
graysonguarino
marked this pull request as ready for review
October 16, 2026 16:00
graysonguarino
requested review from
alexandermerritt,
azenla,
bleggett,
kaniini and
tycho
as code owners
October 16, 2026 16:00
azenla
approved these changes
Oct 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds
CONFIG_KVM_INTEL=ytoconfigs/x86_64/zone-kvm.fragment.config, so thezone-kvmkernel gets KVM on Intel hosts as well as AMD.Why
edera-dev/infra#375 moves all of Edera's CI runners from AMD to Intel AKS nodes, because nested KVM under Hyper-V is broken on AMD EPYC (COR-1). The
edera-16-kvmandedera-24-kvmrunners pinzone-kvm-kernel, and today that kernel has onlyCONFIG_KVM_AMD. KVM is built in, not a module, so on Intel nodes those runners would start without/dev/kvminstead of failing.CONFIG_KVM_INTELdepends onIA32_FEAT_CTL.CONFIG_CPU_SUP_INTEL=yinzone.configalready selects it, so the symbol should stick. Theverify-config.pystickiness check will fail the build if it doesn't.After merge
Bump the
dev.edera/kerneldigest inedera-16-kvm.yamlandedera-24-kvm.yamlon edera-dev/infra#375 to the newzone-kvm-kernelbuild.Refs ENGINFR-56