| 7 Feb 2025 |
 ElvishJerricco | so no action required, it seems | 18:02:15 |
 Arian | good callout though | 18:02:24 |
|  terrorjack joined the room. | 22:46:14 |
| 8 Feb 2025 |
| terrorjack set a profile picture. | 02:24:25 |
| terrorjack removed their profile picture. | 02:24:59 |
|  @marcel:envs.net joined the room. | 20:27:51 |
| 9 Feb 2025 |
|  infowski joined the room. | 22:34:51 |
|  @tired:fairydust.space left the room. | 22:50:18 |
| 11 Feb 2025 |
| Arian | hmm I wanna try to get systemd-vmspawn work | 11:57:38 |
| Arian | it looks for firmware config in /usr/share/qemu/firmware and /etc/qemu/firmware
which obviously doesn’t work. but I have two options here:
- Make it in NixOS config to re-expose ${qemu}/share/qemu to /etc/qemu
- Patch systemd and add a dependency on qemu
| 11:59:20 |
| Arian | option 1 seems better right? it’s calling qemu as a binary — it just needs to be able to discover the configs shipped with qemu | 11:59:45 |
| ElvishJerricco | Depends on if you want to use this within the nix build sandbox, I guess | 12:02:01 |
 K900 | Can you not give it a firmware at runtime? | 12:02:08 |
| K900 | Also IIRC libvirt does something like that already with /run/libvirt/firmware | 12:03:00 |
| K900 | So maybe there should be one standard place for that | 12:03:10 |
| Arian | yeh there’s a —firmware argumentb | 12:03:41 |
| Arian | but by default it points to /etc/qemu/firmware | 12:03:50 |
| Arian | it’s just annoying to have to pass that in explicitly | 12:03:57 |
| Arian | qemu needs to be installed in environment.systemPackages anyway. so might as well expose /etc/qemu/firmware I guess | 12:04:14 |
| Arian |
$ systemd-vmspawn --linux /run/current-system/kernel --tpm no --initrd /run/current-system/initrd
░ Spawning VM nixos-stuff on /mnt/Projects/nixos-stuff.
░ Press Ctrl-] three times within 1s to kill VM.
Couldn't find OVMF firmware blob with Secure Boot support, falling back to OVMF firmware blobs without Secure Boot support.
qemu-kvm: -device vmgenid,guid=cc36b80c-97fa-4233-ad99-c246a2f48443: 'vmgenid' is not a valid device model name
| 12:13:06 |
| Arian | urghh does qemu-kvm-aarch64 not support vmgenid? | 12:13:17 |
 Alyssa Ross | It's ACPI — do aarch64 VMs use ACPI? | 12:16:38 |
 raitobezarius | I think I saw ACPI support for aarch64 in the kernel recently | 13:51:45 |
| Alyssa Ross | Oh yeah I'm not saying you can't do ACPI on aarch64 | 13:58:52 |
 antifuchs | I have a nixos test that tries to assert that a socket unit startup doesn't finish until a certain condition is met. If I do a machine.start() in the test code, the test waits forever until the socket's execstart finishes; is there a way to get backdoor.service not to depend on that socket being fully up? | 15:28:28 |
| antifuchs | * I have a nixos test that tries to assert that a socket unit startup doesn't finish until a certain condition is met. If I do a machine.start() in the test code, the test waits forever until the socket's execstart finishes (which it won't, because the condition for it finishing happens later in the test); is there a way to get backdoor.service not to depend on that socket being fully up? | 15:29:35 |
| antifuchs | trying to do it with the initrdBackdoor, but that feels kinda wonky | 15:33:05 |
| antifuchs | hrm, nope: now switch_root() hangs indefinitely (: | 15:35:14 |
| antifuchs | * I have a nixos test that tries to assert that a socket unit startup doesn't finish until a certain condition is met. If I do a machine.start() in the test code, the test waits forever until the socket's ExecStartPre finishes (which it won't, because the condition for it finishing happens later in the test); is there a way to get backdoor.service not to depend on that socket being fully up? | 16:09:45 |
 aloisw | In reply to @k900:0upti.me
Also IIRC libvirt does something like that already with /run/libvirt/firmware /run/libvirt/nix-ovmf, also /var/lib/qemu/firmware lately (which causes issues). | 18:11:12 |
