Runners
Nested virtualization on runners
KVM and Hyper-V exposed inside the runner for Android emulators, Firecracker microVMs and VM-based integration tests.
Specifications
- Linux
- KVM exposed to the job
- Windows
- Hyper-V available on 2025 images
- Android emulator
- Hardware accelerated
Runner labels
runnerhut-8vcpu-ubuntu-2404runnerhut-16vcpu-windows-2025
Without KVM, an Android emulator falls back to software rendering and a test suite that takes 4 minutes locally takes 40 in CI. GitHub-hosted Linux runners do not expose KVM on the standard tiers.
yaml
jobs: android: runs-on: runnerhut-8vcpu-ubuntu-2404 steps: - uses: actions/checkout@v4 - run: ls -l /dev/kvm # present - uses: reactivecircus/android-emulator-runner@v2 with: api-level: 34 script: ./gradlew connectedCheckYour next build could be twice as fast, at half the price
Start free. Migrating away is the same one line, and we publish that diff too.
Related
Linux x64 GitHub Actions runnersDedicated AMD and Intel vCPU runners from 2 to 64 cores, with NVMe scratch disks and a persistent cache on every job.Windows GitHub Actions runnersDedicated Windows Server 2022 and 2025 runners with Visual Studio build tools preinstalled and a persistent NuGet and MSBuild cache.