jcs.org
qemu with hax to log dma reads & writes
jcs.org/2018/11/12/vfio
1.. _Supported-build-platforms:
2
3Supported build platforms
4=========================
5
6QEMU aims to support building and executing on multiple host OS
7platforms. This appendix outlines which platforms are the major build
8targets. These platforms are used as the basis for deciding upon the
9minimum required versions of 3rd party software QEMU depends on. The
10supported platforms are the targets for automated testing performed by
11the project when patches are submitted for review, and tested before and
12after merge.
13
14If a platform is not listed here, it does not imply that QEMU won't
15work. If an unlisted platform has comparable software versions to a
16listed platform, there is every expectation that it will work. Bug
17reports are welcome for problems encountered on unlisted platforms
18unless they are clearly older vintage than what is described here.
19
20Note that when considering software versions shipped in distros as
21support targets, QEMU considers only the version number, and assumes the
22features in that distro match the upstream release with the same
23version. In other words, if a distro backports extra features to the
24software in their distro, QEMU upstream code will not add explicit
25support for those backports, unless the feature is auto-detectable in a
26manner that works for the upstream releases too.
27
28The Repology site https://repology.org is a useful resource to identify
29currently shipped versions of software in various operating systems,
30though it does not cover all distros listed below.
31
32Linux OS
33--------
34
35For distributions with frequent, short-lifetime releases, the project
36will aim to support all versions that are not end of life by their
37respective vendors. For the purposes of identifying supported software
38versions, the project will look at Fedora, Ubuntu, and openSUSE distros.
39Other short- lifetime distros will be assumed to ship similar software
40versions.
41
42For distributions with long-lifetime releases, the project will aim to
43support the most recent major version at all times. Support for the
44previous major version will be dropped 2 years after the new major
45version is released, or when it reaches "end of life". For the purposes
46of identifying supported software versions, the project will look at
47RHEL, Debian, Ubuntu LTS, and SLES distros. Other long-lifetime distros
48will be assumed to ship similar software versions.
49
50Windows
51-------
52
53The project supports building with current versions of the MinGW
54toolchain, hosted on Linux.
55
56macOS
57-----
58
59The project supports building with the two most recent versions of
60macOS, with the current homebrew package set available.
61
62FreeBSD
63-------
64
65The project aims to support the all the versions which are not end of
66life.
67
68NetBSD
69------
70
71The project aims to support the most recent major version at all times.
72Support for the previous major version will be dropped 2 years after the
73new major version is released.
74
75OpenBSD
76-------
77
78The project aims to support the all the versions which are not end of
79life.