Skip to content
Tuesday, October 20, 2026AboutContactRSS
Tech News

OpenBSD 8.0 Released With Intel Arc Support and Expanded Virtualization

The latest release of the security-focused operating system adds support for modern graphics cards and increases virtual CPU limits while maintaining its long-standing security record.

Illustration: A sleek black graphics card with exposed copper cooling pipes rests on a wooden desk next to a small white server tower.
AI-generated illustration: Threat Times

Key points

  • OpenBSD 8.0 introduces support for Intel Arc A-Series graphics cards and expands kernel virtual address space on AMD64 systems.
  • The release allows up to 64 virtual CPUs per guest machine and includes updates to LibreSSL and OpenSSH.
  • Support for the Loongson architecture has been retired due to compatibility issues with the Clang 22 compiler.

OpenBSD founder Theo de Raadt announced the release of OpenBSD 8.0 on the project’s announcements mailing list, marking the project’s 61st release and continuing its schedule of semiannual releases dating back to 1996. This update introduces significant hardware support improvements while emphasizing the system’s continued security integrity.

The release highlights new compatibility with Intel Arc A-Series graphics cards, specifically the DG2 or Alchemist series, and expands the kernel virtual address space on AMD64 architectures from 4 GB to 512 GB. These changes enable the system to map more than 4 GB of VRAM, improving performance for users with modern high-end graphics hardware.

Technical Updates and Architecture Changes

According to Ars Technica, the update includes several technical enhancements beyond graphics support. RISC-V improvements now include kernel support for the ‘V’ vector extension and support for the Advanced Interrupt Architecture. Wireless network capabilities have also been expanded, with additions to the qwx(4) driver supporting 802.11n and 40 MHz channels.

Virtualization features receive notable upgrades in OpenBSD 8.0. The system now supports up to 64 virtual CPUs per guest virtual machine. The vmm/vmd virtualization stack also received improvements.

Security Record and Software Updates

De Raadt stated that the project remains proud of OpenBSD’s record of more than thirty years with only two remote holes in the default install. This claim underscores the operating system’s reputation for rigorous security auditing and proactive vulnerability mitigation strategies.

The release includes security and internal improvements for LibreSSL 4.4.0 and OpenSSH 10.6. These updates ensure that core cryptographic and remote access components remain aligned with current security standards.

Architectural Support Adjustments

OpenBSD 8.0 retires support for the Loongson architecture. The port was discontinued because it stopped working with the Clang 22 compiler.

Users relying on Loongson hardware will need to transition to a different operating system or an older version of OpenBSD that supports the architecture.

What should you do?

Administrators planning to upgrade to OpenBSD 8.0 should review the release notes for changes affecting their specific hardware configurations, particularly regarding graphics and virtualization settings. Users with Intel Arc cards should verify driver compatibility before deploying the update in production environments.

FAQ

Q: What new hardware support does OpenBSD 8.0 include?

A: OpenBSD 8.0 adds support for Intel Arc A-Series graphics cards and improves RISC-V kernel support for the ‘V’ vector extension and Advanced Interrupt Architecture.

Q: Did OpenBSD 8.0 introduce any new security vulnerabilities?

A: The project highlights its record of only two remote holes in the default install over thirty years.

Q: Which architecture support was removed in OpenBSD 8.0?

A: Support for the Loongson architecture was retired because the port stopped working with the Clang 22 compiler.

What to do and how to stay safe

  • Hardware-backed key storage prevents attackers from extracting credentials even if they gain physical access to the device.
  • Mobile device management enforces consistent security policies across diverse operating systems and hardware configurations.
  • Application sandboxing limits the damage a compromised app can cause by restricting its access to other data and system resources.

Mobile device security requires a layered approach combining hardware, software, and policy controls. Enable encryption, use strong passcodes, and keep your operating system updated to protect your data.

Step-by-step guide: Mobile Device Security: How to Protect Data Beyond Passwords

General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.

Sources

  1. Ars Technica
Related articles