On Mon, May 21, 2012 at 8:11 PM, Hans de Goede <hdego...@redhat.com> wrote: >>> The problem is that with usb device redirection we can have 1 device >>> already redirected, and then the user asks to redirect another device >>> to the virtual machine, so we install a driver for the other device, >>> and then need to be able to use the other device without re-init, since >>> we still have the first device open. Note that we use one context for >>> all devices, which from our pov makes sense since we also do "device >>> management" and for this we have one context where we enumerate devices, >>> once we've the device enumerated in this context, it is easiest to >>> keep using the same context for actually talking to the device. >> >> >> Just wondering how usbredir works. If you replace the existing >> non-winusb driver with the winusb driver. In that case, the existing >> function of the device is no longer valid under the host. For example, >> you keyboard, mouse and flash drive will no longer work as a >> keyboard, mouse or flash drive. > > Correct, you are in effect plugging the device out of the host and into > the vm.
Then it seems to me that the step to install the libusbx supported driver is a bit different from other similar technology. I do not remember that Microsoft Virtual PC (eg: XP mode under Windows 7) or VirtualBox needs to change the driver on the host PC side. The VM side of course will need the driver. -- Xiaofan ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
