Home
last modified time | relevance | path

Searched full:using (Results 1 – 25 of 1111) sorted by relevance

12345678910>>...45

/qemu/tests/qemu-iotests/
H A D153.out15 Is another process using the image [TEST_DIR/t.qcow2]?
19 Is another process using the image [TEST_DIR/t.qcow2]?
27 Is another process using the image [TEST_DIR/t.qcow2]?
31 Is another process using the image [TEST_DIR/t.qcow2]?
35 Is another process using the image [TEST_DIR/t.qcow2]?
40 Is another process using the image [TEST_DIR/t.qcow2]?
45 Is another process using the image [TEST_DIR/t.qcow2]?
49 Is another process using the image [TEST_DIR/t.qcow2]?
53 Is another process using the image [TEST_DIR/t.qcow2]?
57 Is another process using the image [TEST_DIR/t.qcow2]?
[all …]
/qemu/docs/system/devices/
H A Dnet.rst9 connect the NIC of the guest to a real network (e.g. by using a TAP
11 guest instances running in another QEMU process (e.g. by using the
14 Using TAP network interfaces
31 lines using the TAP network interfaces.
41 Using the user mode network stack
44 By using the option ``-net user`` (default configuration if no ``-net``
67 shall work, however. If you're using QEMU on Linux >= 3.0, it can use
74 When using the built-in TFTP server, the router is also the TFTP server.
76 When using the ``'-netdev user,hostfwd=...'`` option, TCP or UDP
80 Using passt as the user mode network stack
[all …]
H A Divshmem.rst19 shared memory region. Interrupt support requires using a shared memory
20 server and using a chardev socket to connect to it. The code for the
22 syntax when using the shared memory server is:
33 When using the server, the guest will be assigned a VM ID (>=0) that
34 allows guests using the same server to communicate via interrupts.
45 migration using the PCI hotplug support.
53 Instead of specifying the <shm size> using POSIX shm, you may specify a
H A Dccid.rst24 reader and smart card (i.e. not backed by a physical device) using this device.
44 Using ccid-card-emulated with hardware
47 user, using libcacard, QEMU acts as another client using ccid-card-emulated::
51 Using ccid-card-emulated with certificates stored in files
99 Using ccid-card-passthru with client side hardware
110 Using ccid-card-passthru with client side certificates
127 This is a typical interchange of messages when using the passthru card device.
/qemu/docs/
H A Drdma.txt39 migration using RDMA is capable of using both technologies because of
47 for a working build of QEMU to run successfully using RDMA Migration.
66 high-performance RDMA hardware using the following command:
76 Example performance of this using an idle VM in the previous example
106 Here is a brief summary of total migration time and downtime using RDMA:
107 Using a 40gbps infiniband link performing a worst-case stress test,
108 using an 8GB RAM virtual machine:
110 Using the following command:
120 active use and the VM itself is completely idle using the same 40 gbps
127 you have to migrate using RDMA.
[all …]
H A Dqcow2-cache.txt30 The 'qemu-img create' command supports specifying the size using the
69 bits, but a different value can be set using the refcount_bits option:
114 Cache sizes can be configured using the -drive option in the
126 (or the cache entry size: see "Using smaller cache sizes" below).
130 value can be modified using the "l2-cache-size" option. QEMU will not use
135 periodically if needed, using the "cache-clean-interval" option (see below).
151 (this can change if you are using internal snapshots, so you may want
159 Using smaller cache entries
170 it smaller than the cluster size. This can be configured using the
H A Dmemory-hotplug.txt33 hotplugged by using any combination of the available memory slots.
47 Using the file backend
50 Besides basic RAM hotplug, QEMU also supports using files as a memory
51 backend. This is useful for using hugetlbfs in Linux, which provides
63 but this allows for a lot of flexibility when using the file backend.
/qemu/docs/system/
H A Ddevice-url-syntax.rst.inc2 In addition to using normal file images for the emulated storage
4 These are specified using a special URL syntax.
47 QEMU supports NBD (Network Block Devices) both using TCP protocol as
50 Syntax for specifying a NBD device using TCP, in preferred URI form:
53 Syntax for specifying a NBD device using Unix Domain Sockets;
60 Syntax for specifying a NBD device using Unix Domain Sockets
85 Currently authentication must be done using ssh-agent. Other
90 use of GlusterFS volumes for hosting VM disk images using TCP and Unix
131 Syntax using a single filename:
173 ';') with each outgoing request. Only supported when using
[all …]
H A Dauthz.rst45 ``joebloggs``, while if using Kerberos/GSSAPI it can have a realm
54 created at startup using the ``-object`` argument, or at runtime using the
167 The object can be created on the command line using
218 On the command line it can be created using
226 here, and it is possible to implement brand new plugins using the PAM API.
232 The authorization driver is created using the ``-object`` argument and then
238 will provide ``tls-authz`` property, while any server using SASL will provide
241 Thus an example using SASL and authorization for the VNC server would look
H A Dsecrets.rst11 secure manner, using the ``secret`` object type.
13 At startup this can be done using the ``-object secret,...`` command line
14 argument. At runtime this can be done using the ``object_add`` QMP / HMP
77 will be launched under. If using mandatory access control such as SELinux, then
90 The secret used as the AES key must always be configured using the file based
119 The earlier mechanisms described are platform agnostic. If using QEMU on a Linux
120 host, it is further possible to pass secrets to QEMU using the Linux keyring:
H A Dmux-chardev.rst.inc1 During emulation, if you are using a character backend multiplexer
2 (which is the default if you are using ``-nographic``) then several
5 changed with ``-echr``. The list below assumes you're using the default.
H A Dgdb.rst19 `Using unix sockets`_ for an example.)
79 off running your guest program with gdb either in the guest or using
99 cluster using the gdb ``info thread`` command, and switch between
100 them using gdb's usual thread-management commands.
120 determining executable automatically. Try using the "file" command.
137 Using unix sockets
152 Start gdb as before, but this time connect using the path to
240 clients can connect to it, e.g., by using a unix socket with proper
/qemu/docs/system/arm/
H A Dorangepi.rst46 The Orange Pi PC machine can start using the standard -kernel functionality
60 and uses a default base year value which can be overridden using the 'base-year' property.
83 simply configure the kernel using the sunxi_defconfig configuration:
130 using the orangepi_pc_defconfig. Also see https://buildroot.org for more information.
132 When using an image as an SD card, it must be resized to a power of two. This can be
143 For example, to boot using the Orange Pi PC Debian image on SD card, simply add the -sd
164 a real board would do using the BootROM. Simply pass the selected image via the -sd
185 U-Boot mainline can be build and configured using the orangepi_pc_defconfig
186 using similar commands as describe above for Linux. Note that it is recommended
191 To start U-Boot using the Orange Pi PC machine, provide the
[all …]
H A Dbananapi_m2u.rst45 The Banana Pi M2U machine can start using the standard -kernel functionality
55 simply configure the kernel using the sunxi_defconfig configuration:
75 to build you own image with buildroot using the bananapi_m2_ultra_defconfig.
83 When using an image as an SD card, it must be resized to a power of two. This can be
97 a real board would do using the BootROM. Simply pass the selected image via the -sd
108 U-Boot mainline can be build and configured using the Bananapi_M2_Ultra_defconfig
109 using similar commands as describe above for Linux. Note that it is recommended
H A Dvirt.rst24 VM migration is not guaranteed when using ``-cpu max``, as features
46 - running guests using the KVM accelerator on aarch64 hardware
47 - large amounts of RAM (at least 255GB, and more if using highmem)
48 - many CPUs (up to 512 if using a GICv3 and highmem)
162 Use the same GIC version the host provides, when using KVM
164 Use the best GIC version possible (same as host when using KVM;
187 using ACPI and guest external abort exceptions. The default is off.
251 - For guests using the Linux kernel boot protocol (this means any
/qemu/tests/tcg/hexagon/
H A Dscatter_gather.c223 /* scatter the 16 bit elements using HVX */
237 /* scatter-accumulate the 16 bit elements using HVX */
251 /* masked scatter the 16 bit elements using HVX */
268 /* scatter the 32 bit elements using HVX */
294 /* scatter-accumulate the 32 bit elements using HVX */
320 /* masked scatter the 32 bit elements using HVX */
354 /* scatter the 16 bit elements with 32 bit offsets using HVX */
370 /* scatter-accumulate the 16 bit elements with 32 bit offsets using HVX */
386 /* masked scatter the 16 bit elements with 32 bit offsets using HVX */
406 /* gather the elements from the scatter16 buffer using HVX */
[all …]
/qemu/docs/devel/
H A Dmultiple-iothreads.rst1 Using Multiple ``IOThread``\ s
16 QEMU is an event-driven program that can do several things at once using an
22 possible to create additional event loop threads using
91 The ``AioContext`` can be obtained from the ``IOThread`` using
92 ``iothread_get_aio_context()`` or for the main loop using
109 The main loop thread can wait synchronously for a condition using
118 ``BlockDriverState`` is associated with an ``AioContext`` using
123 Block layer code must therefore expect to run in an ``IOThread`` and avoid using
/qemu/docs/system/riscv/
H A Dvirt.rst45 "riscv,clint0" if using with OpenSBI BIOS images
50 The ``virt`` machine can start using the standard -kernel functionality
54 firmware and U-Boot proper (S-mode), using the standard -bios functionality.
56 Using flash devices
90 The board has support for the riscv-iommu-pci device by using the following
132 This option also interacts with '-accel kvm'. When using "aia=aplic-imsic"
134 by using "-accel kvm,kernel-irqchip=split". In this case the ``virt`` machine
135 will emulate the APLIC controller instead of using the APLIC controller from
154 64-bit mode, simply configure the kernel using the defconfig configuration:
212 build the U-Boot images using riscv64_spl_defconfig:
/qemu/
H A Dqemu.sasl5 # If you are only using TLS, then you can turn on any mechanisms
8 # If you are only using UNIX sockets then encryption is not
20 # If using TLS with VNC, or a UNIX socket only, it is possible to
37 # If using scram-sha-256 for username/passwds, then this is the file
/qemu/docs/specs/
H A Dppc-spapr-uv-hcalls.rst32 SVM file systems are encrypted using a symmetric key. This key is then
33 wrapped/encrypted using the public key of a trusted system which has the private
35 unwrap/unseal the symmetric key using the system's TPM device or a TPM Resource
39 host system boot. All sensitive in and out values will be encrypted using the
41 any sensitive contents will generally be encrypted using this session key.
/qemu/docs/system/i386/
H A Dmicrovm.rst25 - kvmclock (if using KVM)
40 Using the microvm machine type
62 As no current FW is able to boot from a block device using
64 using a host-side kernel and, optionally, an initrd image.
72 without passing any additional machine-specific option, using the
86 footprint further by disabling some legacy devices. If you're using
/qemu/include/qemu/
H A Dfifo8.h19 * when finished using the fifo. The FIFO is initially empty.
38 * Clients are responsible for checking for fullness using fifo8_is_full().
49 * Clients are responsible for checking the space left in the FIFO using
59 * Clients are responsible for checking for emptyness using fifo8_is_empty().
70 * for checking for emptyness using fifo8_is_empty().
126 * using fifo8_num_used().
153 * using fifo8_num_used().
/qemu/python/
H A DREADME.rst35 See `Installing packages using pip and virtual environments
36 <https://packaging.python.org/guides/installing-using-pip-and-virtual-environments/>`_
40 Using these packages without installing them
43 These packages may be used without installing them first, by using one
48 https://docs.python.org/3/using/cmdline.html#envvar-PYTHONPATH
/qemu/tests/tcg/mips/user/ase/msa/
H A DREADME2 mips64el MSA-enabled CPU (I6400, I6500), using an appropriate MIPS toolchain.
8 They are to be executed using QEMU user mode, using command line:
/qemu/docs/devel/migration/
H A Dmain.rst41 - tcp migration: do the migration using tcp sockets
42 - unix migration: do the migration using unix sockets
43 - exec migration: do the migration using the stdin/stdout through a process.
44 - fd migration: do the migration using a file descriptor that is
46 - file migration: do the migration using a file that is passed to QEMU
52 The file migration also supports using a file that has already been
66 - rdma migration: support is included for migration using RDMA, which
67 transports the page data using ``RDMA``, where the hardware takes
150 Most device data can be described using the ``VMSTATE`` macros (mostly defined
246 forgot to migrate. This is best solved using a subsection.
[all …]

12345678910>>...45