| /qemu/docs/ |
| H A D | qdev-device-use.txt | 1 = How to convert to -device & friends =
5 In qdev, each device has a parent bus. Some devices provide one or
6 more buses for children. You can specify a device's parent bus with
7 -device parameter bus.
9 A device typically has a device address on its parent bus. For buses
23 Example: device i440FX-pcihost is on the root bus, and provides a PCI
24 bus named pci.0. To put a FOO device into its slot 4, use -device
30 A QEMU block device (drive) has a host and a guest part.
32 In the general case, the guest device is connected to a controller
33 device. For instance, the IDE controller provides two IDE buses, each
[all …]
|
| /qemu/qapi/ |
| H A D | qdev.json | 8 # = Device infrastructure (qdev)
14 # @device-list-properties:
16 # List properties associated with a device.
18 # @typename: the type name of a device
29 { 'command': 'device-list-properties',
36 # Add a device.
38 # @driver: the name of the new device's driver
40 # @bus: the device's parent bus (device tree path)
42 # @id: the device's ID, must be unique
46 # @json-cli: If present, the "-device" command line option supports
[all …]
|
| H A D | vfio.json | 12 # An enumeration of the VFIO device migration states.
14 # @stop: The device is stopped.
16 # @running: The device is running.
18 # @stop-copy: The device is stopped and its internal state is
21 # @resuming: The device is stopped and its internal state is available
24 # @running-p2p: The device is running in the P2P quiescent state.
26 # @pre-copy: The device is running, tracking its internal state and
29 # @pre-copy-p2p: The device is running in the P2P quiescent state,
42 # This event is emitted when a VFIO device migration state is changed.
44 # @device-id: The device's id, if it has one.
[all …]
|
| H A D | block.json | 102 # @device: Block device name
104 # @id: The name or QOM path of the guest device (since: 2.8)
111 # @deprecated: Member @device is deprecated. Use @id instead.
114 # - If @device is not a valid block device, DeviceNotFound
116 # .. note:: Ejecting a device with no media results in success.
126 'data': { '*device': { 'type': 'str', 'features': [ 'deprecated' ] },
133 # Opens a block device's tray. If there is a block driver state tree
135 # it will remain associated to the block device, so closing the tray
145 # - if the BlockBackend denoted by @device does not have a guest
146 # device attached to it
[all …]
|
| H A D | virtio.json | 43 # "path": "/machine/peripheral-anon/device[4]/virtio-backend"
51 # "path": "/machine/peripheral-anon/device[2]/virtio-backend"
55 # "path": "/machine/peripheral-anon/device[1]/virtio-backend"
59 # "path": "/machine/peripheral-anon/device[0]/virtio-backend"
71 # Information about a vhost device. This information will only be
72 # displayed if the vhost device is active.
117 # Full status of the virtio device with most VirtIODevice members.
118 # Also includes the full status of the corresponding vhost device if
119 # the vhost device is active.
123 # @device-id: VirtIODevice ID
[all …]
|
| /qemu/tests/qemu-iotests/ |
| H A D | 186.out | 6 Testing: -device floppy
9 /machine/peripheral-anon/device[1]: [not inserted]
10 Attached to: /machine/peripheral-anon/device[N]
11 Removable device: not locked, tray closed
14 Testing: -device floppy,id=qdev_id
19 Removable device: not locked, tray closed
22 Testing: -device ide-cd
25 /machine/peripheral-anon/device[1]: [not inserted]
26 Attached to: /machine/peripheral-anon/device[N]
27 Removable device: not locked, tray closed
[all …]
|
| H A D | 172.out | 64 Attached to: /machine/unattached/device[N]
65 Removable device: not locked, tray closed
69 Attached to: /machine/unattached/device[N]
70 Removable device: not locked, tray closed
114 Attached to: /machine/unattached/device[N]
115 Removable device: not locked, tray closed
119 Attached to: /machine/unattached/device[N]
120 Removable device: not locked, tray closed
123 Attached to: /machine/unattached/device[N]
124 Removable device: not locked, tray closed
[all …]
|
| H A D | 172 | 100 # '-device floppy', even to a different slot, the default drive is disabled.
128 echo === Using -drive if=none and -device ===
130 check_floppy_qtree -drive if=none,file="$TEST_IMG" -device floppy,drive=none0
131 check_floppy_qtree -drive if=none,file="$TEST_IMG" -device floppy,drive=none0,unit=1
133 -device floppy,drive=none0 -device floppy,drive=none1,unit=1
144 echo === Mixing -fdX and -device ===
147 check_floppy_qtree -fda "$TEST_IMG" -drive if=none,file="$TEST_IMG.2" -device floppy,drive=none0
148 check_floppy_qtree -fda "$TEST_IMG" -drive if=none,file="$TEST_IMG.2" -device floppy,drive=none0,un…
150 check_floppy_qtree -fdb "$TEST_IMG" -drive if=none,file="$TEST_IMG.2" -device floppy,drive=none0
151 check_floppy_qtree -fdb "$TEST_IMG" -drive if=none,file="$TEST_IMG.2" -device floppy,drive=none0,un…
[all …]
|
| H A D | 026.out | 31 write failed: No space left on device
36 write failed: No space left on device
41 qemu-io: Failed to flush the L2 table cache: No space left on device
42 qemu-io: Failed to flush the refcount block cache: No space left on device
43 write failed: No space left on device
48 qemu-io: Failed to flush the L2 table cache: No space left on device
49 qemu-io: Failed to flush the refcount block cache: No space left on device
50 write failed: No space left on device
89 write failed: No space left on device
90 read failed: No space left on device
[all …]
|
| H A D | 026.out.nocache | 31 write failed: No space left on device
36 write failed: No space left on device
41 qemu-io: Failed to flush the L2 table cache: No space left on device
42 qemu-io: Failed to flush the refcount block cache: No space left on device
43 write failed: No space left on device
48 qemu-io: Failed to flush the L2 table cache: No space left on device
49 qemu-io: Failed to flush the refcount block cache: No space left on device
50 write failed: No space left on device
89 write failed: No space left on device
90 read failed: No space left on device
[all …]
|
| H A D | 083.out | 4 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo
8 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo
12 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo
16 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo
20 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo
24 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo
28 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo
32 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo
36 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo
40 qemu-io: can't open device nbd+tcp://127.0.0.1:PORT/foo
[all …]
|
| /qemu/docs/specs/ |
| H A D | pci-ids.rst | 5 Red Hat, Inc. donates a part of its device ID range to QEMU, to be used for
8 Contact Gerd Hoffmann <kraxel@redhat.com> to get a device ID assigned
14 The 1000 -> 10ff device ID range is used as follows for virtio-pci devices.
15 Note that this allocation is separate from the virtio device IDs, which are
19 network device (legacy)
21 block device (legacy)
23 balloon device (legacy)
25 console device (legacy)
27 SCSI host bus adapter device (legacy)
29 entropy generator device (legacy)
[all …]
|
| H A D | riscv-iommu.rst | 9 The emulation includes a PCI reference device (riscv-iommu-pci) and a platform
10 bus device (riscv-iommu-sys) that QEMU RISC-V boards can use. The 'virt'
13 riscv-iommu-pci reference device
16 This device implements the RISC-V IOMMU emulation as recommended by the section
17 "Integrating an IOMMU as a PCIe device" of `iommu1.0.0`_: a PCI device with base
20 As a reference device it doesn't implement anything outside of the specification,
23 To include the device in the 'virt' machine:
27 $ qemu-system-riscv64 -M virt -device riscv-iommu-pci,[optional_pci_opts] (...)
29 This will add a RISC-V IOMMU PCI device in the board following any additional
41 The current Linux kernel support will use the IOMMU device to create IOMMU groups
[all …]
|
| /qemu/tests/qtest/fuzz/ |
| H A D | generic_fuzz_configs.h | 2 * Generic Virtual-Device Fuzzing Target Configs
27 "-device virtio-9p,fsdev=hshare,mount_tag=hshare " in generic_fuzzer_virtio_9p_args()
36 "-device virtio-net,netdev=net0 -netdev user,id=net0",
40 .args = "-machine q35 -device virtio-blk,drive=disk0 "
45 .args = "-machine q35 -device virtio-scsi,num_queues=8 "
46 "-device scsi-hd,drive=disk0 "
51 .args = "-machine q35 -nodefaults -device virtio-gpu",
55 .args = "-machine q35 -nodefaults -device virtio-vga",
59 .args = "-machine q35 -nodefaults -device virtio-rng",
63 .args = "-machine q35 -nodefaults -device virtio-balloon",
[all …]
|
| /qemu/docs/devel/migration/ |
| H A D | vfio.rst | 2 VFIO device migration
5 Migration of virtual machine involves saving the state for each device that
14 continue whilst the VFIO device state is transferred to the destination, this
29 the device, but the device can respond to incoming ones. Additionally, all
31 the device enters this state.
39 support P2P migration. Single VFIO device migration is allowed regardless of
42 A detailed description of the UAPI for VFIO device migration can be found in
46 VFIO implements the device hooks for the iterative approach as follows:
50 * A ``load_setup`` function that sets the VFIO device on the destination in
55 device.
[all …]
|
| /qemu/scripts/ |
| H A D | device-crash-test | 22 Run QEMU with all combinations of -machine and -device types,
48 logger = logging.getLogger('device-crash-test')
66 # * device: regexp, full match only
80 # devices that don't work out of the box because they require extra options to "-device DEV":
81 # DEVICE | ERROR MESSAGE
82 {'device':'.*-(i386|x86_64)-cpu', 'expected':True}, # CPU socket-id is not set
83 …{'device':'icp', 'expected':True}, # icp_realize: required link 'xics' not fou…
84 …{'device':'ics', 'expected':True}, # ics_base_realize: required link 'xics' no…
85 # "-device ide-cd" does work on more recent QEMU versions, so it doesn't have expected=True
86 {'device':'ide-cd'}, # No drive specified
[all …]
|
| /qemu/docs/system/devices/ |
| H A D | usb.rst | 21 |qemu_system| -device qemu-xhci
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
63 -device usb-ehci,id=ehci \\
64 -device usb-tablet,bus=usb-bus.0 \\
65 -device usb-storage,bus=ehci.0,drive=usbstick
68 device to the EHCI adapter.
100 USB devices can be connected with the ``-device usb-...`` command line
108 Pointer device that uses absolute coordinates (like a touchscreen).
[all …]
|
| H A D | usb-u2f.rst | 1 Universal Second Factor (U2F) USB Key Device
8 The second factor is provided by a device implementing the U2F
9 protocol. In case of a USB U2F security key, it is a USB HID device
12 QEMU supports both pass-through of a host U2F key device to a VM,
18 The ``u2f-passthru`` device allows you to connect a real hardware
25 simple host device assignment pass-through.
28 option, which takes the host path to a Linux ``/dev/hidrawN`` device:
31 |qemu_system| -usb -device u2f-passthru,hidraw=/dev/hidraw0
33 If you don't specify the device, the ``u2f-passthru`` device will
34 autoscan to take the first U2F device it finds on the host (this
[all …]
|
| /qemu/docs/system/ |
| H A D | virtio-net-failover.rst | 9 virtio-net device. Before migration the vfio device is unplugged and data flows
10 through the virtio-net device, on the target side another vfio-pci device is
14 The two devices are called primary and standby device. The fast hardware based
15 networking device is called the primary device and the virtio-net device is the
16 standby device.
23 devices are allowed as primary device. The user needs to ensure that primary
30 networking device by falling back to a virtio-net device for the duration of
33 another host QEMU will unplug the primary device via the PCIe based hotplug
34 handler and traffic will go through the virtio-net device. On the target
35 system the primary device will be automatically plugged back and the
[all …]
|
| H A D | device-emulation.rst | 3 Device Emulation
15 Device Front End
18 A device front end is how a device is presented to the guest. The type
19 of device presented should match the hardware that the guest operating
21 ``--device`` command line option. Running QEMU with the command line
22 options ``--device help`` will list all devices it is aware of. Using
23 the command line ``--device foo,help`` will list the additional
24 configuration options available for that device.
29 Device Buses
34 automatically created. In most cases the BUS a device is attached to
[all …]
|
| /qemu/include/hw/ |
| H A D | qdev-core.h | 14 * DOC: The QEMU Device API
17 * TYPE_DEVICE. The device API introduces the additional methods of
18 * @realize and @unrealize to represent additional stages in a device
27 * 2) device realization via the #DeviceState.realized property
30 * during device introspection already), and the latter may return error
56 * Hiding a device
59 * To hide a device, a DeviceListener function hide_device() needs to
60 * be registered. It can be used to defer adding a device and
63 * later. It must return if it wants the device to be hidden or
64 * visible. When the handler function decides the device shall be
[all …]
|
| /qemu/tests/qtest/ |
| H A D | device-plug-test.c | 2 * QEMU device plug/unplug handling
24 * Other devices might get removed along with the removed device. Skip in wait_device_deleted_event()
25 * these. The device of interest will be the last one. in wait_device_deleted_event()
30 if (!data || !qdict_get(data, "device")) { in wait_device_deleted_event()
34 qstr = qobject_to(QString, qdict_get(data, "device")); in wait_device_deleted_event()
47 * Request device removal. As the guest is not running, the request won't in process_device_remove()
49 * handled, removing the device. in process_device_remove()
63 g_test_skip("Device virtio-mouse-pci not available"); in test_pci_unplug_request()
71 qtest = qtest_initf("%s -device virtio-mouse-pci,id=dev0", in test_pci_unplug_request()
84 g_test_skip("Device virtio-mouse-pci not available"); in test_q35_pci_unplug_request()
[all …]
|
| /qemu/docs/devel/ |
| H A D | multi-process.rst | 68 Another is the modular nature of QEMU device emulation code provides
69 interface points where the QEMU functions that perform device emulation
74 QEMU device emulation
77 QEMU uses an object oriented SW architecture for device emulation code.
80 code to emulate a device named "foo" is always present in QEMU, but its
81 instantiation code is only run when the device is included in the target
82 VM. (e.g., via the QEMU command line as *-device foo*)
84 The object model is hierarchical, so device emulation code names its
85 parent object (such as "pci-device" for a PCI device) and QEMU will
86 instantiate a parent object before calling the device's instantiation
[all …]
|
| /qemu/docs/system/s390x/ |
| H A D | css.rst | 10 in the form ``<cssid>.<ssid>.<device number>``.
21 Any device may be put into any subchannel set, there is no restriction by
22 device type.
24 The device number can range from ``0-0xffff``.
26 If the ``devno`` property is not specified for a device, QEMU will choose the
27 next free device number in subchannel set 0, skipping to the next subchannel
28 set if no more device numbers are free.
30 QEMU places a device at the first free subchannel in the specified subchannel
31 set. If a device is hotunplugged and later replugged, it may appear at a
38 * a virtio-net device, cssid/ssid/devno automatically assigned::
[all …]
|
| /qemu/block/monitor/ |
| H A D | block-hmp-cmds.c | 160 error_report("Device '%s' not found", id); in hmp_drive_del()
165 error_report("Deleting device added with blockdev-add" in hmp_drive_del()
184 * If this BlockBackend has a device attached to it, its refcount will be in hmp_drive_del()
185 * decremented when the device is removed; otherwise we have to do so here. in hmp_drive_del()
198 const char *device = qdict_get_str(qdict, "device"); in hmp_commit() local
205 if (!strcmp(device, "all")) { in hmp_commit()
210 blk = blk_by_name(device); in hmp_commit()
212 error_report("Device '%s' not found", device); in hmp_commit()
219 error_report("Device '%s' has no medium", device); in hmp_commit()
226 error_report("'commit' error for '%s': %s", device, strerror(-ret)); in hmp_commit()
[all …]
|