Lines Matching refs:usb
46 ``-usb`` switch. QEMU will create the UHCI controller as function of
47 the PIIX3 chipset. The USB 1.1 bus will carry the name ``usb-bus.0``.
52 ``-device usb-ehci,id=ehci``. This will give you a USB 2.0 bus named
62 -usb \\
63 -device usb-ehci,id=ehci \\
64 -device usb-tablet,bus=usb-bus.0 \\
65 -device usb-storage,bus=ehci.0,drive=usbstick
91 Using the ``-usb`` switch for ``q35`` machines will create a similar
100 USB devices can be connected with the ``-device usb-...`` command line
103 ``usb-mouse``
107 ``usb-tablet``
113 ``usb-storage,drive=drive_id``
124 -device nec-usb-xhci,id=xhci \\
125 -device usb-storage,bus=xhci.0,drive=stick
127 ``usb-uas``
131 specify what those disks are backed by. One ``usb-uas`` device can
141 -device nec-usb-xhci,id=xhci \\
142 -device usb-uas,id=uas,bus=xhci.0 \\
147 ``usb-bot``
149 same USB bulk-only transport protocol interface as ``usb-storage``, but
150 the QEMU command line option works like ``usb-uas`` and does not
151 automatically create SCSI disks for you. ``usb-bot`` supports up to
152 16 LUNs. Unlike ``usb-uas``, the LUN numbers must be continuous,
154 ``usb-uas`` example above won't work with ``usb-bot``.
156 ``usb-mtp,rootdir=dir``
160 ``usb-host,hostbus=bus,hostaddr=addr``
163 ``usb-host,vendorid=vendor,productid=product``
166 ``usb-wacom-tablet``
171 ``usb-kbd``
174 ``usb-serial,chardev=id``
178 ``usb-braille,chardev=id``
186 |qemu_system| [...] -chardev braille,id=brl -device usb-braille,chardev=brl
194 ``usb-net[,netdev=id]``
201 |qemu_system| [...] -netdev user,id=net0 -device usb-net,netdev=net0
203 ``usb-ccid``
206 ``usb-audio``
210 :doc:`usb-u2f`
229 -device usb-tablet,bus=usb-bus.0,port=1
233 -device usb-hub,bus=usb-bus.0,port=2
238 -device usb-storage,bus=usb-bus.0,port=2.4,drive=...
246 (qemu) device_add usb-tablet,bus=usb-bus.0,port=1,id=my-tablet
252 The ``usb-bot`` and ``usb-uas`` devices can be hotplugged. In the hotplug
258 #. ``device-add usb-bot,id=foo``
277 2. Verify that ``/proc/bus/usb`` is working (most Linux distributions
282 ls /proc/bus/usb
291 chown -R myuid /proc/bus/usb
308 device_add usb-host,vendorid=0x1234,productid=0x5678
311 You can use the option ``-device usb-host,...`` to do the same.
318 ``usb-host`` properties for specifying the host device
323 the only way to specify the host device. ``usb-host`` supports
362 -usb \\
363 -device usb-ehci,id=ehci \\
364 -device usb-host,bus=usb-bus.0,hostbus=3,hostport=1 \\
365 -device usb-host,bus=ehci.0,hostbus=1,hostport=1
367 ``usb-host`` properties for reset behavior
371 whenever the guest is allowed to reset the physical usb device on the
375 The guest is not allowed to reset the (physical) usb device.
379 initialized (aka no usb bus address assigned). Usually this results
385 The reason for this existing are broken usb devices. In theory one
386 should be able to reset (and re-initialize) usb devices at any time.
387 In practice that may result in shitty usb device firmware crashing and
392 usb device at hand, so it's a trial-and-error game. If the default
396 record usb transfers
399 All usb devices have support for recording the usb traffic. This can
402 ``-device usb-mouse,pcap=mouse.pcap``