/qemu/docs/system/ |
H A D | cpu-models-mips.rst.inc | 9 The following CPU models are supported for use on MIPS32 hosts. 10 Administrators / applications are recommended to use the CPU model that 11 matches the generation of the host CPUs in use. In a deployment with a 13 compatibility is required, use the newest CPU model that is compatible 41 The following CPU models are supported for use on MIPS64 hosts. 42 Administrators / applications are recommended to use the CPU model that 43 matches the generation of the host CPUs in use. In a deployment with a 45 compatibility is required, use the newest CPU model that is compatible 85 The following CPU models are supported for use on nanoMIPS hosts. 87 matches the generation of the host CPUs in use. In a deployment with a [all …]
|
H A D | target-openrisc.rst | 21 want to use with the ``-M`` or ``--machine`` option; the default machine is 28 the kernel. The kernel can then use this to configure itself for the machine. 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 41 and just want to run Linux, the best option is to use the ``virt`` board. This 43 use in virtual machines. You'll need to compile Linux with a suitable
|
H A D | security.rst | 13 QEMU supports many different use cases, some of which have stricter security 21 The virtualization use case covers cloud and virtual private server (VPS) 23 use cases rely on hardware virtualization extensions to execute guest code 36 real-world use cases and treated as security bugs if this is the case. 41 The non-virtualization use case covers emulation using the Tiny Code Generator 43 the non-virtualization use case should meet the same security requirements as 44 the virtualization use case. However, for historical reasons much of the 45 non-virtualization use case code was not written with these security 48 Bugs affecting the non-virtualization use case are not considered security 49 bugs at this time. Users with non-virtualization use cases must not rely on [all …]
|
H A D | target-arm.rst | 8 You can use either ``qemu-system-arm`` or ``qemu-system-aarch64`` 18 then built into machines which can vary still further even if they use 36 model you want to use with the ``-M`` or ``--machine`` option; 49 use that board model. If it is not listed, then unfortunately your image 51 extract the filesystem and use that with a different kernel which 56 disk, etc., and just want to run Linux, the best option is to use the 58 real hardware and is designed for use in virtual machines. You'll
|
H A D | qemu-block-drivers.rst.inc | 121 Name of the hash algorithm to use for PBKDF algorithm 279 Name of the hash algorithm to use for PBKDF algorithm 323 Specifies which VMDK subformat to use. Valid options are 340 Specifies which VHD subformat to use. Valid options are 410 it. For example, use ``/dev/cdrom`` to access to the CDROM. 457 host data (use the ``-snapshot`` command line so that the 473 directory tree. In order to use it, just type: 498 - use non-ASCII filenames 499 - use "-snapshot" together with ":rw:" 532 and then you can use it with two guests: [all …]
|
H A D | gdb.rst | 13 In order to use gdb, launch QEMU with the ``-s`` and ``-S`` options. 17 TCP port to use or to use something other than TCP for the gdbstub 18 connection, use the ``-gdb dev`` option instead of ``-s``. See 35 Then you can use gdb normally. For example, type 'c' to launch the 40 Here are some useful tips in order to use gdb on system code: 46 3. Use ``set architecture i8086`` to dump 16 bit code. Then use 140 An alternate method for connecting gdb to the QEMU gdbstub is to use 146 instruct the gdbserver to use that device: 157 Note that to use a unix socket for the connection you will need 199 the single step, but not timers, you would use:
|
H A D | target-riscv.rst | 15 then built into machines which can vary still further even if they use 26 model you want to use with the ``-M`` or ``--machine`` option; 39 use that board model. If it is not listed, then unfortunately your image 41 extract the file system and use that with a different kernel which 46 disk, etc., and just want to run Linux, the best option is to use the 48 real hardware and is designed for use in virtual machines. You'll
|
H A D | vnc-security.rst | 40 mode as it requires the use of the DES cipher. Password authentication 57 The QEMU VNC server also implements the VeNCrypt extension allowing use 59 authentication. The use of x509 certificates is strongly recommended, 73 Unprivileged users will want to use a private directory, for example 126 for authentication, but assuming use of one supporting SSF, then QEMU 156 The following documentation assumes use of the Cyrus SASL implementation 182 This says to use the 'GSSAPI' mechanism with the Kerberos v5 protocol, 202 Note that all mechanisms, except GSSAPI, should be combined with use of
|
H A D | cpu-models-x86.rst.inc | 20 recommended CPU to use, provided live migration is not required. 54 depending on the machine type is in use. 67 The following CPU models are preferred for use on Intel hosts. 68 Administrators / applications are recommended to use the CPU model that 69 matches the generation of the host CPUs in use. In a deployment with a 71 compatibility is required, use the newest CPU model that is compatible 159 Recommended to allow guest OS to use 1GB size pages. 205 processor is vulnerable, use the Intel VERW instruction (a 230 The following CPU models are preferred for use on AMD hosts. 321 Recommended to allow guest OS to use 1GB size pages [all …]
|
/qemu/pc-bios/ |
H A D | petalogix-ml605.dts | 68 xlnx,dcache-use-fsl = < 0x00 >; 116 xlnx,use-barrel = < 0x01 >; 118 xlnx,use-dcache = < 0x01 >; 119 xlnx,use-div = < 0x01 >; 120 xlnx,use-ext-brk = < 0x01 >; 123 xlnx,use-fpu = < 0x01 >; 124 xlnx,use-hw-mul = < 0x02 >; 125 xlnx,use-icache = < 0x01 >; 126 xlnx,use-interrupt = < 0x01 >; 127 xlnx,use-mmu = < 0x03 >; [all …]
|
H A D | petalogix-s3adsp1800.dts | 59 xlnx,dcache-use-fsl = <0x01>; 95 xlnx,use-barrel = <0x01>; 96 xlnx,use-dcache = <0x01>; 97 xlnx,use-div = <0x00>; 98 xlnx,use-ext-brk = <0x01>; 101 xlnx,use-fpu = <0x00>; 102 xlnx,use-hw-mul = <0x01>; 103 xlnx,use-icache = <0x01>; 105 xlnx,use-mmu = <0x03>; 243 xlnx,use-parity = <0x00>; [all …]
|
/qemu/docs/devel/ |
H A D | style.rst | 9 Please use the script checkpatch.pl in the scripts directory to check 38 to use tab stops of eight positions. 313 QEMU makes fairly extensive use of the macro pre-processor to 341 If it's file-size related, use off_t. 342 If it's file-offset related (i.e., signed), use off_t. 343 If it's just counting small numbers use "unsigned int"; 381 off_t, use matching types for any corresponding variables. 430 use the GLib memory allocation routines 505 so instead of e.g. isalnum you should use qemu_isalnum. 738 Do not use printf(), fprintf() or monitor_printf(). Instead, use [all …]
|
/qemu/qapi/ |
H A D | audio.json | 19 # @mixing-engine: use QEMU's mixing engine to mix all streams inside 24 # @fixed-settings: use fixed settings for host input/output. When 28 # @frequency: frequency to use when using fixed settings (default 33 # @voices: number of voices to use (default 1) 35 # @format: sample format to use when using fixed settings (default 74 # @dev: the name of the ALSA device to use (default 'default') 118 # @dev: the name of the sndio device to use (default 'default') 202 # @exact-name: use the exact name requested otherwise JACK 290 # @name: name of the sink/source to use 334 # @name: name of the sink/source to use [all …]
|
/qemu/scripts/coccinelle/ |
H A D | error-use-after-free.cocci | 1 // Find and fix trivial use-after-free of Error objects 19 // How to use: 20 // spatch --sp-file scripts/coccinelle/error-use-after-free.cocci \ 22 // --no-show-diff ( FILES... | --use-gitgrep . )
|
/qemu/docs/config/ |
H A D | q35-virtio-serial.cfg | 12 # CHANGE ME before being able to use this configuration! 43 # We use '-display none' to prevent QEMU from creating a 44 # graphical display window, which would serve no use in 47 # to the host's stdio; use 'Ctrl+A h' to learn how to 54 # We use the q35 machine type and enable KVM acceleration 140 # We use virtio-scsi here so that we can (hot)plug a large 183 # We use virtio-net for improved performance over emulated
|
H A D | mach-virt-serial.cfg | 13 # CHANGE ME before being able to use this configuration! 40 # We use '-display none' to prevent QEMU from creating a 41 # graphical display window, which would serve no use in 44 # to the host's stdio; use 'Ctrl+A h' to learn how to 51 # We use the virt machine type and enable KVM acceleration 60 # command line, but we can configure the guest to use the 190 # We use virtio-scsi here so that we can (hot)plug a large 233 # We use virtio-net for improved performance over emulated
|
/qemu/tests/qemu-iotests/ |
H A D | pylintrc | 6 # file where it should appear only once). You can also use "--disable=all" to 8 # you want to run only the similarities checker, you can use "--disable=all 10 # no Warning level messages displayed, use "--disable=all --enable=classes 23 # If we really care to make it statically knowable, we'll use mypy.
|
H A D | 242.out | 104 Checking "in-use" flag... 118 [0]: in-use 123 [0]: in-use 135 "in-use" 142 "in-use",
|
/qemu/ |
H A D | qemu-options.hx | 121 use ``x-use-canonical-path-for-ramblock-id=off`` backend option 615 use -``device``. 1666 Instead of ``-cdrom`` you can use: 2340 Specify which ciphers to use. 2743 Applications intending to use OEM strings data are encouraged to use their application name as 2788 Here is an example of use: 3174 guest screen 0, use the following: 3719 use either protocol. 3892 sysfs entry to use. 4992 HXCOMM Internal use [all …]
|
/qemu/scripts/qapi/ |
H A D | pylintrc | 8 # file where it should appear only once). You can also use "--disable=all" to 10 # you want to run only the similarities checker, you can use "--disable=all 12 # no Warning level messages displayed, use "--disable=all --enable=classes
|
/qemu/docs/system/devices/ |
H A D | usb.rst | 26 need to use the bus= parameter when adding USB devices. 34 devices. The companion controller setup is more convenient to use 83 you, which you can use like this: 89 Then use ``bus=ehci.0`` to assign your USB devices to that bus. 188 or alternatively, use the following equivalent shortcut: 242 specify some unique id which you can use to refer to the device. 243 You can then use ``device_del`` to unplug the device later. 287 devices you want to use. For testing, the following suffices: 301 You should see the list of the devices you can use (Never try to use 311 You can use the option ``-device usb-host,...`` to do the same. [all …]
|
/qemu/docs/system/s390x/ |
H A D | 3270.rst | 16 to actually be able to use it, attach the ``x3270`` emulator to the chardev. 30 * Start the guest. In the guest, use ``chccwdev -e 0.0.000a`` to enable 44 * If you want to use the 3270 device as the Linux kernel console instead of 46 the guest's kernel command line. The kernel then should use the 3270 as
|
/qemu/linux-headers/LICENSES/exceptions/ |
H A D | Linux-syscall-note | 8 To use this exception add it with the keyword WITH to one of the 13 NOTE! This copyright does *not* cover user programs that use kernel 14 services by normal system calls - this is merely considered normal use
|
/qemu/tests/qapi-schema/ |
H A D | reserved-member-u.json | 2 # We reject use of 'u' as a member name, to allow it for internal use in
|
/qemu/docs/ |
H A D | igd-assign.txt | 14 by Intel, does not support direct video output. The intention is to use 16 or to use this mode in combination with guest-based remote access software, 55 It may therefore be necessary to use kernel boot options video=vesafb:off or 72 DVI, or DisplayPort) may be unsupported in some use cases. In the author's 79 management tools like libvirt. To make use of legacy mode, simply remove all 80 other graphics options and use "-nographic" and either "-vga none" or 86 device making use of any other bus address other than 02.0. libvirt will 109 recommended that firmware should make use of this fw_cfg entry for any
|