• Thread Author
VirtualBox’s long march into the ARM era has reached a major milestone: version 7.2 delivers true ARM-on-ARM virtualization, a redesigned UI, macOS Metal-backed 3D experiments, and a broad set of stability and compatibility fixes that make this release the most consequential VirtualBox update of the last two years. (forums.virtualbox.org, techspot.com)

A neon-lit cyberpunk desk with a glowing cube connected to a digital screen displaying app icons.Background​

VirtualBox has been a ubiquitous free and open-source virtualization platform for desktop users, developers, and testers for years. Historically focused on x86/x86_64 hosts and guests, the project added early experimental Apple Silicon support in 2022 but stopped short of offering full, native virtualization for ARM guests on ARM hosts. That left a gap for users of Apple M-series Macs and Windows/ARM laptops who wanted to run ARM-native virtual machines with near-native performance. VirtualBox 7.2 is the first release in the stable 7.2 series to bridge that gap in a meaningful way. (virtualbox.org, 9to5linux.com)
This release is being distributed as a standard VirtualBox package and is accompanied by an updated Oracle user guide for 7.2 and an expanded changelog; the stable 7.2 series was announced and landed in mid-August 2025. (docs.oracle.com, techspot.com)

What’s new at a glance​

  • Full ARM-on-ARM virtualization: Windows 11/ARM and other ARM guests can be virtualized on ARM hosts (Windows/ARM, macOS on Apple Silicon, and Linux ARM). Guest Additions for Windows/ARM are supplied, including a WDDM graphics driver with basic 2D/3D mode support. (forums.virtualbox.org, techspot.com)
  • UI redesign: Global tools moved from the hamburger menu to a left-side vertical taskbar; VM tools are now horizontal tabs over the right-hand panel to reduce menu scavenger hunts and improve usability. (forums.virtualbox.org, techspot.com)
  • macOS/Arm experimental 3D via DXMT: A Metal-based Direct3D implementation (DXMT) replaces the earlier non-working DXVK-on-MoltenVK approach for 3D acceleration on Apple Silicon hosts. 3D acceleration on Intel-based macOS hosts has been removed. (techspot.com, omgubuntu.co.uk)
  • Linux host video decoding acceleration: When 3D acceleration is enabled, Linux hosts gain hardware-accelerated video decoding inside guests. (techspot.com, omgubuntu.co.uk)
  • Compatibility and kernel support: Initial support for Linux kernel 6.16 and 6.17, fixes for nested virtualization on Intel CPUs, and numerous bug fixes across audio, storage, and UEFI/BIO S subsystems. (forum.virtualbox.org, 9to5linux.com)
  • Important migration note: Saved states and snapshots for ARM VMs created under VirtualBox 7.1 are incompatible with 7.2 — shut down or export VMs before upgrading. (forums.virtualbox.org, techspot.com)
These are the headline items; the full changelog includes many smaller but consequential fixes and improvements for day-to-day use. (techspot.com)

Deep dive: ARM-on-ARM virtualization — what changed and why it matters​

Why ARM-on-ARM virtualization matters​

ARM silicon (Apple M-series, Qualcomm Snapdragon laptops, and various Linux ARM SBCs) is now common in consumer and developer hardware. Running ARM-native operating systems as VMs on ARM hosts is fundamentally different from emulating x86 on ARM: virtualization lets the guest run the same ISA as the host, preserving CPU instruction semantics and enabling far higher performance with lower power consumption compared to full ISA translation. VirtualBox’s 7.2 moves from experimental Apple Silicon x86 emulation toward true ARM virtualization on native ARM platforms. This is a major platform-level upgrade for workflows that target ARM-native builds, testing, and software validation. (forums.virtualbox.org, linuxiac.com)

What VirtualBox 7.2 delivers for ARM hosts and guests​

  • Windows 11/ARM guests: Full virtualization support for Windows 11/ARM guests is now available, including an initial Guest Additions package and a WDDM graphics driver with 2D and 3D modes. This reduces the friction of running Windows-on-ARM builds for developers and testers. (forums.virtualbox.org, techspot.com)
  • ARM Guest Additions features: Shared folders, basic guest integration, and initial graphics support are present for Windows/ARM guests — the features that make desktop-style VM usage practical beyond headless CI or server workloads. (forums.virtualbox.org, linuxiac.com)
  • ACPI and vboxwebsrv: ACPI is enabled for ARM VMs and vboxwebsrv is included in ARM packages, improving manageability and compatibility for many guests. (forums.virtualbox.org)

