Hi everyone! I’ve been working on an AArch64 AROS port that runs in a hardware-accelerated VM on Apple Silicon Macs, using Apple’s Virtualization.framework. It boots into Wanderer and includes display and input support, networking through the Mac’s NAT connection, persistent storage, clipboard synchronization, and file exchange with macOS. It’s packaged as a standalone Mac application. The guest runs its own AROS kernel, separately from the macOS-hosted port. I’ve also tested guest boot under QEMU with HVF acceleration. I’d like your feedback on whether this would be a useful addition to upstream AROS, and whether you’d be happy for me to contribute it. Where would you suggest placing the VM-specific platform code and drivers? My preference would be to share the generic AArch64 and virtio components wherever possible, while keeping the macOS launcher and packaging separate, but I’d appreciate guidance on the structure you’d prefer. Would a short architecture overview followed by smaller, focused PRs be a good way to start? The architectural goal is a shared AROS AArch64 kernel that discovers the platform through a Device Tree and binds the appropriate drivers, across virtual machines, Apple Silicon bare metal, and Raspberry Pi. This is the direction of the work at least... I'm not yet there but I'm close to having the bare metal version running as well. @Kalamatee no x18 register reserved.