Repository navigation
v20261026.01
·
126 commits
to main
since this release
What changed since v20261023.01
QEMU and firmware
- ci: every workflow step is one task, and Task from go.mod
- alpine 3.24 at today's digest: the apk locks and QEMU's build cache follow
Kernel
- ci: every workflow step is one task, and Task from go.mod
- versions: kernel 7.3, cosign v3.1.4, buildkit, git-lfs, snapshot and base images
Base image
- ci: every workflow step is one task, and Task from go.mod
- alpine 3.24 at today's digest: the apk locks and QEMU's build cache follow
Pins (versions.yaml)
alpine3.24pin294b683cb724→be2656061b53buildkit0.34.0→0.34.1cosignv3.0.6→v3.1.4debiantrixiepin913f6706df59→4c25275446cadebian-snapshot20261014T000000Z→20261026T000000Zgit-lfs3.8.0→3.8.1kernel7.3-rc5→7.3ubuntu26.04pinf144425ff09b→c098726dd9b9
6 more, none of them in the machine: tests, the lab, CI, tooling
- go-tools at main (dfcf2c1): sfw and taskgate as merged
- go-tools at main (5824d9a): refs runs the Task go.mod pins as go tool task
- ci: GitHub's runners for the builds, the fleet for what boots
- ci: report and lab on the bench fleet
- ci: the vsock step is the Taskfile's task
- vsock: load the module before looking for the node
Checkpoints taken against v20261023.01 still resume on this machine
fingerprint_sha256, the machine's contract, is unchanged: its machine type, shape,
devices and BIOS size are the same, whatever else below moved - a new QEMU of the same
machine type, a new kernel or firmware a boot reads. Each VM's own sizes come from
whoever runs the guests and are untouched by a release.
Changed, and not part of the fingerprint — checkpoints are unaffected:
kernel_sha256- was
1a83bc6a092d3789774ad3b047d2326ffd0c1aaebc2e7525f7d7bbbb6681ec0a(v20261023.01) - now
7d7521617c4bdcd2ce99db97718b43e9b8a4e9ab3d040c483c2ec165a14dd29f
- was
image_sha256- was
67e4e07fc7c14f411489954d7058c9144e8b77ee556ba70395fd7d772cd51b9e(v20261023.01) - now
165a5c9c18dd227f0e337ba37d577dbc9a4f5461358e3ea5ef0c0a32b99e4a0b
- was
The machine as it stood on this date.
version=v20261026.01
source_commit=0bb00ceb3a9911248426fd1c488e90ef89c6c24a
qemu_version=11.1.2
kernel_version=7.3
e2fsprogs_version=1.47.4
built=2026-10-26T22:15:31Z
qemu_sha256=65b8dfd15d168b8bbba2174a39ab333d05bd6c63c7897c0adf2fe5bcd7e45f69
kernel_sha256=7d7521617c4bdcd2ce99db97718b43e9b8a4e9ab3d040c483c2ec165a14dd29f
bios_sha256=23ac0e3077e1ffbdd6a074a572b11c450472c6f2cabe4e7ded214cdcb312e720
pvh_sha256=918ff03a118615c2f4611a5df2d9496aabe099b5cfaaf69e544ebf973305d59d
fingerprint_sha256=2bd7da6b35b14fd5bc35dc183af22389f3f1cb5456e88ab41c8ad6699d2f35a3
image_sha256=165a5c9c18dd227f0e337ba37d577dbc9a4f5461358e3ea5ef0c0a32b99e4a0b
v20261026.01 against v20261023.01
Measured on different hosts (AMD Ryzen 9 5900X 12-Core Processor, 24 CPUs; Intel(R) Xeon(R) 6975P-C, 16 CPUs): the times below compare two machines, not two releases.
image_sha256changed:67e4e07fc7c1→165a5c9c18ddkernel_sha256changed:1a83bc6a092d→7d7521617c4b
Feature matrix
| row | what changed | usable p50 / p95 (ms) |
|---|---|---|
| memory=anonymous,vsock=off,hotplug=off | fingerprint, usable p50 -6.3% | 381.8 / 745.3 → 357.6 / 376.4 |
| memory=anonymous,vsock=off,hotplug=on | fingerprint, usable p50 -8.6% | 413.1 / 879.8 → 377.5 / 400.1 |
| memory=anonymous,vsock=on,hotplug=off | fingerprint | 370.3 / 404.8 → 375.9 / 390.5 |
| memory=anonymous,vsock=on,hotplug=on | fingerprint, usable p50 +5.8% | 370.9 / 391.1 → 392.5 / 408.0 |
| memory=ceiling,vsock=off,hotplug=off | fingerprint | 361.8 / 391.8 → 374.3 / 387.8 |
| memory=ceiling,vsock=off,hotplug=on | fingerprint | 386.3 / 419.2 → 388.5 / 421.6 |
| memory=ceiling,vsock=on,hotplug=off | fingerprint | 375.4 / 554.8 → 372.0 / 404.7 |
| memory=ceiling,vsock=on,hotplug=on | fingerprint | 402.6 / 472.8 → 407.9 / 429.6 |
Image variants
No row changed beyond 5%.