OpenBSD 8.0 adds ARM64 hibernation, Intel Arc graphics and 64-vCPU virtual machines
On October 20, 2026, OpenBSD ships its 61st release, and it is one of the rare ones where the hardware-support column matters as much as the hardening: ARM64 hibernation, Intel Arc GPUs, and vmd stepping up to 64 vCPUs per guest. If you self-host a pf router or a VM host on OpenBSD, this release earns an upgrade cycle.
October 20, 2026. OpenBSD ships its 61st release, 8.0, with the official song “The Simps on AI” — a pointed wink at the surrounding hype. 6.18.53. That is the Linux kernel version whose code the drm(4) graphics driver now tracks, which unlocks Intel Arc GPUs. 64. The number of vCPUs per virtual machine that vmd(8), the native hypervisor, can now drive. For a self-hoster, this release moves the needle on three fronts at once.
A project that hardens first, then adds hardware
OpenBSD stays true to its mantra: few remotely exploitable flaws in the default install, mechanisms like pledge and unveil to restrict processes, and an assumed line-by-line audit. Release 8.0 does not deviate — it adds structural defenses before it adds hardware.
The most notable is the randomized pmap direct map on amd64, alongside the kernel virtual address space growing from 4 GB to 512 GB. That randomization complicates attacks that lean on predictable kernel addresses, and the larger space changes the picture for GPUs: it becomes possible to map more than 4 GB of VRAM. Swap encryption, sped up by the CPU’s AES instructions, also advances on both amd64 and arm64.
ARM64 hibernation arrives, hardening follows
The most anticipated change is hibernation on ARM64. Until 8.0, an ARM laptop could only suspend to RAM; it can now write full state to disk and hibernate, a feature OpenBSD laptop users have wanted for years.
The hibernation work does not stop at the new feature: the commits harden the resume path by validating the size of chunks copied while unpacking the image, checking on-disk sizes against integer overflow, and preventing overreads of the image during wake. In other words, the new capability ships with the same audit level as the rest of the system — the project’s trademark.
Intel Arc GPUs, finally usable
The drm(4) driver is updated to Linux 6.18.53, and inteldrm(4) gains support for Intel Arc A-Series (DG2/Alchemist) cards. The amd64 address-space change matters here: it makes it possible to map more than 4 GB of VRAM, which was previously out of reach.
For a self-hoster, this is the missing argument for running Jellyfin or Frigate with hardware transcoding on a cheap Arc card under OpenBSD rather than Linux. Support is still young — a workaround already covers GuC timeouts on some Alder Lake systems — but the direction is clear.
vmd steps up to 64 vCPUs per guest
The most strategic point for homelabs is vmm(4)/vmd(8), the built-in hypervisor. OpenBSD 8.0 adds:
- multiprocessor support up to 64 vCPUs per VM;
- x2apic mode for guests;
- checksum offload and MSI/MSI-X interrupts on virtio devices;
- a reworked VM ownership model managed via files, and better qcow handling.
32-bit Linux guests are also fixed thanks to the missing lapic/ioapic modes. In practice, a heavy VM that used to cap out at a handful of vCPUs can now receive a real allocation, and virtual networking benefits from offload. For a homelab that hosts its services in a few VMs under vmd, this is the difference between “it fits” and “it runs comfortably.”
OpenBSD versus FreeBSD and Linux for self-hosting
The choice of a system for a home router or firewall often comes down to three names. OpenBSD brings the most-audited pf and a minimal surface; FreeBSD brings the same pf with a wider package ecosystem and better very-high-throughput networking; Linux brings the broadest hardware and software selection. 8.0 closes the hardware gap (Arc GPUs, ARM64 hibernation) without conceding anything on hardening — which is what makes it interesting for anyone who prioritizes security without giving up a modern homelab.
The twice-yearly cadence and the song’s irony
OpenBSD runs on a strict twice-yearly cadence: a release in April and one in October, each supported for a year. 8.0 is the 61st in that series, a number that recalls the longevity of a project founded in 1995 by Theo de Raadt.
The title of the official song, “The Simps on AI,” is no accident. The project has always kept a deliberate distance from fads — whether the feature race or, today, the frenzy around AI. That irony does not cost it technically: release 8.0 delivers hardening (randomized direct map), fresh hardware support (Arc GPUs, ARM64 hibernation) and a hypervisor scale-up (64 vCPUs) all at once. It is a lesson in balance: you can be skeptical of the hype without being behind on substance.
For the self-hoster, the twice-yearly rhythm means one simple thing: the 7.9 → 8.0 upgrade is a schedulable event with a clear support window. Those who stay on 7.9 have until the 8.1 release (April 2027) before support ends, but there is no reason to wait: sysupgrade handles the switch in minutes.
Secondary hardware follows too
The release does not stop at amd64 and arm64. On riscv64, the kernel now detects CPU extensions and advertises them via AT_HWCAP, adds support for the V vector extension and the Sstc timer, and ships the imsic(4) and aplic(4) drivers for the advanced RISC-V interrupt architecture. On laptops, suspend/resume improves machine by machine: the ufshci(4) controller now survives a suspend on the Samsung Galaxy Book4 Edge and the HONOR MagicBook Art 14 Snapdragon, and wakeup interrupts fix resume on IdeaPads.
Under the hood, the hardening is cumulative. Every hibernation image is validated against integer overflow, every chunk size is checked, and overreads are rejected — the kind of line-by-line audit that keeps OpenBSD’s default install nearly free of remotely exploitable holes. loongson, meanwhile, exits the catalog, incompatible with Clang 22.
Verdict
If you self-host a router or firewall on OpenBSD (pf, relayd), plan the 7.9 → 8.0 upgrade using the official guide: the hardening (randomized direct map, audited hibernation) is a free win, and sysupgrade makes the switch fast.
If your OpenBSD box is a VM host, vmd’s jump to 64 vCPUs is the main reason to migrate — test your heavy guests before reallocating cores, because the move to x2apic and the new lapic/ioapic modes can surface different behavior. If you are targeting Intel Arc transcoding, keep an eye on the errata: support works but is young, and a production homelab should stay on an already-validated card. In every case, note the retirement of the loongson architecture, incompatible with Clang 22 — if you still run it, stay on 7.9.