How to get a KVM client using a host USB device

KVM Command Line arguments

-USB Open USB driver, start client USB support

-usbdevice Devname adds USB devices to the client, devname in many forms, as described in Man KVM, where only one form of host:vendor_id:product_id is involved,-usbdevce vendor_id: product_id

Get USB Device Parameters

Before inserting a USB device into the host

$lsusb > Usb.old

After the USB device is plugged into the host

$lsusb > Usb.new

And then

Vimdiff Usb.old usb.new

Find the newly added line, similar to the following line

Bus 002 Device 004:id 13fd:1040 initio Corporation

The two fields following the ID are vendor_id and product_id, respectively.

Mapping USB Devices

The client command line adds these two parameters

sudo kvm-usb-usbdevice host:13fd:1040 ...

So that the client can see the mapped USB device.

Small problem

The mobile hard disk mapped to the client to do the test, the virtual client can not start, from the remote VNC look at the booting from Hard disk ..., search the next also no results, then a flash, is not because the mobile hard disk into a boot disk? Sure enough, modify the boot parameters as follows

-boot Order=c,menu=on

Here added Menu=on, so that when the boot F12 can choose from which drive boot, reboot, and really see the mobile hard drive into the first boot device, select the local hard drive normal boot system, from the client can also see the mobile hard disk.

It is understood that the KVM has not yet command line parameters can be set to boot from the second hard drive, but also someone to mention this thing, suggest order=e from the second hard drive, and so on.

Update

Parameter-usbdevice devname maps ordinary USB devices are available in two formats, Devname can be specified as

Host:bus.addr

host:vendor_id:product_id

Above-usbdevice host:13fd:1040 Specifies host:vendor_id:product_id This format, for the USB device shown in the example, can also set parameters in HOST:BUS.ADDR format

host:2.4

2 of which is the bus number, 4 is the address of the device on the bus 002 Device 004, but using HOST:BUS.ADDR this format has a disadvantage, if the USB device for a socket, its bus and device number will change, and host:vendor_id: PRODUCT_ID This format is unaffected, even if the client is running on another host.

Update Again (09/19/2012):

KVM host two of the same type of USB devices, this two USB devices verdor_id and product_id is exactly the same, that can only be host:bus.addr this way for the client to specify a USB device, or the KVM host is overwhelmed.