# Linux x64 Runners (https://tenki.cloud/docs/runners/x64-runners)

> For the complete documentation index, see [llms.txt](https://tenki.cloud/llms.txt)

Bare-metal Linux x64 GitHub Actions runners on AMD EPYC processors, running the official GitHub Actions runner images.

Tenki's x64 runners use **AMD EPYC processors** with a 1:2 physical-to-virtual core mapping: each pair of vCPUs corresponds to a single physical core, which keeps compute performance consistent and predictable between runs.

Sizes run from 2 vCPU / 4 GB up to 16 vCPU / 32 GB, with larger configurations available on request. Starter workspaces are capped at 4 vCPU / 8 GB. See [Runner Sizes & Labels](https://tenki.cloud/docs/runners/sizes.md) for labels and specifications, and [Limits & Concurrency](https://tenki.cloud/docs/runners/limits-and-concurrency.md) for per-plan limits.

## Image

Linux runners use the official GitHub Actions runner images from [`actions/runner-images`](https://github.com/actions/runner-images), with Ubuntu 24.04 as the default. Anything that runs on GitHub-hosted `ubuntu-latest` runs on Tenki with no changes, with the same toolchains on the same version cadence. See [Runner Images](https://tenki.cloud/docs/runners/runner-images.md) for details and custom images.

## Nested virtualization (KVM)

x64 runners support KVM nested virtualization, so jobs can boot VMs and emulators inside the runner. This is the configuration Android emulator workloads (Espresso, instrumented UI tests) need. See [Android Emulator](https://tenki.cloud/docs/runners/android-emulator.md) for a full example and sizing guidance.

## Every job is a fresh VM

Each job runs in its own single-use VM with its own kernel, destroyed when the job ends. Nothing is shared or reused between jobs or customers; see [Security & Isolation](https://tenki.cloud/docs/trust/security.md).