| 23 Oct 2023 |
 fricklerhandwerk | * Robert Hensing (roberth) wrote a proposal on changing that: https://github.com/NixOS/nixpkgs/issues/185234
I think it should be implemented as written.
| 09:42:24 |
| fricklerhandwerk | I’ll only be in the meeting for the first half hour today because of a conflicting appointment | 11:16:47 |
 asymmetric | In reply to @fricklerhandwerk:matrix.org
I’ll only be in the meeting for the first half hour today because of a conflicting appointment thanks! i'ld love to discuss some of this stuff on thu (i can't attend today) | 12:55:00 |
| asymmetric | oops, was meant as a reply to the post above 😉 | 12:55:11 |
| 25 Oct 2023 |
|  @federicodschonborn:matrix.org changed their profile picture. | 00:13:04 |
 fsbof | I've been upgrading NixOS. On the good side, I've had options that other distros didn't offer but I still broke stuff! Badly! I finally tracked down that "virtualisation.libvirtd.qemu.ovmf.package = pkgs.OVMFFull" updated the version of OVMF_CODE.fd which subsequently caused virtual domains using UEFI to no longer successfully boot. This is likely related to a change in size of the nvram, and starting the domains with the virsh --reset-nvram option allowed them to boot. I also needed to then go into the UEFI config and update the display resolution in order to see the actual boot process. This took hours to work through - is it worth documenting anywhere for others because I couldn't find much. Also I am still on NixOS 22.05 - Trying to get to 23.05, so my issues maybe 'out-of-date' but they got me! | 10:00:05 |
 infinisil | fsbof: Sounds like that should be added (if it's not already) to the 23.05 release notes. There's a breaking changes section | 10:02:31 |
| fsbof | I did look in the release notes and could only find two mentions of OVMF changes in 22.11 and 21.11 | 10:06:09 |
| fsbof | I also managed to break it with out needing to upgrade the NixOS version - just by add the line above to configuration.nix in 22.05 when it previously didn't exist. | 10:08:34 |
| fsbof | I guess what I am saying is it could happen in two situations | 10:08:56 |
| infinisil | Making a PR to the release notes for both cases would be good imo | 10:09:42 |
| infinisil | For the the first release where each became a problem | 10:10:07 |
| fsbof | Can you guide me through the process - happy to do it, just haven't done it before | 10:10:13 |
 raitobezarius | Please include details about how did you narrow down to this, it's complicated when release notes misidentify the root cause | 10:10:32 |
