lassulus

hmm could be old CPU, but I cannot reproduce it here. I remember seeing this QEMU error but no memory of when and how I fixed it

hmm, we could try to add a script option to make-disk-image.nix (in nixpkgs) we then could use for example https://github.com/nix-community/disko to create whatever filesystem/bootloader combination we would want?

there is now an image builder in disko: https://github.com/nix-community/disko/blob/master/docs/reference.md#generating-disk-images-with-secrets-included-using-disko

you can't reference the systems own top-level in it's own dependencies (that's also unnecessary, because the system usually has itself available :)) what you need to do instead is create...

we can add nvme if those devices are used, probably the same for mmcblk. for some lvm raids we also need kernel modules. those we can set.

> I think nixos takes also care of loading raid kernel modules already when it's used. not all of them https://github.com/nix-community/disko/blob/master/tests/lvm-raid.nix#L10

yes, but afair the heuristic is incomplete and we still need to add extra modules

well now its markdown, so the first half is done

notice me senpai

hmm, not really. I guess you would need to get the disk data into nix first and then do some detection on it. Another possibility would be to generate multiple...