# Target Reference Den separates the conda platform from the boot/image target. The default target is still `qemu-aarch64`, but the codebase now has a `qemu-x86_64` target model for Linux amd64 work. | Target | Conda platform | Docker platform | Buildroot defconfig | Kernel artifact | Console | QEMU | | --- | --- | --- | --- | --- | --- | --- | | `qemu-aarch64` | `linux-aarch64` | `linux/arm64` | `den_qemu_aarch64_defconfig` | `Image` | `ttyAMA0` | `qemu-system-aarch64` | | `qemu-x86_64` | `linux-64` | `linux/amd64` | `den_qemu_x86_64_defconfig` | `bzImage` | `ttyS0` | `qemu-system-x86_64` | Use the target option on commands that create or boot target-specific artifacts: ```bash den image early-boot --target qemu-x86_64 den image qemu-bundle --target qemu-x86_64 den image uefi --target qemu-x86_64 den image oci --target qemu-x86_64 --rootfs build/rootfs --context build/oci-image --tag den:dev den smoke qemu --target qemu-x86_64 --kind systemd den smoke qemu-bundle --target qemu-x86_64 den smoke oci --target qemu-x86_64 den smoke uefi --target qemu-x86_64 ``` `DEN_TARGET` provides the same default for conda tasks and direct command use: ```bash DEN_TARGET=qemu-x86_64 ct run boot-systemd-smoke ``` Target aliases are accepted by the CLI. For example, `--target linux-64` and `--target amd64` both resolve to `qemu-x86_64`. The checked-in lockfile covers contributor tooling. Image commands generate a separate workspace and lock for the selected target, using the hosted Den package channel before `conda-forge`. Both targets have native package and image workflow definitions. A target is release-supported only after its candidate and promotion jobs have passed.