KVM clients use host USB devices

When a KVM client uses a host USB device, sometimes the KVM client still needs to use a USB device, such as a USB key and other KVM command line parameters-usb to open the USB driver, usb support for starting the client-usb devicedevname adds a USB device to the client. there are multiple formats of devname. for details, see mankvm. the KVM client uses the host usb device.
Sometimes the KVM client still needs to use USB devices, such as USB keys and other KVM command line parameters-usb to open the usb driver and start the usb support-USB device devname to add USB devices to the client, devname has multiple forms. for details, see man kvm. here only one form is involved: host: vendor_id: product_id, that is,-usbdevce vendor_id: product_id get USB device parameters $ lsusb> usb before the usb device is inserted into the host. after the old usb device is inserted into the host, $ lsusb> usb. new and then vimdiff usb. old usb. find the newly added line, similar to the following two fields after Bus 002 Device 004: ID 13fd: 1040 Initio Corporation ID: vendor_id and product_id ing usb Device client command line to add this Two parameters: sudo kvm-usb-usbdevice host: 13fd: 1040... In this way, the client can see that the mapped USB device has a small problem and maps the mobile hard disk to the client for testing. the virtual client cannot be started, from the remote vnc, we can see that we have stayed at Booting from Hard Disk ..., After searching, there was no result, and the Flash came. Was it because the mobile hard disk became the boot disk? Indeed, modify the boot parameters as follows-boot order = c, menu = on and add menu = on. in this way, press F12 to choose which drive to start and restart, as a result, the mobile hard disk became the first boot device. select the local hard disk to start the system normally, and you can also see the mobile hard disk from the client. It is understood that there is no command line parameter for KVM to be set to start from the second hard disk. someone is also asking about this. order = e is recommended to start from the second hard disk, and so on. Update: The parameter-USB device devname maps to a common USB device in two formats. the devname can be specified as host: bus. addrhost: vendor_id: product_id above-USB device host: 13fd: 1040 specifies the format of host: vendor_id: product_id. for USB devices displayed in this example, you can also use host: bus. addr format setting parameter host: 2.4 where 2 is the Bus number, 4 is the address of the Device on the bus Bus bus 002 Device 004, but use host: Bus. the addr format has a disadvantage. if a USB device has another plug-in, its bus and device number will change, while the format of host: vendor_id: product_id will not be affected, the same is true even if the client is switched to another host. Update again (): two usb devices of the same type are inserted on the KVM host. the verdor_id and product_id of the two usb devices are exactly the same, and they can only be transmitted through host: bus. addr specifies a usb device for the client. Otherwise, the kvm host will be overwhelmed.