Practical implications and limitations​

  • Not an x86/ARM binary translator: This is important — VirtualBox’s ARM virtualization does not magically run x86 or x64 guests with native performance on ARM hosts. Running legacy x86 Windows inside an ARM VM still requires OS-level emulation (for example, Microsoft’s x86-emulation layers for Windows/ARM), which incurs substantial performance penalties. Users must plan to run ARM-native guest OSes for best results. (windowsforum.com)
  • Hardware and driver dependency: Performance and feature parity will vary by host SoC (M1 vs M2 vs Snapdragon) and by guest OS’s driver support. The WDDM driver is an important step, but expect limitations in driver maturity, GPU acceleration, and device support in early 7.2 builds. Real-world benchmarks remain limited at launch; users should treat initial ARM virtualization as usable for development and testing, but not yet a drop-in replacement for mature x86 virtualization workflows. Benchmarks and production readiness remain to be proven. (linuxiac.com, phoronix.com)

UI and usability: a long-overdue polish​

VirtualBox’s UI has long been criticized as cluttered and inconsistent. Version 7.2 continues the UI modernization work started in the 7.1 cycle by moving a number of frequently used controls out of the hamburger menu and into a left-side global tools taskbar and a set of horizontal tabs in the Machines view. For users who’ve previously hunted through nested menus, this is a concrete improvement in discoverability and workflow speed. (forums.virtualbox.org, omgubuntu.co.uk)
Key UI changes:
  • Left vertical taskbar with clear sections: Home, Machines, Extensions, Media, Network, Cloud, and Resources.
  • Horizontal VM tools tabs for the currently selected VM, directly above the right-hand panel.
  • Polished Preferences and Settings pages, plus small but practical extras (example: a global checkbox to make a Shared Folder available across all VMs). (techspot.com, omgubuntu.co.uk)
These changes are incremental but meaningful — they don’t reinvent VirtualBox, but they make the app less frustrating for daily use.

Graphics and multimedia: DXMT, Linux decoding acceleration, and the Intel Mac caveat​

macOS (Apple Silicon) — DXMT experimental 3D​

VirtualBox 7.2 introduces an experimental pathway for 3D acceleration on Apple Silicon hosts using DXMT, a Metal-based Direct3D 10/11 implementation. This is a strategically sensible choice: leveraging Metal directly through a purpose-built translation layer (DXMT) avoids the instability and performance limits of earlier DXVK-on-MoltenVK attempts. Expect experimental 3D support to improve guest compatibility for Direct3D workloads on Apple Silicon hosts, but don’t expect full parity with mature commercial hypervisors immediately. (techspot.com, omgubuntu.co.uk)
Important warning: 3D acceleration support on Intel-based macOS hosts has been removed in 7.2. If you rely on VirtualBox 3D acceleration on an Intel Mac, do not upgrade to 7.2 until you’ve confirmed alternative paths; staying on the 7.1.x series may be necessary for those users. (techspot.com)

Linux hosts — hardware-accelerated video decoding (with 3D enabled)​

On Linux hosts, VirtualBox 7.2 adds video decoding acceleration inside VMs when 3D acceleration is enabled. For multimedia-heavy guests, this should reduce CPU load and improve playback smoothness. This is a substantial quality-of-life improvement for Linux developers and testers who run media-rich guests. However, the feature is gated by 3D support and host GPU capabilities, and real-world improvements will depend on host drivers and guest configuration. (techspot.com, omgubuntu.co.uk)

Compatibility, migration, and upgrade guidance​

  • Saved-state incompatibility for ARM VMs: Arm VM saved states and snapshots from VirtualBox 7.1 are incompatible with 7.2. Before upgrading, shut down any ARM VMs (do not leave them in saved/suspended state), or export them (OVA/OVF) to preserve ability to migrate. This is one of the clearest upgrade pitfalls. (forums.virtualbox.org, techspot.com)
  • Extension Pack and licensing: The Extension Pack remains a separate install (PUEL) for certain proprietary features. Review your use of the extension pack if you depend on USB 2/3 passthrough, RDP, or other features that may be in the proprietary bundle. The NVMe controller emulation moving into the open-source base package is a welcome change for those who need NVMe without extension pack constraints. (techspot.com)
  • Kernel and distro compatibility: 7.2 adds initial compatibility for Linux kernels 6.16 and 6.17. Linux hosts running very recent kernels may still need temporary workarounds for module loading in certain setups, and Secure Boot systems may require manual module signing during installation. Test upgrades in an isolated environment before rolling out to production systems. (forum.virtualbox.org, phoronix.com)
  • Nested virtualization and CPU feature passthrough: Nested virtualization fixes on Intel CPUs and improved x86_64-v3 instruction reporting when using Windows Hyper-V as the engine will help advanced nested setups, but users relying on specific CPU features must validate on their specific hardware. (forums.virtualbox.org, techspot.com)

Real-world expectations and performance (a cautious assessment)​

