Hello, I don't really get why my config is not working and I don't understand why the errors appears. I used to make my VMs with NixOS 24.05 (apparently old) and wanted to update to 25.11.
I get this error:

Cannot build '/nix/store/61hn1fcn4y43gsgvikkfg2ycqx7mk0l2-kernel-modules-shrunk.drv'.
       Reason: builder failed with exit code 1.
       Output paths:
         /nix/store/rfy659qwndivmbfnz9xqidjglj5xkq3a-kernel-modules-shrunk
       Last 2 log lines:
       > Required modules: 9p 9pnet_virtio virtiofs virtio_pci virtio_blk virtio_balloon virtio_rng
       > Can not derive a closure of kernel modules because no modules were provided.
       For full logs, run:
         nix log /nix/store/61hn1fcn4y43gsgvikkfg2ycqx7mk0l2-kernel-modules-shrunk.drv

But my hardware-configuration.nix does provide some the modules. And even if I insert the named one, it does not change 🤔

{ config, lib, pkgs, modulesPath, ... }:

{
  imports =
    [ (modulesPath + "/profiles/qemu-guest.nix")
    ./disk.nix
    ];
  boot = {
    initrd.availableKernelModules = [ "ahci" "xhci_pci" "virtio_pci" "virtio_scsi" "sr_mod" "sd_mod"];
    initrd.kernelModules = [ ];
    kernelModules = [ "kvm-intel" ];
    kernelPackages = pkgs.linuxKernel.packages.linux_6_12;
    extraModulePackages = [ ];    
    
    loader.grub.efiSupport = lib.mkDefault true;
    loader.grub.efiInstallAsRemovable = lib.mkDefault true;    
    
  };
  swapDevices = [ ];
  networking.useDHCP = lib.mkDefault true;

  nix.settings.trusted-users = [ "admin"];
  nixpkgs.hostPlatform = lib.mkDefault "x86_64-linux";
}

I can still create VMs with the exact same configuration, but only changing the nixpkgs version in system.stateVersion and in the flake input url for the packages.

Specifically the nesting of drive -> luks/lvm_pv -> lvm_vg -> partition is pretty frustrating, and naming is really confusing so I'm having a hard time following it...

Like if I have main (drive) -> crypted (maybe crypted-main or luks-main if it needs to be unique) -> main (maybe vg-main if it needs to be unique) -> root and storage (drive) -> crypted (maybe crypted-storage or luks-storage) -> storage (or vg-storage) -> data

This works, but there's a lot of duplication and the structure is relatively unclear unless you really dig into it.
Is there a better way to do that or best practices around luks?

In reply to @belak:matrix.org
Playing around with it and using :lf . to experiment, yes - luks names need to be unique