1 .. _Supported-build-platforms:
3 Supported build platforms
4 =========================
6 QEMU aims to support building and executing on multiple host OS
7 platforms. This appendix outlines which platforms are the major build
8 targets. These platforms are used as the basis for deciding upon the
9 minimum required versions of 3rd party software QEMU depends on. The
10 supported platforms are the targets for automated testing performed by
11 the project when patches are submitted for review, and tested before and
14 If a platform is not listed here, it does not imply that QEMU won't
15 work. If an unlisted platform has comparable software versions to a
16 listed platform, there is every expectation that it will work. Bug
17 reports are welcome for problems encountered on unlisted platforms
18 unless they are clearly older vintage than what is described here.
20 Note that when considering software versions shipped in distros as
21 support targets, QEMU considers only the version number, and assumes the
22 features in that distro match the upstream release with the same
23 version. In other words, if a distro backports extra features to the
24 software in their distro, QEMU upstream code will not add explicit
25 support for those backports, unless the feature is auto-detectable in a
26 manner that works for the upstream releases too.
28 The `Repology`_ site is a useful resource to identify
29 currently shipped versions of software in various operating systems,
30 though it does not cover all distros listed below.
32 Supported host architectures
33 ----------------------------
35 Those hosts are officially supported, with various accelerators:
43 - kvm (64 bit only), tcg, xen
55 - hax, hvf (64 bit only), kvm, nvmm, tcg, whpx (64 bit only), xen
57 Other host architectures are not supported. It is possible to build QEMU on an
58 unsupported host architecture using the configure ``--enable-tcg-interpreter``
59 option to enable the experimental TCI support, but note that this is very slow
60 and is not recommended.
62 Non-supported architectures may be removed in the future following the
63 :ref:`deprecation process<Deprecated features>`.
65 Linux OS, macOS, FreeBSD, NetBSD, OpenBSD
66 -----------------------------------------
68 The project aims to support the most recent major version at all times. Support
69 for the previous major version will be dropped 2 years after the new major
70 version is released or when the vendor itself drops support, whichever comes
71 first. In this context, third-party efforts to extend the lifetime of a distro
72 are not considered, even when they are endorsed by the vendor (eg. Debian LTS).
74 For the purposes of identifying supported software versions available on Linux,
75 the project will look at CentOS, Debian, Fedora, openSUSE, RHEL, SLES and
76 Ubuntu LTS. Other distros will be assumed to ship similar software versions.
78 For FreeBSD and OpenBSD, decisions will be made based on the contents of the
79 respective ports repository, while NetBSD will use the pkgsrc repository.
81 For macOS, `HomeBrew`_ will be used, although `MacPorts`_ is expected to carry
87 The project supports building with current versions of the MinGW toolchain,
88 hosted on Linux (Debian/Fedora).
90 The version of the Windows API that's currently targeted is Vista / Server
93 .. _HomeBrew: https://brew.sh/
94 .. _MacPorts: https://www.macports.org/
95 .. _Repology: https://repology.org/