Oracle’s VirtualBox project has taken a major step toward making Windows on Arm a practical option for desktop virtualization, with the 7.2 development cycle bringing explicit Windows 11 ARM guest and host support, preliminary Linux 6.16 compatibility, reworked Guest Additions for Arm, and a host of GUI and driver refinements that together mark one of the most significant VirtualBox platform expansions in years. (phoronix.com) (phoronix.com)
VirtualBox has long been a go-to cross-platform hypervisor for developers, testers, and hobbyists who need to run multiple OSes on a single machine. Over the past two major series (7.0 and 7.1), Oracle focused on modernizing the UI, improving 3D support, and adding features such as Wayland clipboard sharing and improved NVMe handling. The 7.2 branch now targets architectural expansion—notably Arm virtualization on Windows hosts and direct support for Windows 11/ARM guests—and moves more of the project’s source and issue tracking onto GitHub to invite broader community participation. (virtualbox.org) (virtualbox.org)
Recent coverage and developer announcements describe the initial 7.2 preview/beta releases as the vehicles for these changes. Phoronix’s reporting highlights that VirtualBox 7.2 Beta 1 adds Windows 11 on Arm support for both hosts and guests and that Beta 2 expands the work with WDDM graphics and shared-folder support while preparing for Linux 6.16 compatibility. Oracle’s official announcement lists the 7.2.0_BETA1 release and points to the public GitHub mirror for the VirtualBox source. (phoronix.com) (phoronix.com) (virtualbox.org)
Additionally, community discussions and bug tracker entries reflect real-world friction points (driver install issues on Windows hosts, ARM installer quirks, and saved-state incompatibilities), which align with the release notes’ cautions and the advice to treat these builds as early access / preview rather than production-ready releases. (forum.virtualbox.org)
However, the broader industry still faces the mixed-architecture reality: full software stacks, tooling, and third-party drivers must be Arm-aware for the transition to be seamless. VirtualBox’s work accelerates the operating-system-level and hypervisor-level readiness, but application and driver ecosystem changes remain the rate-limiting factors.
That said, these builds are still in beta. Users and admins should:
Conclusion
VirtualBox 7.2’s development marks a turning point: the hypervisor once primarily focused on x86 cross-platform convenience is actively embracing Arm-era realities. The betas already show practical, usable features for Arm-native guests and improved Linux kernel compatibility; the move to GitHub and the depth of work on graphics and Guest Additions make this a release series to follow closely. Organizations should validate the beta features in isolated environments now, while planning migration strategies that account for known incompatibilities and the still-maturing state of Arm virtualization tooling. (phoronix.com) (phoronix.com) (virtualbox.org)
Source: Phoronix VirtualBox 7.2 Released With Windows 11 ARM Support, Linux 6.16 Compatibility - Phoronix
Background
VirtualBox has long been a go-to cross-platform hypervisor for developers, testers, and hobbyists who need to run multiple OSes on a single machine. Over the past two major series (7.0 and 7.1), Oracle focused on modernizing the UI, improving 3D support, and adding features such as Wayland clipboard sharing and improved NVMe handling. The 7.2 branch now targets architectural expansion—notably Arm virtualization on Windows hosts and direct support for Windows 11/ARM guests—and moves more of the project’s source and issue tracking onto GitHub to invite broader community participation. (virtualbox.org) (virtualbox.org)Recent coverage and developer announcements describe the initial 7.2 preview/beta releases as the vehicles for these changes. Phoronix’s reporting highlights that VirtualBox 7.2 Beta 1 adds Windows 11 on Arm support for both hosts and guests and that Beta 2 expands the work with WDDM graphics and shared-folder support while preparing for Linux 6.16 compatibility. Oracle’s official announcement lists the 7.2.0_BETA1 release and points to the public GitHub mirror for the VirtualBox source. (phoronix.com) (phoronix.com) (virtualbox.org)
What’s actually new in VirtualBox 7.2 (high level)
- Windows 11/ARM guest support: Guest Additions for Windows 11 on Arm are now part of the 7.2 preview work, enabling tighter integration features (keyboard/mouse seamlessness, shared folders, clipboard) for Arm guests running under Arm hosts or supported hosts. (phoronix.com)
- Windows/Arm host virtualization: The unified Windows installer package now includes Arm virtualization support so Windows 11 on Arm machines can act as hosts for Arm VMs. (linuxcompatible.org)
- WDDM graphics driver work: Beta 2 shows progress on a WDDM driver for Windows 11/ARM guests, aiming to unlock better 2D/3D acceleration and a more responsive UI inside guest VMs. (phoronix.com)
- Linux kernel compatibility: Development builds include preparatory work for Linux 6.16 (and in some notes 6.17) to ensure guest and host integration keep pace with the latest distributions. (phoronix.com)
- GUI rework and usability: The UI receives layout changes—global and VM tools moved into accessible toolbars—plus general preference and window behavior fixes. (linuxcompatible.org)
- Source code on GitHub: VirtualBox’s repository is mirrored to GitHub, improving transparency and developer collaboration. (virtualbox.org)
Deep dive: Windows 11 on Arm — what’s supported and what isn’t (yet)
Native Arm virtualization vs. emulation
VirtualBox 7.2’s most headline-grabbing capability is native virtualization for Arm-based Windows 11 (Arm64) guests. This differs from attempting to emulate x86/x64 guests on Arm hosts; VirtualBox’s work focuses on running Arm-native OSes and Arm-native guest additions, which avoids the high cost of binary translation. For users wanting to run legacy x86/x64 Windows or Linux inside an Arm VM, the practical performance remains poor unless a translation/emulation layer (like Microsoft’s Prism running in the guest OS) is used—VirtualBox is not providing an x86->Arm binary translator as part of this feature set. (linuxiac.com) (reddit.com)Guest Additions and integration features
Beta 1 and Beta 2 reveal explicit work to support Guest Additions for Windows 11 on Arm. That’s significant because Guest Additions bring:- Mouse/keyboard seamless integration (no capture/release friction)
- Shared folders and drag-and-drop between host and guest
- Display resizing and improved video/graphics handling
- Clipboard synchronization (text, possibly files depending on implementation)
WDDM graphics driver: why it matters
On Windows, the Windows Display Driver Model (WDDM) is the kernel/user driver model that defines how the OS and GPU talk. A proper WDDM driver inside the guest lets VirtualBox provide accelerated GPU features rather than relying purely on software rendering. Beta 2’s explicit mention of WDDM work indicates a path toward smoother UI, better video playback, and possibly improved support for graphically heavy applications inside Windows 11/ARM guests—but the driver is not yet mature and remains a development focus. Expect incremental gains: windowed UI responsiveness and some 3D features rather than full game-level acceleration at first. (phoronix.com)Saved-state and snapshot caveats
One concrete interoperability note: saved states from 7.1 ARM VMs are not compatible with 7.2 ARM VMs. Users upgrading to the 7.2 series should fully shut down Arm VMs (not suspend to saved state) before migrating. This incompatibility is common during cross-major upgrades where guest CPU or device models change. Plan migrations accordingly. (linuxcompatible.org)Linux 6.16 compatibility: what to expect
VirtualBox 7.2 beta work explicitly prepares for recent upstream Linux kernels. The implications are practical:- Guest Additions kernel modules need updates to compile cleanly against kernel 6.16/6.17. The VirtualBox team has introduced initial support and fixes so Guest Additions can install on modern distributions without manual patching. (phoronix.com)
- Host-side kernel changes in networking, graphics, or module handling sometimes break hypervisors; preemptive compatibility increases reliability for distro upgrades (important for VMs used in CI, testing, and server roles). (forum.virtualbox.org)
UI, drivers and ecosystem shifts
GUI and usability
7.2 reorganizes the UI to reduce hidden controls and surface common tasks. Global tools are moved into a persistent toolbar and VM-specific tools into tabs—this reduces reliance on nested “hamburger” menus and aims to make advanced tasks more discoverable for new users. Accessibility and preference panel fixes also appear across the release notes. These changes are practical quality-of-life improvements for power users and newcomers alike. (linuxcompatible.org)NVMe, NAT, and network stack changes
VirtualBox’s changelog and release notes list numerous refinements:- NVMe controller emulation improvements (import/export compatibility and bug fixes). This matters for VMs using virtual NVMe disks, especially when moving images between hosts or importing cloud-style images. (linuxiac.com)
- NAT engine upgrades (historically moving to newer libs such as libslirp) improve networking reliability and IPv6 handling. NAT changes can influence port forwarding and complex network setups; validate those after upgrading. (virtualbox.org)
Open-source posture: code on GitHub
Oracle has published the VirtualBox source tree on GitHub, making it easier for developers to file issues, propose changes, and fork code for platform-specific optimizations. This is a noteworthy shift for a project historically tracked through its own infrastructure; the move can accelerate contributions, code review, and third-party integrations. (virtualbox.org)Independent corroboration and verification
Phoronix’s reporting on the 7.2 beta series closely matches Oracle’s official announcements: the public 7.2.0_BETA1 announcement is present in the VirtualBox mailing archive and Oracle’s site lists the associated beta downloads, while beta2 reports confirm further Arm/WDDM and Linux kernel work. Independent Linux-focused coverage (community and news outlets) also documents the same set of headline changes—Windows 11/ARM guest additions, Arm host virtualization, WDDM work, GUI rework, and Linux kernel compatibility—giving confidence that these are project-level priorities and not isolated experiments. (phoronix.com) (virtualbox.org) (linuxiac.com)Additionally, community discussions and bug tracker entries reflect real-world friction points (driver install issues on Windows hosts, ARM installer quirks, and saved-state incompatibilities), which align with the release notes’ cautions and the advice to treat these builds as early access / preview rather than production-ready releases. (forum.virtualbox.org)
Strengths — why this matters for Windows and Linux users
- Brings native Arm virtualization to Windows 11 on Arm machines, enabling local development and testing of Arm-native workloads without cloud dependence. This is a practical win for developers targeting Arm platforms. (phoronix.com)
- Improves guest integration for Windows 11 Arm (Guest Additions and WDDM), which reduces friction for desktop-style usage inside VMs—valuable for QA and application compatibility testing. (phoronix.com)
- Keeps pace with Linux kernel evolution, reducing the burden on users who adopt cutting-edge distros or who run kernel-heavy workloads in VMs. (phoronix.com)
- Greater transparency and community contribution potential via GitHub lowers the barrier for external fixes, ports, and vendor collaboration. (virtualbox.org)
Risks, limitations, and practical cautions
- Beta status — not production-ready
VirtualBox 7.2 features are appearing in beta builds. Organizations should not migrate mission-critical VM fleets to 7.2 until a stable release is published and validated in their environment. Expect regressions and incompatibilities (saved-state incompatibility is a concrete example). (linuxcompatible.org) - x86/x64 emulation is not solved here
If your goal is to run legacy x86 or x64 Windows inside an Arm VM on an Arm host, VirtualBox’s Arm virtualization does not magically translate those binaries. Emulation remains slow and is better handled by OS-level translation (e.g., Prism in Windows) or cloud services. Plan to run Arm-native guests for usable performance. (reddit.com) - Graphics acceleration is incremental
WDDM and 3D improvements are promising, but early drivers are seldom complete. Don’t assume full Direct3D game support in the first stable builds; expect progressive improvements and selective hardware/feature support. (phoronix.com) - Driver and installer variability across Arm chips
Arm platform fragmentation (Snapdragon variants, Apple silicon, and other Arm SoCs) means behavior will vary by vendor. Some device drivers and low-level hardware integration may need vendor-specific adjustments. Test on the target hardware early. - Saved-state and snapshot migration hazards
The incompatibility of saved states between major versions means that administrators must plan shutdown-and-upgrade operations rather than relying on suspend/resume migration strategies. (linuxcompatible.org)
Practical upgrade and adoption guidance
- Inventory current VMs and note any Arm-based VMs or saved states. Do not upgrade a host running production VMs without a backup plan.
- For each Arm VM, perform a clean shutdown (no saved states) before installing 7.2 preview builds. (linuxcompatible.org)
- If you rely on intensive graphics or gaming in VMs, treat WDDM enhancements as experimental—validate specific title compatibility and anti-cheat systems in controlled tests. (phoronix.com)
- For Linux host or guest use, update Guest Additions to the latest preview matching the kernel series; verify dkms/module build success against kernel 6.16/6.17 dev kernels where applicable. (phoronix.com)
- Track GitHub issues and the VirtualBox forums for platform-specific patches; the move to GitHub should speed up fixes and external contributions. (virtualbox.org)
What administrators and developers should test right away
- Boot a Windows 11/Arm guest on an Arm host and verify Guest Additions install and basic integration (clipboard, shared folders). (phoronix.com)
- Validate display behavior (dynamic resolution, multiple monitors) and note rendering performance with and without WDDM enabled. (phoronix.com)
- Test NVMe-backed VM images for import/export fidelity and ensure no VMDK corruption or resizing problems on your workload. (linuxiac.com)
- On Linux hosts, compile and load Guest Additions modules against your kernel version and observe for kernel module errors or KVM/KSM conflicts. (forum.virtualbox.org)
How this changes the virtualization landscape
VirtualBox enabling Windows 11/ARM guests and Windows/Arm host virtualization levels the playing field for developers and small teams who want a local, standalone environment for Arm-native development—previously, the easiest route was cloud-hosted Arm instances or relying on vendor-specific hypervisors. Packaging Arm virtualization into Oracle’s unified Windows installer and moving the code to GitHub are both signals that the project intends to be a long-term, actively maintained option for Arm scenarios. (virtualbox.org)However, the broader industry still faces the mixed-architecture reality: full software stacks, tooling, and third-party drivers must be Arm-aware for the transition to be seamless. VirtualBox’s work accelerates the operating-system-level and hypervisor-level readiness, but application and driver ecosystem changes remain the rate-limiting factors.
Final assessment and recommendations
VirtualBox 7.2’s preview builds are a meaningful and strategic step: they provide the first clear path for running Windows 11/ARM guests with integrated Guest Additions and begin the work needed for a real Arm-first virtualization story on Windows hosts. That progress is backed by official announcements and multiple independent reports, and Oracle’s GitHub move increases confidence that community contributions will accelerate fixes and feature parity. (phoronix.com) (virtualbox.org)That said, these builds are still in beta. Users and admins should:
- Treat 7.2 as a preview and perform careful testing before production adoption. (linuxcompatible.org)
- Prefer Arm-native guest images for usable performance; do not expect x86/x64 guests to perform well via emulation. (reddit.com)
- Test saved-state and snapshot workflows and plan for full VM shutdowns on upgrades. (linuxcompatible.org)
Conclusion
VirtualBox 7.2’s development marks a turning point: the hypervisor once primarily focused on x86 cross-platform convenience is actively embracing Arm-era realities. The betas already show practical, usable features for Arm-native guests and improved Linux kernel compatibility; the move to GitHub and the depth of work on graphics and Guest Additions make this a release series to follow closely. Organizations should validate the beta features in isolated environments now, while planning migration strategies that account for known incompatibilities and the still-maturing state of Arm virtualization tooling. (phoronix.com) (phoronix.com) (virtualbox.org)
Source: Phoronix VirtualBox 7.2 Released With Windows 11 ARM Support, Linux 6.16 Compatibility - Phoronix
Last edited:
