Skip to content

macOS: enable nested virtualization by default on supported Macs - #76

Merged
paf0186 merged 4 commits into
masterfrom
macos-hvf-nested
Nov 17, 2026
Merged

paf0186 merged 4 commits into
masterfrom
macos-hvf-nested

Conversation

@paf0186

@paf0186 paf0186 commented Nov 17, 2026

Copy link
Copy Markdown
Contributor

Maintainer announcement

Native aarch64 guests now get Arm EL2 automatically on capable Apple Silicon Macs with macOS 15+ and QEMU 11.1+. This gives a KVM-enabled Linux guest /dev/kvm so it can run accelerated inner VMs. ltvm checks support on cold boot and uses ordinary HVF if nesting is unavailable. create --disable-nesting and cluster create --disable-nesting save the opt-out across restarts.

On a capable Mac, ltvm doctor reports when the selected QEMU is older than 11.1. ltvm doctor --fix and ltvm install --qemu can install the signed, checksum-pinned QEMU 11.1.3 bundle from this repository. The ltvm skill and operator docs cover the default and the opt-out.

Verification

  • On an M5 with macOS 26.6.2, QEMU 11.1.3 booted a Rocky 10 guest at EL2 with /dev/kvm. The same VM cold-booted at EL1 with QEMU 10.2.2 and returned to EL2 when switched back. The explicit opt-out stayed at EL1 across restart.
  • Rocky 9 booted as an inner KVM guest, mounted Lustre, and read back one 16 MiB file with a matching SHA-256 after writing and syncing it.
  • In an isolated prefix, the doctor check flagged QEMU 10.2.2 and repair downloaded, verified, and selected QEMU 11.1.3 from the public GitHub release.
  • Ruff passed. Focused Python tests finished with 651 passed and 3 skipped.

Persist a create-time opt-in for native aarch64 HVF guests. Validate the macOS EL2 capability and the selected QEMU before boot, then enable the platform GIC and guest EL2.
Detect host EL2 and QEMU support at cold boot and persist a create-time opt-out for individual VMs and clusters. Keep the userspace GIC available when running newer QEMU on macOS before 15.
@paf0186
paf0186 merged commit 5ef5061 into master Nov 17, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant