Name
Date
Size
#Lines
LOC

..--

.github/workflows/H--3123

.gitlab/issue_templates/H--9825

.gitlab-ci.d/H--2,5822,089

accel/H--21,42415,422

audio/H--13,24310,350

authz/H--959677

backends/H--8,7166,568

block/H--88,88264,816

bsd-user/H--19,33913,069

chardev/H--9,1997,035

common-user/H--1,212564

configs/H--738581

contrib/H--12,6749,589

crypto/H--16,94512,677

disas/H--51,48835,919

docs/H--67,13850,539

dump/H--2,8682,104

ebpf/H--1,5201,326

fpu/H--7,8426,258

fsdev/H--1,305922

gdb-xml/H--2,3311,852

gdbstub/H--4,9693,820

host/include/H--1,8611,405

hw/H--790,871602,295

include/H--180,85192,855

io/H--6,1964,774

libdecnumber/H--10,6686,261

linux-headers/H--18,11112,866

linux-user/H--75,55860,731

migration/H--34,58823,378

monitor/H--5,2323,879

nbd/H--5,7384,154

net/H--19,57214,535

pc-bios/H--48,76433,823

plugins/H--2,0551,488

po/H--706521

python/H--9,4917,145

qapi/H--30,32228,164

qga/H--15,61612,431

qobject/H--3,7032,303

qom/H--3,8353,027

replay/H--2,4551,866

roms/H--916771

rust/H--3,1312,201

scripts/H--37,96028,526

scsi/H--2,3001,801

semihosting/H--2,4701,818

stats/H--420341

storage-daemon/H--512389

stubs/H--963646

subprojects/H--8,1205,809

system/H--21,28616,338

target/H--908,237761,461

tcg/H--60,25751,142

tests/H--578,605477,949

tools/H--1,165895

trace/H--1,6171,041

ui/H--43,71634,728

util/H--34,97623,649

.dir-locals.elH A D09-Oct-201575 32

.editorconfigH A D11-Mar-2021951 5040

.exrcH A D10-Jan-2013220 87

.gdbinitH A D12-Jun-2017326 97

.git-blame-ignore-revsH A D04-Apr-2023474 2217

.gitattributesH A D06-Nov-2024226 108

.gitignoreH A D06-Jun-2023194 2322

.gitlab-ci.ymlH A D29-Jul-2021884 252

.gitmodulesH A D06-Jun-20231.5 KiB4645

.gitpublishH A D05-Mar-20181.6 KiB5244

.mailmapH A D03-Dec-202411.2 KiB230223

.patchew.ymlH A D25-Jun-20218.3 KiB300228

.readthedocs.ymlH A D21-Dec-2023621 2611

.travis.ymlH A D04-Nov-20247.6 KiB276239

COPYINGH A D12-Oct-200817.6 KiB340281

COPYING.LIBHD31-Jan-201925.9 KiB

KconfigH A D11-Oct-2024152 87

Kconfig.hostH A D02-Nov-2024750 6444

LICENSEH A D11-Nov-20191.1 KiB2820

MAINTAINERSH A D03-Dec-202499.5 KiB4,2763,844

MakefileH A D05-Nov-202411.4 KiB337249

README.rstH A D17-Jul-20245.4 KiB172117

VERSIONH A D08-Feb-20256 21

block.cH A D10-Sep-2024247.1 KiB8,4335,570

blockdev-nbd.cH A D26-Aug-20248.9 KiB330242

blockdev.cH A D30-Sep-2024108.6 KiB3,6532,870

blockjob.cH A D21-Dec-202317.5 KiB631472

configureH A D18-Nov-202459.4 KiB2,0621,686

cpu-common.cH A D16-Nov-202412.5 KiB458301

cpu-target.cH A D04-Jun-202412.8 KiB475356

event-loop-base.cH A D09-May-20224 KiB141106

gitdm.configH A D22-Mar-20231.9 KiB6052

