| 14 Dec 2023 |
 matthewcroughan | is extendModules working correctly? | 10:15:08 |
| matthewcroughan | vmTools! | 10:36:18 |
| matthewcroughan | Figured it out, making a PR now, but it does increase the necessary memSize | 10:59:58 |
| matthewcroughan | maybe the VM should have zram :D | 11:00:24 |
| matthewcroughan | It is quite unfortunate, but there is no way to get a list of kernel module names for the filesystems involved in a nixos configuration | 11:02:00 |
| matthewcroughan | nixosConfigurations.pi3.config.boot.supportedFilesystems
[ "bcachefs" "bcachefs" "vfat" ]
| 11:02:21 |
| matthewcroughan | This is not a module list, even though it looks like one | 11:02:27 |
| matthewcroughan | https://github.com/NixOS/nixpkgs/tree/master/nixos/modules/tasks/filesystems | 11:02:47 |
| matthewcroughan | if the string "bcachefs" is found in the supportedFilesystems, it will add boot.initrd.availableKernelModules = [ "bcachefs" "sha256" "chacha20" "poly1305" ]; to the nixosConfiguration | 11:03:24 |
| matthewcroughan | maybe this is only really a problem for zfs, actually | 11:04:59 |
| matthewcroughan | * maybe this is only really a problem for zfs, actually, since it needs to be in the modulesTree | 11:05:09 |
| matthewcroughan | * maybe this is only really a problem for zfs, actually, since it needs to be in the rootModules | 11:05:17 |
| matthewcroughan | * maybe this is only really a problem for zfs, actually, since it needs to be in the rootModules and can't be dynamically loaded | 11:05:28 |
| matthewcroughan | zram inside of vm tests might be a big boost for all performance actually | 11:09:59 |
| matthewcroughan | I wonder why we don't to that | 11:10:02 |
| matthewcroughan | * I wonder why we don't do that to the nodes by default | 11:10:08 |
| matthewcroughan | lassulus: I enabled zram inside the disk builder VM, and it allowed me to install a closure with 1024M that I could only install with 2048M otherwise | 11:22:34 |
| matthewcroughan | * lassulus: I enabled zram inside the disk builder VM, and it allowed me to install a closure with 1024M that I could only install with 3GB otherwise | 11:22:40 |
 lassulus | uh weird | 11:23:16 |
| lassulus | but ok | 11:23:18 |
| matthewcroughan | @ | 12:09:31 |
| matthewcroughan | * https://github.com/nix-community/disko/pull/467 | 12:09:33 |
| matthewcroughan | I'm thinking something like disko.imageBuilder as an option namespace might begin to make sense, but not for this PR | 12:10:22 |
| matthewcroughan | disko.imageBuilder.memSize and disko.imageBuilder.extraRootModules | 12:11:02 |
 eyJhb | I've not been that productive today, but I'm very much enjoying the adventures of Matthew Croughan. And am currently having a hard time not playing with disko as well. | 12:14:28 |
| matthewcroughan | I'm astounded how fast those tests ran. | 12:15:20 |
| matthewcroughan | Hmm, it looks like f2fs won't work with this method even with extraRootModules = [ "f2fs" ] | 13:23:56 |
| matthewcroughan | since mkfs.f2fs doesn't exist unless f2fs-tools is in the initrd | 13:24:06 |
| matthewcroughan | It gets added to the initrd if the initrd is systemd-boot, but vmTools is too low level to benefit from that | 13:26:57 |
| matthewcroughan | Should we not just ditch vmTools altogether and use NixOS VMs? The vmTools machinery is shocking to me, it's like a whole other OS being maintained alongside NixOS | 13:27:27 |
