This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Same problem on RHEL 6.3

Can confirm I see this problem on RHEL 6.3 too.

Please provide an update with the status of this issue.

(In reply to )> Please provide an update with the status of this issue.Unfortunatelly still no luck to get eToken to work in KVM VM.Using following components:Fedora release 16 (Verne) x86_64kernel-3.6.10-2.fc16.x86_64qemu-kvm-0.15.1-8.fc16.x86_64qemu-img-0.15.1-8.fc16.x86_64qemu-kvm-tools-0.15.1-8.fc16.x86_64qemu-system-x86-0.15.1-8.fc16.x86_64qemu-common-0.15.1-8.fc16.x86_64Tested eiher with "Default" and "USB2" USB Controller Mode in KVM.

This issue has been open for almost a year.  Since there isn't a workaround or fix yet, can this errata be documented in the Technical Notes document?

Anyone hitting an issue on RHEL, please file a separate bug there.Sorry for the general lack of response, but given that F16 is EOL if about a month, and USB support in qemu has changed quite a bit between F16 version and current state of things, my recommendation would be to try out Fedora 18, and if you can reproduce the issue I'll raise it with the USB guys.

I can try things out with F18 and report back in any case so we can decide what to to with this issue.(In reply to )

This message is a reminder that Fedora 16 is nearing its end of life.Approximately 4 (four) weeks from now Fedora will stop maintainingand issuing updates for Fedora 16. It is Fedora's policy to close allbug reports from releases that are no longer maintained. At that timethis bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'.Package Maintainer: If you wish for this bug to remain open because youplan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life.Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora.Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.The process we are following is described here:

(In reply to )> I can try things out with F18 and report back in any case so we can decide> what to to with this issue.(In reply to )I've tested things out with F17. Same behaviour.Following components are in use:qemu-common-1.0.1-2.fc17.x86_64qemu-kvm-1.0.1-2.fc17.x86_64kernel-3.6.11-1.fc17.x86_64qemu-kvm-tools-1.0.1-2.fc17.x86_64qemu-system-x86-1.0.1-2.fc17.x86_64qemu-img-1.0.1-2.fc17.x86_64

We tried this out on Fedora 18 and encountered the same problem.  Can you raise the issue with the USB guys?

Don, for completeness can you please provide the following:qemu package versionsqemu command lineguest OSlsusb -vvv of the devicedescribe how things are failing in the guest

Created  lsusb -vvv output of the device

F18:qemu-system-x86-1.2.2-11.fc18.x86_64qemu-img-1.2.0-23.fc18.x86_64qemu-kvm-1.2.2-11.fc18.x86_64qemu-common-1.2.2-11.fc18.x86_64kernel-3.6.10-4.fc18.x6_64Guest OSs:Windows Server 2008 R2 SP1 and Windows Server 2012lsusb -vvv output:  Please see attachmentDescription of how things are failing in the guest:Used Virtual Machine Manager to direct assign a USB device to a guest.  This works fine if the guest is Linux, but with a Windows guest it doesn't get assigned.  The device is removed from the host, and the guest OS has a yellow bang in device manager under Universal Serial Bus Controllers > USB Mass Storage Device.  In device properties, the general tab has the following device status: This device cannot start. (Code 10)An invalid parameter was passed to a service or function.  The events tab has an error event: Device not started (USBSTOR).  The device not started event has the following information:  Device USB\VID_0BC2&PID_2400\2GJ11QJ6____had a problem starting.Driver Name: usbstor.infClass GUID: {36FC9E60-C464-11CF-8056-444553540000}Service: USBSTORLower Filters:Upper Filters: Problem: 0xAStatus: 0x0The Windows Event Manager logged the following information for the same error event described above:Log Name: Microsoft-Windows-Kernel-PnP/Device ConfigurationSource: Kernel-PnpEvent ID:  411Level: WarningUser: SYSTEMOpCode: InfoTried two USB devices on and they produced the same results.

Hans, Gerd, anything else to check for here?

Hi all,(In reply to Cole Robinson from )> Hans, Gerd, anything else to check for here?Denise, can you check what the usb controller type is set to in the virtual hardware details tab? If it is set to default or 1, can you try changing it to 2 ?Also you're using host redirection, so can you please check /var/log/libvirt/qemu/
          
           .log and if there are any USB related messages there, collect them and attach here?Thanks,Hans
          

Just my 5 cents.I finally got Alladin eToken to work on F18 with the following components:qemu-system-sparc-1.2.2-11.fc18.x86_64kernel-modules-extra-3.8.11-200.fc18.x86_64qemu-system-xtensa-1.2.2-11.fc18.x86_64qemu-system-mips-1.2.2-11.fc18.x86_64qemu-system-x86-1.2.2-11.fc18.x86_64kernel-3.9.2-200.fc18.x86_64qemu-user-1.2.2-11.fc18.x86_64qemu-system-ppc-1.2.2-11.fc18.x86_64qemu-system-sh4-1.2.2-11.fc18.x86_64qemu-system-s390x-1.2.2-11.fc18.x86_64qemu-system-alpha-1.2.2-11.fc18.x86_64qemu-img-1.2.2-11.fc18.x86_64qemu-system-or32-1.2.2-11.fc18.x86_64qemu-1.2.2-11.fc18.x86_64qemu-system-unicore32-1.2.2-11.fc18.x86_64qemu-system-microblaze-1.2.2-11.fc18.x86_64kernel-doc-3.9.2-200.fc18.noarchqemu-system-m68k-1.2.2-11.fc18.x86_64qemu-kvm-1.2.2-11.fc18.x86_64kernel-modules-extra-3.8.9-200.fc18.x86_64kernel-headers-3.9.2-200.fc18.x86_64kernel-modules-extra-3.9.2-200.fc18.x86_64qemu-system-lm32-1.2.2-11.fc18.x86_64qemu-kvm-tools-1.2.2-11.fc18.x86_64qemu-system-cris-1.2.2-11.fc18.x86_64qemu-common-1.2.2-11.fc18.x86_64qemu-system-arm-1.2.2-11.fc18.x86_64USB controller model for the virtual machine set to: Model USB 2Guest OS: Windows 7 64 bit.

Denise, please see , more info has been requested.

Setting the USB controller type to 2 instead of 1 (default) works.  The log for the VM (/var/log/libvirt/qemu/
          
           .log) didn't have any USB specific information when I tried using controller type 1.
          

Hi,Thanks for testing!(In reply to denise.p.berry from )> Setting the USB controller type to 2 instead of 1 (default) works.  The log> for the VM (/var/log/libvirt/qemu/
          
           .log) didn't have any USB specific> information when I tried using controller type 1.That explains things then, the device you're trying to redirect is considered not compatible with a USB-1 controller, before we had USB-2 support we did not check that, but now we only allow redirecting USB-2 devices to a USB-1 controller if the meet certain criteria and the device apparently does not,Since moving to an USB-2 controller fixes this I'm going to close this bug.Regards,Hans
          

FYI: CentOS 7.0, and presumably RHEL 7.0, are affected by this issue also.Changing the USB controller from "default" to "USB2" fixed compatibility with my SATA hard drive in a  USB2 dock (13fd:1240 "Generic External").