!RROtHmAaQIkiJzJZZE:nixos.org

NixOS Infrastructure

424 Members
Next Infra call: 2024-07-11, 18:00 CEST (UTC+2) | Infra operational issues backlog: https://github.com/orgs/NixOS/projects/52 | See #infra-alerts:nixos.org for real time alerts from Prometheus.133 Servers

Load older messages


SenderMessageTime
12 Oct 2021
@hexa:lossy.networkhexaimage.png
Download image.png
13:55:11
13 Oct 2021
@piper:lutris.engineeringPiper McCorkle (she/her or they/them) joined the room.05:34:55
@piper:lutris.engineeringPiper McCorkle (she/her or they/them)What would the hurdles be to add qemu-binfmt to Hydra builders? I'm working on sparc64 and ppc64le bootstrap seeds and investigating the possibility of running the 3-stage build entirely on Hydra, so that they're actually just derived from the x86_64-linux seeds05:37:27
@r-burns:matrix.orgRyan BurnsThe one thing I would worry about is poorly written cross packages "working" on hydra because of binfmt, because executable from the wrong arch are being run via qemu. It's good for the builders to mirror a "vanilla" NixOS install for the sake of local reproducibility.05:47:05
@r-burns:matrix.orgRyan BurnsThis isn't an issue if it's possible to make binfmt opt-in on a per-package basis. Idk if that's possible or how hard that would be05:47:36
@piper:lutris.engineeringPiper McCorkle (she/her or they/them)Sadly you can't namespace binfmt definitions. Hmm...05:48:34
@piper:lutris.engineeringPiper McCorkle (she/her or they/them)I guess one way of namespacing would be do spin up an x86_64-linux NixOS VM with binfmt-misc inside, that way those systems don't need to have NixOS building05:54:42
@r-burns:matrix.orgRyan BurnsI wonder if it would be possible to do that and still get KVM accel05:56:30
@piper:lutris.engineeringPiper McCorkle (she/her or they/them)Should be, it's just a regular NixOS VM that happens to have binfmt_misc configured05:56:49
@piper:lutris.engineeringPiper McCorkle (she/her or they/them)Granted the KVM accel won't do much for the binary emulation, but things like Nix would be accelerated05:57:11
@piper:lutris.engineeringPiper McCorkle (she/her or they/them) * Granted the KVM accel won't do much for the binary emulation of the other arch, but things like Nix would be accelerated05:57:22
@r-burns:matrix.orgRyan BurnsTrue, probably wouldn't make much difference for total build time05:57:48
@piper:lutris.engineeringPiper McCorkle (she/her or they/them)Yep, especially if we spin up a VM and run the whole bootstrap process inside it05:58:31
@piper:lutris.engineeringPiper McCorkle (she/her or they/them) * Yep, especially if we spin up a VM and run the whole bootstrap process inside it, that way there's no boot overhead05:58:47
@vcunat:matrix.orgVladimír Čunát
In reply to @hexa:lossy.network
sent an image.
Oh, now I see... at the top of https://hydra.nixos.org/machines That looks like Hydra interpreting something meant as a comment.
07:46:07
@sternenseemann:systemli.orgsterni
In reply to @piper:lutris.engineering
What would the hurdles be to add qemu-binfmt to Hydra builders? I'm working on sparc64 and ppc64le bootstrap seeds and investigating the possibility of running the 3-stage build entirely on Hydra, so that they're actually just derived from the x86_64-linux seeds
you can build cross packages on hydra as well, I think that would be more worthwhile actually
08:08:22
@sternenseemann:systemli.orgsterniof course you then can't get binary cache for any native packages from hydra08:08:38
@piper:lutris.engineeringPiper McCorkle (she/her or they/them)The first stage of building bootstrap-tools is cross, but the second two stages are native08:09:01
@sternenseemann:systemli.orgsterniah right, yeah08:09:23
@sternenseemann:systemli.orgsterniI wonder how noticeable the performance cost of binfmt_misc would be for us; I think it would hurt us more than e. g. alpine which build riscv64 packages using it since we rebuild everything a lot08:10:37
@rick:matrix.ciphernetics.nlRick (Mindavi)There's also a chance of miscompilation due to bugs in the emulator or mismatched feature support, I think. Anyway, afaik it's also very slow08:22:22
@piper:lutris.engineeringPiper McCorkle (she/her or they/them)I am realizing from experience how slow it is... unfortunately I don't know if there's a better option without having a native buildbox, and it would be hard to get a dedicated buildbox for these exotic architectures08:23:32
@sternenseemann:systemli.orgsterniDoes it sound plausible that some Hydra builders are running a Kernel < 5.9?10:18:51
@vcunat:matrix.orgVladimír Čunát
In reply to @sternenseemann:systemli.org
Does it sound plausible that some Hydra builders are running a Kernel < 5.9?
t4b does. Generally we probably don't want to rely on that in builds.
10:20:24
@sternenseemann:systemli.orgsterni Vladimír Čunát: bingo :) https://hydra.nixos.org/build/154918256/nixlog/2 10:25:20
@sternenseemann:systemli.orgsternibut that's easy I'll just disable the test suite if the kernel is too old10:25:41
@vcunat:matrix.orgVladimír Čunát I suspected it's the only one with old kernel. But I don't think there's just hydra.nixos.org; we also want people to be able to reproduce the build, and 5.9 isn't that old nowadays. 10:27:59
@vcunat:matrix.orgVladimír Čunát * I suspected it's the only one with old kernel. But I don't think there's just hydra.nixos.org; we also want people to be able to reproduce the build, and 5.9 isn't that old nowadays (even though 5.10 has been default on NixOS for some time). 10:28:41
@toonn:matrix.orgtoonn Uhm, so I had a job aborted earlier and I started a new evaluation after pushing some more commits but most of the jobs have already "finished" as being aborted. Why is this and can I get them unaborted? 19:32:04
@toonn:matrix.orgtoonn *An evaluation aborted rather, I guess. 19:33:48

Show newer messages


Back to Room ListRoom Version: 6