hmp-commands-info.hxH A D30-Jun-202421.6 KiB982838

hmp-commands.hxH A D09-May-202454.2 KiB1,8621,605

iothread.cH A D13-Feb-202411.6 KiB409286

job-qmp.cH A D14-Dec-20224.3 KiB189122

job.cH A D21-Dec-202331.6 KiB1,265899

meson.buildH A D30-Mar-2023173.8 KiB4,8834,459

meson_options.txtH A D06-Nov-202419.2 KiB385365

module-common.cH A D29-Jan-2016113 118

os-posix.cH A D30-Jun-20248.2 KiB345250

os-win32.cH A D19-Apr-20222 KiB6327

page-target.cH A D26-Apr-2024822 4527

page-vary-common.cH A D19-Apr-20221.6 KiB5422

page-vary-target.cH A D05-Oct-20231.2 KiB4219

pythondeps.tomlH A D11-Oct-20241.7 KiB3632

qemu-bridge-helper.cH A D01-Oct-202011.9 KiB467345

qemu-edid.cH A D13-Oct-20223.7 KiB133118

qemu-img-cmds.hxH A D18-Jan-20245.6 KiB10386

qemu-img.cH A D21-Dec-2023165.8 KiB5,6224,693

qemu-io-cmds.cH A D13-Jun-202473.4 KiB2,8142,370

qemu-io.cH A D21-Dec-202317.7 KiB690593

qemu-keymap.cH A D04-Oct-20247.6 KiB269211

qemu-nbd.cH A D08-Aug-202439.8 KiB1,2341,069

qemu-options.hxH A D29-Oct-2024260.1 KiB6,0494,888

qemu.nsiH A D25-Sep-20246.8 KiB250203

qemu.saslH A D14-Jun-20211.7 KiB4237

replication.cH A D26-May-20212.5 KiB10877

trace-eventsH A D19-Nov-20241.7 KiB4541

version.rcH A D06-Jan-2021867 3128

README.rst

