This is likely fixed with the qemu version in raring. Unsubscribing
ubuntu-sponsors.
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu Quantal)
Importance: Undecided
Status: New
** Also affects: qemu-kvm (Ubuntu Quantal)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu Raring)
Importance: Undecided
Status: New
** Also affects: qemu-kvm (Ubuntu Raring)
Importance: Medium
Status: Confirmed
** Changed in: qemu (Ubuntu Raring)
Status: New => Fix Released
** Changed in: qemu (Ubuntu Quantal)
Status: New => Invalid
** Changed in: qemu-kvm (Ubuntu Quantal)
Status: New => Confirmed
** Changed in: qemu-kvm (Ubuntu Quantal)
Importance: Undecided => Medium
** Changed in: qemu-kvm (Ubuntu Raring)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1033727
Title:
USB passthrough doesn't work anymore with qemu-kvm 1.1.1
Status in QEMU:
Fix Released
Status in “qemu” package in Ubuntu:
Fix Released
Status in “qemu-kvm” package in Ubuntu:
Invalid
Status in “qemu” source package in Quantal:
Invalid
Status in “qemu-kvm” source package in Quantal:
Confirmed
Status in “qemu” source package in Raring:
Fix Released
Status in “qemu-kvm” source package in Raring:
Invalid
Status in “qemu-kvm” package in Debian:
Fix Released
Bug description:
Hi,
I have a "Bus 006 Device 002: ID 0d46:3003 Kobil Systems GmbH mIDentity Light
/ KAAN SIM III" (kind of smart card) in an USB port which I make available to a
Windows XP guest.
This worked fine with every older qemu-kvm version I've used so far.
But since 1.1.0 it doesn't work anymore.
The device shows up in the guest, but the software can't access it anymore
(and the guest is pretty unresponsive).
On the host I get every 2 seconds this message:
[ 7719.239528] usb 6-1: reset full-speed USB device number 2 using uhci_hcd
Command line options are:
/usr/bin/kvm
...
-device usb-host,vendorid=0x0d46,productid=0x3003,bus=usb.0,port=3
...
When I switch back to qemu-kvm 1.0.1 everything works fine again.
Any idea what the problem could be?
Thanks
Klaus
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1033727/+subscriptions
