You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The standard x86_64/firecracker lane was pulling the guest kernel
straight from `nixpkgs#linuxPackages_latest`, which currently resolves
to 7.0.3. That is both a moving target and not yet bootable under PVM,
and it shipped without `CONFIG_DUMMY=y`, so the K3s install proof's
`ip link add port0 type dummy` aborted with `Error: Unknown device
type.` and the cluster never came up.
Introduce a small port-owned `nix/guest-kernel.nix` that takes
`linuxPackages_6_12.kernel` and overrides `structuredExtraConfig.DUMMY
= yes`, exposed through `legacyPackages.<sys>.linuxPackages-port-guest`
so callers retain `.kernel.dev` and `.kernel.modules`. The artifact
build/validate scripts now resolve the standard lane through that
attr, with `PORT_GUEST_KERNEL_ATTR` / `PORT_GUEST_KERNEL_MODULES_ATTR`
override hooks. PVM and aarch64 lanes are unchanged.
0 commit comments