USB passthrough device ID interpreted as decimal instead of hex

Bug #514610 reported by James Bellinger
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libvirt (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: virt-manager

In 10.04, at least, when adding a device, the second half of lsusb's output is interpreted as decimal, when it is in fact hexidecimal.
As a result, to make a USB passthrough device work, I had to edit the XML file from 0x1d0b (which virt-manager filled in) to 0x7435 for my Sansa Clip (as well as enabling USB in /etc/apparmor.d/abstractions/libvirt-qemu, of course). This is a bug. lsusb's output is hex.

That is to say, virt-manager took lsusb on the host's 0781:7435 and made it 0781:1d0b. Naturally this did not match anything on the host, so the guest got nothing.

I imagine this is not something that would be noticed for devices where the second half is 1 or 2, but for this device it mattered.

Related branches

Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

This is actually a libvirt bug.

affects: virt-manager (Ubuntu) → libvirt (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libvirt - 0.7.5-5ubuntu7

---------------
libvirt (0.7.5-5ubuntu7) lucid; urgency=low

  * debian/patches/0010-Use-base-16-for-product-vendor.patch: parse the USB
    and PCI product and vendor ids in hexadecimal. This fixes incorrect
    USB ids being used in virt-manager. (LP: #514610)
 -- Marc Deslauriers <email address hidden> Sun, 07 Feb 2010 11:08:23 -0500

Changed in libvirt (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.