Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1110141

Summary:

"husb error submitting iso urb 0: 28" with passthough usb camera

Product:

Red Hat Enterprise Linux 6

Reporter:

mazhang <mazhang>

Component:

qemu-kvm

Assignee:

Gerd Hoffmann <kraxel>

Status:

CLOSED NOTABUG

QA Contact:

Virtualization Bugs <virt-bugs>

Severity:

medium

Docs Contact:

Priority:

medium

Version:

6.5

CC:

acathrow, bsarathy, juli, juzhang, mazhang, michen, mkenneth, qzhang, sluo, virt-maint

Target Milestone:

Target Release:

---

Hardware:

Unspecified

OS:

Unspecified

Whiteboard:

Fixed In Version:

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2014-07-02 12:24:44 UTC

Type:

Bug

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

---

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Embargoed:

Attachments:

Description	Flags
detail messages of usb camera.	none

Description mazhang 2014-06-17 06:51:05 UTC

Description of problem:
Passthouth usb camera to guest, got this error while initialize the camera in guest by "Microsoft LifeCam".

Version-Release number of selected component (if applicable):

Host:
qemu-kvm-debuginfo-0.12.1.2-2.427.el6.x86_64
qemu-kvm-0.12.1.2-2.427.el6.x86_64
qemu-img-0.12.1.2-2.427.el6.x86_64
qemu-kvm-tools-0.12.1.2-2.427.el6.x86_64
kernel-2.6.32-477.el6.x86_64

Guest:
win7-64

How reproducible:
always

Steps to Reproduce:
1.Boot vm with passthough usb camera.
[root@m2 home]# lsusb
...
Bus 001 Device 030: ID 045e:00f7 Microsoft Corp. LifeCam VX-1000

cli:
/usr/libexec/qemu-kvm \
-M pc \
-cpu SandyBridge \
-m 4G \
-smp 4,sockets=2,cores=2,threads=1,maxcpus=160 \
-enable-kvm \
-name rhel6.6 \
-uuid 990ea161-6b67-47b2-b803-19fb01d30d12 \
-smbios type=1,manufacturer='Red Hat',product='RHEV Hypervisor',version=el6,serial=koTUXQrb,uuid=feebc8fd-f8b0-4e75-abc3-e63fcdb67170 \
-k en-us \
-rtc base=localtime,clock=host,driftfix=slew \
-nodefaults \
-monitor stdio \
-qmp tcp:0:6666,server,nowait \
-boot menu=on,strict=on \
-bios /usr/share/seabios/bios.bin \
-chardev socket,id=seabios,path=/tmp/seabios,server,nowait \
-device isa-debugcon,chardev=seabios,iobase=0x402 \
-monitor unix:/tmp/guest-sock,server,nowait \
-vga qxl \
-spice port=5900,disable-ticketing \
-drive file=/home/win2012r2-64.qcow2,if=none,id=drive-virtio-disk0,format=qcow2,cache=none,werror=stop,rerror=stop,aio=threads \
-device virtio-blk-pci,scsi=off,bus=pci.0,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 \
-netdev tap,id=hostnet0,vhost=on \
-device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:39:13:2c,bootindex=2 \
-readconfig /home/ich9-ehci-uhci.cfg \
-device usb-host,hostbus=1,hostaddr=30,id=camera0

2.Open "Microsoft LifeCam", then check the camera status.
3.

Actual results:
Qemu-kvm output follow messages:
QEMU 0.12.1 monitor - type 'help' for more information
(qemu) husb: open device 1.30
husb: grabbed usb device 1.30

(qemu) main_channel_link: add main channel client
main_channel_handle_parsed: net test: latency 0.235000 ms, bitrate 419672131 bps (400.230533 Mbps)
inputs_connect: inputs channel client create
red_dispatcher_set_cursor_peer: 
(qemu) husb: config #1 need 1
husb: 3 interfaces claimed for configuration 1
(qemu) info usb
  Device 0.1, Port 1, Speed 12 Mb/s, Product USB camera
(qemu) husb: config #1 need 1
husb: 3 interfaces claimed for configuration 1
husb: config #1 need 1
husb: 3 interfaces claimed for configuration 1

(qemu) husb error submitting iso urb 0: 28
husb error submitting iso urb 0: 28
husb error submitting iso urb 0: 28
husb error submitting iso urb 0: 28
husb error submitting iso urb 0: 28
husb error submitting iso urb 0: 28
husb error submitting iso urb 0: 28
husb error submitting iso urb 0: 28
husb error submitting iso urb 0: 28
husb error submitting iso urb 0: 28
husb error submitting iso urb 0: 28
husb error submitting iso urb 0: 28
husb error submitting iso urb 0: 28
...


Expected results:
no error.

Additional info:
Just this camera "Microsoft Corp. LifeCam VX-1000" hit this problem, we have another camera "Z-Star Microelectronics Corp" works well.

Comment 2 Gerd Hoffmann 2014-07-02 07:37:44 UTC

Attach lspci -v output for the camera please.

Comment 3 mazhang 2014-07-02 07:47:17 UTC

Created attachment 914027 [details]
detail messages of usb camera.

Comment 4 Gerd Hoffmann 2014-07-02 12:24:44 UTC

[ ... ]
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            1
          Transfer Type            Isochronous
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0000  1x 0 bytes
        bInterval               1
[ ... ]

wMaxPacketSize == 0 ???

Device at fault here I'd say.