Version 7.2.5-1 is a new release; it follows the upstream QEMU release.

The xPack QEMU RISC-V is a standalone cross-platform binary distribution of QEMU.

There are separate binaries for Windows (Intel 64-bit), macOS (Intel 64-bit, Apple Silicon 64-bit) and GNU/Linux (Intel 64-bit, Arm 32/64-bit).


The binary files are available from GitHub Releases.


  • GNU/Linux Intel 64-bit: any system with GLIBC 2.27 or higher (like Ubuntu 18 or later, Debian 10 or later, RedHat 8 later, Fedora 29 or later, etc)
  • GNU/Linux Arm 32/64-bit: any system with GLIBC 2.27 or higher (like Raspberry Pi OS, Ubuntu 18 or later, Debian 10 or later, RedHat 8 later, Fedora 29 or later, etc)
  • Intel Windows 64-bit: Windows 7 with the Universal C Runtime (UCRT), Windows 8, Windows 10
  • macOS Intel 64-bit: 10.13 or later
  • macOS Apple Silicon 64-bit: 11.6 or later

On GNU/Linux, QEMU requires the X11 libraries to be present. On Debian derived distribution they are already in the system; on RedHat & Arch derived distributions they must be installed explicitly.


The full details of installing the xPack QEMU RISC-V on various platforms are presented in the separate Install page.

Easy install

The easiest way to install QEMU RISC-V is with xpm by using the binary xPack, available as @xpack-dev-tools/qemu-riscv from the registry.

With the xpm tool available, installing the latest version of the package and adding it as a development dependency for a project is quite easy:

cd my-project
xpm init # Add a package.json if not already present

xpm install @xpack-dev-tools/qemu-riscv@latest --verbose

ls -l xpacks/.bin

To install this specific version, use:

xpm install @xpack-dev-tools/qemu-riscv@7.2.5-1.1 --verbose

For xPacks aware tools, like the Eclipse Embedded C/C++ plug-ins, it is also possible to install QEMU RISC-V globally, in the user home folder.

xpm install --global @xpack-dev-tools/qemu-riscv@latest --verbose

Eclipse will automatically identify binaries installed with xpm and provide a convenient method to manage paths.


To remove the links created by xpm in the current project:

cd my-project

xpm uninstall @xpack-dev-tools/qemu-riscv

To completely remove the package from the central xPack store:

xpm uninstall --global @xpack-dev-tools/qemu-riscv


The xPack QEMU RISC-V currently is based on the official QEMU, with major changes.

The current version is based on:

  • QEMU version 7.2.5, commit 9abcf97 from August 7, 2023.


Compared to the master qemu-system-riscv*, there are no major changes.

The supported boards and CPUs are:

$ .../xpack-qemu-riscv-7.2.5-1/bin/qemu-system-riscv32 -machine help
Supported machines are:
none                 empty machine
opentitan            RISC-V Board compatible with OpenTitan
sifive_e             RISC-V Board compatible with SiFive E SDK
sifive_u             RISC-V Board compatible with SiFive U SDK
spike                RISC-V Spike board (default)
virt                 RISC-V VirtIO board
$ .../xpack-qemu-riscv-7.2.5-1/bin/qemu-system-riscv32 -cpu help

$ .../xpack-qemu-riscv-7.2.5-1/bin/qemu-system-riscv64 -machine help
Supported machines are:
microchip-icicle-kit Microchip PolarFire SoC Icicle Kit
none                 empty machine
shakti_c             RISC-V Board compatible with Shakti SDK
sifive_e             RISC-V Board compatible with SiFive E SDK
sifive_u             RISC-V Board compatible with SiFive U SDK
spike                RISC-V Spike board (default)
virt                 RISC-V VirtIO board
$ .../xpack-qemu-riscv-7.0.0-1/bin/qemu-system-riscv64 -cpu help

Bug fixes

  • none


  • none

Known problems

  • in order to build on macOS 10.13, the Intel macOS version has some functionality related to bridged virtual interfaces disabled.

Shared libraries

On all platforms the packages are standalone, and expect only the standard runtime to be present on the host.

All dependencies that are build as shared libraries are copied locally in the libexec folder (or in the same folder as the executable for Windows).


On GNU/Linux the binaries are adjusted to use a relative path:

$ readelf -d | grep runpath
 0x000000000000001d (RPATH)            Library rpath: [$ORIGIN]

In the GNU search strategy, the DT_RPATH has the highest priority, higher than LD_LIBRARY_PATH, so if this later one is set in the environment, it should not interfere with the xPack binaries.

Please note that previous versions, up to mid-2020, used DT_RUNPATH, which has a priority lower than LD_LIBRARY_PATH, and does not tolerate setting it in the environment.

@rpath and @loader_path

Similarly, on macOS, the binaries are adjusted with install_name_tool to use a relative path.


The original documentation is available on-line:


The binaries for all supported platforms (Windows, macOS and GNU/Linux) were built using the xPack Build Box (XBB), a set of build environments based on slightly older distributions, that should be compatible with most recent systems.

For the prerequisites and more details on the build procedure, please see the How to build page.

CI tests

Before publishing, a set of simple tests were performed on an exhaustive set of platforms. The results are available from:




The SHA-256 hashes for the files are:







Deprecation notices

32-bit support

Support for 32-bit Intel Linux and Intel Windows was dropped in 2022. Support for 32-bit Arm Linux (armv7l) will be preserved for a while, due to the large user base of 32-bit Raspberry Pi systems.

Linux minimum requirements

Support for RedHat 7 was dropped in 2022, and the minimum requirement was raised to GLIBC 2.27, available starting with Ubuntu 18 and RedHat 8.

Pre-deprecation notice for Ubuntu 18.04

Ubuntu 18.04 LTS Bionic Beaver reached the end of the standard five-year maintenance window for Long-Term Support (LTS) release on 31 May 2023.

As a courtesy, the xPack GNU/Linux releases will continue to be based on Ubuntu 18.04 for another year.

From mid-2024 onwards, the GNU/Linux binaries will be built on Debian 10, (GLIBC 2.28), and are also expected to run on RedHat 8.

Users are urged to update their build and test infrastructure to ensure a smooth transition to the next xPack releases.

Download analytics

Credit to Shields IO for the badges and to Somsubhra/github-release-stats for the individual file counters.