VirtualBox 7.2’s ARM-on-ARM virtualization enables far better performance for ARM-native guests compared to prior x86 emulation approaches — in theory. In practice, performance will vary:
  • On Apple Silicon (M1/M2) hosts, VirtualBox performance should benefit from the efficiency and single-ISA semantics; however, host GPU/driver maturity, Guest Additions optimization, and DXMT’s early state will temper expectations for graphics-heavy workloads. (linuxiac.com, omgubuntu.co.uk)
  • On Windows/ARM laptops (Snapdragon-based or other vendors), the VM experience will depend heavily on the SoC vendor support, Windows on ARM’s hardware emulation layers, and available drivers. Some early testers have reported instability and edge-case failures in beta builds; expect iterative improvement rather than instant perfection. (phoronix.com, windowsforum.com)
  • Running x86 guests on ARM remains an emulation story — not a virtualization story. For legacy x86 Windows or Linux guests, VirtualBox 7.2 does not remove the fundamental performance penalties of ISA translation. For scenarios that require x86 compatibility, continue to expect considerably reduced performance compared with native x86 hosts or with hypervisors that provide OS-level translation and more mature acceleration (for example, certain commercial solutions). (windowsforum.com)
In short: VirtualBox 7.2 opens the door to practical ARM-native virtualization, but production-scale deployments should be tested carefully and staged. Benchmarks and in-depth comparisons with alternatives (Parallels, VMware Fusion, QEMU/KVM frontends) will be essential to decide platform-level choices for heavy workloads.

Risks, known issues, and migration checklist​

Notable risks and caveats​

  • Saved state incompatibility for ARM VMs: Shut down ARM guests before upgrading or export them; otherwise snapshots and saved states created in 7.1 may be unusable. (forums.virtualbox.org)
  • Experimental 3D and driver gaps: DXMT is experimental; graphics drivers in guests may lag. Intel macOS hosts lose 3D support in this release. (techspot.com)
  • Beta-level instability in early builds: If you rely on 7.2 beta packages, expect crashes and edge-case behavior — the stable release reduces but does not eliminate this reality. (forums.virtualbox.org, phoronix.com)
  • x86 emulation still slow: For those wanting to run x86 Windows or Linux guests on ARM machines, VirtualBox 7.2 does not eliminate emulation performance penalties. Plan to use ARM-native guest systems for acceptable performance. (windowsforum.com)

Migration checklist before upgrading to 7.2​

  • Export any ARM VMs as OVA/OVF or shut them down (avoid saved/suspended states). (forums.virtualbox.org)
  • Back up VirtualBox configuration files and VM disks.
  • Verify whether your workflow depends on 3D acceleration on Intel macOS hosts; if so, delay upgrading. (techspot.com)
  • Confirm kernel compatibility and ensure you can sign modules on Secure Boot Linux hosts if needed. (phoronix.com)
  • Test Guest Additions installation in a disposable VM before rolling out across multiple systems. (techspot.com)

Installation and where to get it​

VirtualBox 7.2 binaries are provided for Windows, Intel macOS, Apple Silicon macOS, Linux distributions, and Solaris families. Oracle’s official download page and the 7.2 user guide and changelog are the authoritative starting points for downloads, installer packages, and documentation. Distribution package repositories and third-party mirrors may lag the upstream release. (docs.oracle.com, techspot.com)

Verdict: why this release matters for WindowsForum readers​

VirtualBox 7.2 is a strategic and practical step forward. For the Windows-on-ARM and Apple Silicon user communities, 7.2 provides the first broadly usable path to native ARM guests inside a familiar, free VirtualBox ecosystem. That’s a major win for developers and testers who need to validate ARM-native builds locally.
At the same time, this release is not a panacea. The real-world value of ARM-on-ARM virtualization in VirtualBox 7.2 depends on guest driver maturity, DXMT’s development, host SoC behavior, and the long tail of edge-case bugs that accompany any major platform transition. Users should treat this release as a capability-enabling milestone and adopt it progressively: test, validate, and keep fallbacks in place for mission-critical workloads.
For those who run mixed environments, the advice is straightforward: if you depend on older 3D acceleration on Intel Macs, stay on 7.1.x until you have a migration plan; if you run ARM-native workloads or develop for Apple Silicon or Windows/ARM, evaluate 7.2 in a controlled test rig and plan to benefit from lower CPU overhead and better integration in the long run. (techspot.com, linuxiac.com)

Final thoughts and the road ahead​

VirtualBox 7.2 transforms the product from a largely x86-centric legacy tool into a cross-ISA virtualization contender with a clearer future on ARM. The project’s move to open-source the NVMe controller emulation and publish source on GitHub opens the door for community contributions, faster driver work, and better long-term support.
Expect several cycles of iterative improvement: Guest Additions maturity, DXMT stabilization, and more robust nested virtualization and CPU feature passthrough are likely on Oracle’s roadmap. In the near term, this release is an essential milestone — it puts VirtualBox back on the table for serious ARM development workflows while preserving its role as a free, widely supported virtualization option.
Practical next steps for readers: back up critical VMs, test 7.2 in disposable environments, and track DXMT and Guest Additions updates closely. The ARM era for desktop virtualization is here — but as with any major platform shift, success will be decided by the next few maintenance and feature releases. (forums.virtualbox.org, techspot.com)


Source: How-To Geek VirtualBox 7.2 Finally adds Full ARM-on-ARM Virtualization
 

Back
Top