| /qemu/ |
| H A D | COPYING | 18 the GNU Lesser General Public License instead.) You can apply it to
22 price. Our General Public Licenses are designed to make sure that you
24 this service if you wish), that you receive source code or can get it
25 if you want it, that you can change the software or use pieces of it
26 in new free programs; and that you know you can do these things.
29 anyone to deny you these rights or to ask you to surrender the rights.
30 These restrictions translate to certain responsibilities for you if you
31 distribute copies of the software, or if you modify it.
33 For example, if you distribute copies of such a program, whether
34 gratis or for a fee, you must give the recipients all the rights that
[all …]
|
| H A D | qemu.sasl | 1 # If you want to use VNC remotely without TLS, then you *must*
5 # If you are only using TLS, then you can turn on any mechanisms
6 # you like for authentication, because TLS provides the encryption
8 # If you are only using UNIX sockets then encryption is not
27 # You can also list many mechanisms at once, and the VNC server will
|
| /qemu/linux-headers/LICENSES/preferred/ |
| H A D | GPL-2.0 | 37 the GNU Library General Public License instead.) You can apply it to
41 price. Our General Public Licenses are designed to make sure that you
43 this service if you wish), that you receive source code or can get it
44 if you want it, that you can change the software or use pieces of it
45 in new free programs; and that you know you can do these things.
48 anyone to deny you these rights or to ask you to surrender the rights.
49 These restrictions translate to certain responsibilities for you if you
50 distribute copies of the software, or if you modify it.
52 For example, if you distribute copies of such a program, whether
53 gratis or for a fee, you must give the recipients all the rights that
[all …]
|
| /qemu/docs/system/ |
| H A D | gdb.rst | 7 (the "gdbstub"). This allows you to debug guest code in the same
8 way that you might with a low-level debug facility like JTAG
9 on real hardware. You can stop and start the virtual machine,
16 guest until you tell it to from gdb. (If you want to specify which
35 Then you can use gdb normally. For example, type 'c' to launch the
67 confusion when debugging such things you either need to update gdb's
77 hard to follow what's going on. Unless you are specifically trying to
78 debug some interaction between kernel and user-space you are better
97 When you connect gdb to the gdbstub, it will automatically
98 connect to the first inferior; you can display the CPUs in this
[all …]
|
| H A D | target-openrisc.rst | 20 For QEMU's OpenRISC system emulation, you must specify which board model you
24 If you intend to boot Linux, it is possible to have a single kernel image that
32 If you already have a system image or a kernel that works on hardware and you
34 help`` output. If it is listed, then you can probably use that board model. If
36 on QEMU. (You might be able to extract the filesystem and use that with a
39 If you don't care about reproducing the idiosyncrasies of a particular
43 use in virtual machines. You'll need to compile Linux with a suitable
|
| H A D | target-riscv.rst | 19 so typically you don't need to specify the CPU type by hand, except for
25 For QEMU's RISC-V system emulation, you must specify which board
26 model you want to use with the ``-M`` or ``--machine`` option;
36 If you already have a system image or a kernel that works on hardware
37 and you want to boot with QEMU, check whether QEMU lists that machine
38 in its ``-machine help`` output. If it is listed, then you can probably
40 will almost certainly not boot on QEMU. (You might be able to
44 If you don't care about reproducing the idiosyncrasies of a particular
48 real hardware and is designed for use in virtual machines. You'll
57 undocumented; you can get a complete list by running
|
| H A D | target-arm.rst | 8 You can use either ``qemu-system-arm`` or ``qemu-system-aarch64``
29 the hardware has), so typically you don't need to specify the CPU type
35 For QEMU's Arm system emulation, you must specify which board
36 model you want to use with the ``-M`` or ``--machine`` option;
46 If you already have a system image or a kernel that works on hardware
47 and you want to boot with QEMU, check whether QEMU lists that machine
48 in its ``-machine help`` output. If it is listed, then you can probably
50 will almost certainly not boot on QEMU. (You might be able to
54 If you don't care about reproducing the idiosyncrasies of a particular
58 real hardware and is designed for use in virtual machines. You'll
|
| H A D | images.rst | 15 You can create a disk image with the command::
20 kilobytes. You can add an ``M`` suffix to give the size in megabytes and
30 If you use the option ``-snapshot``, all disk images are considered as
32 created in ``/tmp``. You can however force the write back to the raw
43 order to use VM snapshots, you must have at least one non removable and
74 you can always make VM snapshots, but they are deleted as soon as you
|
| /qemu/docs/devel/ |
| H A D | submitting-a-pull-request.rst | 15 you to.
30 the original author if the patch was not written by you. This is because
31 with a pull request you're now indicating that the patch has passed via
32 you rather than directly from the original author.
35 people have reviewed the patches you're putting in the pull request,
36 make sure you've copied their signoffs across. (If you use the `patches
39 you're updating patches manually or in some other way you'll need to
44 have passed the standard code review processes. In particular if you've
45 corrected issues in one round of code review, you need to send your
46 fixed patch series as normal to the list; you can't put it in a pull
[all …]
|
| H A D | submitting-a-patch.rst | 8 some guidelines about submitting them. If you follow these, you'll
12 This page seems very long, so if you are only trying to post a quick
22 …- States you are legally able to contribute the code. See :ref:`patch_emails_must_include_a_signed…
28 You do not have to subscribe to post (list policy is to reply-to-all to
30 start), although you may find it easier as a subscriber to pick up good
31 ideas from other posts. If you do subscribe, be prepared for a high
33 moderated; first-time posts from an email address (whether or not you
37 The larger your contribution is, or if you plan on becoming a long-term
39 Reading the table of contents below should already give you an idea of
41 read the parts that you have doubts about.
[all …]
|
| H A D | build-environment.rst | 13 You can find additional instructions on `QEMU wiki <https://wiki.qemu.org/>`_:
37 You first need to enable `Sources List <https://wiki.debian.org/SourcesList>`_.
47 You first need to install `Homebrew <https://brew.sh/>`_. Then, use it to
57 You first need to install `MSYS2 <https://www.msys2.org/>`_.
64 Then, you can open a windows shell, and enter msys2 env using:
72 dependencies. You can start with this list of packages using pacman:
74 Note: Dependencies need to be installed again if you use a different MSYS2
79 # update MSYS2 itself, you need to reopen your shell at the end.
95 If you want to install all dependencies, it's possible to use recipe used to
112 Meson detects x86_64 processes emulated, so you need to manually set the cpu,
|
| H A D | stable-process.rst | 28 If you think the patch would be important for users of the current release
38 * Preferred: Make sure that the stable maintainers are on copy when you send
46 to ``qemu-stable@nongnu.org`` if you use git send-email, which is where
49 * You can also reply to a patch and put ``qemu-stable@nongnu.org`` on copy
50 directly in your mail client if you think a previously submitted patch
53 * If a maintainer judges the patch appropriate for stable later on (or you
57 * If you judge an already merged patch suitable for stable, send a mail
70 the patch as part of back-porting things across branches. You may also
71 nominate other patches that you think are suitable for inclusion. After
|
| H A D | clocks.rst | 148 At creation, the period of the clock is 0: the clock is disabled. You can
151 Note that if you are creating a clock with a fixed period which will never
152 change (for example the main clock source of a board), then you'll have
160 You can give a clock a callback function in several ways:
178 When you register the callback you specify a mask of ClockEvent values
179 that you are interested in. The callback will only be called for those
194 different functions for different events. You must register a single
195 callback which listens for all of the events you are interested in,
269 mechanism so you can configure a clock to make its children
270 run at a different period from its own. If you call the
[all …]
|
| /qemu/docs/system/devices/ |
| H A D | usb.rst | 4 QEMU can emulate a PCI UHCI, OHCI, EHCI or XHCI USB controller. You can
24 only controller you need. With only a single USB controller (and
38 When running EHCI in standalone mode you can add UHCI or OHCI
49 You can use the standard ``-device`` switch to add a EHCI controller to
52 ``-device usb-ehci,id=ehci``. This will give you a USB 2.0 bus named
55 When adding USB devices using the ``-device`` switch you can specify the
83 you, which you can use like this:
129 you need to explicitly create a ``scsi-hd`` or ``scsi-cd`` device
151 automatically create SCSI disks for you. ``usb-bot`` supports up to
153 i.e. for three devices you must use 0+1+2. The 0+1+5 numbering from the
[all …]
|
| H A D | canokey.rst | 60 If you want to install libcanokey-qemu in a different place,
88 Note: you should keep this file carefully as it may contain your private key!
93 After the guest OS boots, you can check that there is a USB device.
95 For example, If the guest OS is an Linux machine. You may invoke lsusb
103 You may setup the key as guided in [6]_. The console for the key is at [7]_.
113 If you want to trace what happens inside the secure key, when compiling
114 libcanokey-qemu, you should add ``-DQEMU_DEBUG_OUTPUT=ON`` in cmake command
121 If you want to trace events happened in canokey.c, use
128 If you want to capture USB packets between the guest and the host, you can:
139 multiple CanoKey QEMU running, namely you can not
|
| H A D | usb-u2f.rst | 18 The ``u2f-passthru`` device allows you to connect a real hardware
23 In addition, the dedicated pass-through allows you to share a single
27 You can specify the host U2F key to use with the ``hidraw``
33 If you don't specify the device, the ``u2f-passthru`` device will
59 Assuming that you have a working libu2f-emu installed on the host,
68 It is the default if you do not pass any other options to the device.
73 You can pass the device the path of a setup directory on the host
84 You can also manually pass the device the paths to each of these files,
85 if you don't want them all to be in the same directory, using the options
|
| /qemu/.gitlab-ci.d/cirrus/ |
| H A D | README.rst | 13 There is, however, some one-time setup required. If you want FreeBSD and macOS
14 builds to happen when you push to your GitLab repository, you need to
18 be kept up to date, so you can create it and then forget about it;
28 for Cirrus CI to properly recognize the project. You can check whether
41 of it can impersonate you as far as Cirrus CI is concerned.
44 general you'll want to be able to trigger Cirrus CI builds from non-protected
47 Once this one-time setup is complete, you can just keep pushing to your GitLab
48 repository as usual and you'll automatically get the additional CI coverage.
|
| /qemu/docs/ |
| H A D | qdev-device-use.txt | 6 more buses for children. You can specify a device's parent bus with
45 The new way keeps the parts separate: you create the host part with
55 Instead of bus=BUS,unit=UNIT, you can also say index=IDX.
95 As for all PCI devices, you can add bus=PCI-BUS,addr=DEVFN to
109 Without any -device floppy,... you get an empty unit 0 and no unit
110 1. You can use -nodefaults to suppress the default unit 0, see
117 This lets you control PCI device class and MSI-X vectors.
122 As for all PCI devices, you can add bus=PCI-BUS,addr=DEVFN to
156 The new way keeps the parts separate: you create the host part with
176 This lets you control I/O ports and IRQs.
[all …]
|
| H A D | pcie_sriov.txt | 34 you would need to add a PCI Express capability in the normal PCI
35 capability list. You might also want to add an ARI (Alternative
66 For cleanup, you simply call:
72 2) Similarly in the implementation of the virtual function, you need to
74 except for the SR/IOV capability. Then you need to set up the VF BARs as
101 You should now see 4 VFs with lspci.
102 To turn SR/IOV off again - the standard requires you to turn it off before you can enable
112 To disable the VFs again then, you simply have to unload the driver:
|
| /qemu/docs/system/arm/ |
| H A D | vexpress.rst | 48 - QEMU will default to creating one CPU unless you pass a different
53 TrustZone or the Virtualization Extensions: if you want these you
70 recommended (and also useful if you build a lot of different targets).
72 points to the root of the Linux source tree. You can drop $SRC if you
80 By default you will want to boot your rootfs off the sdcard interface.
82 DTB you could also add devices to the virtio-mmio bus.
|
| H A D | versatile.rst | 36 recommended (and also useful if you build a lot of different targets).
38 points to the root of the Linux source tree. You can drop $SRC if you
46 You may want to enable some additional modules if you want to boot
54 You can then boot with a command line like:
|
| /qemu/pc-bios/ |
| H A D | edk2-licenses.txt | 243 IS GOVERNED BY THE TERMS AND CONDITIONS OF THIS AGREEMENT BETWEEN YOU AND
245 INDICATED OR REFERENCED BELOW. BY USING THE CONTENT, YOU AGREE THAT YOUR
248 REFERENCED BELOW. IF YOU DO NOT AGREE TO THE TERMS AND CONDITIONS OF THIS
250 AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW, THEN YOU MAY NOT
254 on the TianoCore site is provided to you under the terms and conditions of the
260 TianoCore site is provided to you under the terms and conditions of the
268 You accept and agree to the following terms and conditions for Your
270 for the license granted to Intel hereunder, You reserve all right,
274 * "You" or "Contributor" shall mean the copyright owner or legal
286 that is intentionally submitted by You to the TianoCore site for
[all …]
|
| /qemu/python/ |
| H A D | README.rst | 10 ``setup.py``. You will generally invoke it by doing one of the following:
13 environment. If you are inside a virtual environment, they will
14 install there. If you are not, it will attempt to install to the
18 local python packages. If you are inside of a virtual environment,
19 this will fail; you want the first invocation above.
21 If you append the ``--editable`` or ``-e`` argument to either invocation
60 invoke them without installation, you can invoke e.g.:
80 - ``README.rst`` you are here!
|
| /qemu/include/hw/ssi/ |
| H A D | ssi.h | 39 /* if you have standard or no CS behaviour, just override transfer.
51 /* if you have non-standard CS behaviour override this to take control
93 * This function is useful if you have created @dev via qdev_new()
94 * (which takes a reference to the device it returns to you), so that
95 * you can set properties on it before realizing it. If you don't need
99 * If you are embedding the SSI peripheral into another QOM device and
104 * would be incorrect. (Instead you would want ssi_realize(), which
|
| /qemu/docs/system/s390x/ |
| H A D | bootdevices.rst | 7 For classical mainframe guests (i.e. LPAR or z/VM installations), you always
8 have to explicitly specify the disk where you want to boot from (or "IPL" from,
11 So for booting an s390x guest in QEMU, you should always mark the
12 device where you want to boot from with the ``bootindex`` property, for
31 Note that you really have to use the ``bootindex`` property to select the
40 support for scanning through the available block devices. So in case you did
48 This also means that you should avoid the classical short-cut commands like
51 ``-cdrom`` option even does not give you a real (virtio-scsi) CD-ROM device on
52 s390x. Due to technical limitations in the QEMU code base, you will get a
76 the kernel names, so you only get a list without names here.
[all …]
|