1===========
2QEMU README
3===========
4
5QEMU is a generic and open source machine & userspace emulator and
6virtualizer.
7
8QEMU is capable of emulating a complete machine in software without any
9need for hardware virtualization support. By using dynamic translation,
10it achieves very good performance. QEMU can also integrate with the Xen
11and KVM hypervisors to provide emulated hardware while allowing the
12hypervisor to manage the CPU. With hypervisor support, QEMU can achieve
13near native performance for CPUs. When QEMU emulates CPUs directly it is
14capable of running operating systems made for one machine (e.g. an ARMv7
15board) on a different machine (e.g. an x86_64 PC board).
16
17QEMU is also capable of providing userspace API virtualization for Linux
18and BSD kernel interfaces. This allows binaries compiled against one
19architecture ABI (e.g. the Linux PPC64 ABI) to be run on a host using a
20different architecture ABI (e.g. the Linux x86_64 ABI). This does not
21involve any hardware emulation, simply CPU and syscall emulation.
22
23QEMU aims to fit into a variety of use cases. It can be invoked directly
24by users wishing to have full control over its behaviour and settings.
25It also aims to facilitate integration into higher level management
26layers, by providing a stable command line interface and monitor API.
27It is commonly invoked indirectly via the libvirt library when using
28open source applications such as oVirt, OpenStack and virt-manager.
29
30QEMU as a whole is released under the GNU General Public License,
31version 2. For full licensing details, consult the LICENSE file.
32
33
34Documentation
35=============
36
37Documentation can be found hosted online at
38`<https://www.qemu.org/documentation/>`_. The documentation for the
39current development version that is available at
40`<https://www.qemu.org/docs/master/>`_ is generated from the ``docs/``
41folder in the source tree, and is built by `Sphinx
42<https://www.sphinx-doc.org/en/master/>`_.
43
44
45Building
46========
47
48QEMU is multi-platform software intended to be buildable on all modern
49Linux platforms, OS-X, Win32 (via the Mingw64 toolchain) and a variety
50of other UNIX targets. The simple steps to build QEMU are:
51
52
53.. code-block:: shell
54
55  mkdir build
56  cd build
57  ../configure
58  make
59
60Additional information can also be found online via the QEMU website:
61
62* `<https://wiki.qemu.org/Hosts/Linux>`_
63* `<https://wiki.qemu.org/Hosts/Mac>`_
64* `<https://wiki.qemu.org/Hosts/W32>`_
65
66
67Submitting patches
68==================
69
70The QEMU source code is maintained under the GIT version control system.
71
72.. code-block:: shell
73
74   git clone https://gitlab.com/qemu-project/qemu.git
75
76When submitting patches, one common approach is to use 'git
77format-patch' and/or 'git send-email' to format & send the mail to the
78qemu-devel@nongnu.org mailing list. All patches submitted must contain
79a 'Signed-off-by' line from the author. Patches should follow the
80guidelines set out in the `style section
81<https://www.qemu.org/docs/master/devel/style.html>`_ of
82the Developers Guide.
83
84Additional information on submitting patches can be found online via
85the QEMU website:
86
87* `<https://wiki.qemu.org/Contribute/SubmitAPatch>`_
88* `<https://wiki.qemu.org/Contribute/TrivialPatches>`_
89
90The QEMU website is also maintained under source control.
91
92.. code-block:: shell
93
94  git clone https://gitlab.com/qemu-project/qemu-web.git
95
96* `<https://www.qemu.org/2017/02/04/the-new-qemu-website-is-up/>`_
97
98A 'git-publish' utility was created to make above process less
99cumbersome, and is highly recommended for making regular contributions,
100or even just for sending consecutive patch series revisions. It also
101requires a working 'git send-email' setup, and by default doesn't
102automate everything, so you may want to go through the above steps
103manually for once.
104
105For installation instructions, please go to:
106
107*  `<https://github.com/stefanha/git-publish>`_
108
109The workflow with 'git-publish' is:
110
111.. code-block:: shell
112
113  $ git checkout master -b my-feature
114  $ # work on new commits, add your 'Signed-off-by' lines to each
115  $ git publish
116
117Your patch series will be sent and tagged as my-feature-v1 if you need to refer
118back to it in the future.
119
120Sending v2:
121
122.. code-block:: shell
123
124  $ git checkout my-feature # same topic branch
125  $ # making changes to the commits (using 'git rebase', for example)
126  $ git publish
127
128Your patch series will be sent with 'v2' tag in the subject and the git tip
129will be tagged as my-feature-v2.
130
131Bug reporting
132=============
133
134The QEMU project uses GitLab issues to track bugs. Bugs
135found when running code built from QEMU git or upstream released sources
136should be reported via:
137
138* `<https://gitlab.com/qemu-project/qemu/-/issues>`_
139
140If using QEMU via an operating system vendor pre-built binary package, it
141is preferable to report bugs to the vendor's own bug tracker first. If
142the bug is also known to affect latest upstream code, it can also be
143reported via GitLab.
144
145For additional information on bug reporting consult:
146
147* `<https://wiki.qemu.org/Contribute/ReportABug>`_
148
149
150ChangeLog
151=========
152
153For version history and release notes, please visit
154`<https://wiki.qemu.org/ChangeLog/>`_ or look at the git history for
155more detailed information.
156
157
158Contact
159=======
160
161The QEMU community can be contacted in a number of ways, with the two
162main methods being email and IRC:
163
164* `<mailto:qemu-devel@nongnu.org>`_
165* `<https://lists.nongnu.org/mailman/listinfo/qemu-devel>`_
166* #qemu on irc.oftc.net
167
168Information on additional methods of contacting the community can be
169found online via the QEMU website:
170
171* `<https://wiki.qemu.org/Contribute/StartHere>`_
172