From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 207707] New: USB pass through to qemu/kvm causes CDROM reset and "device not configured"
Date: Tue, 12 May 2020 22:20:52 +0000 [thread overview]
Message-ID: <bug-207707-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=207707
Bug ID: 207707
Summary: USB pass through to qemu/kvm causes CDROM reset and
"device not configured"
Product: Virtualization
Version: unspecified
Kernel Version: 4.19.121
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: kvm
Assignee: virtualization_kvm@kernel-bugs.osdl.org
Reporter: steffen@sdaoden.eu
Regression: No
Hello.
I update my 4.19 kernel each Saturday.
In March i wrote a C program that accesses CDDA data (toc, CD-TEXT, etc), and
ported it to *BSD via qemu/kvm via USB pass through (i could). I updated the
binary (s-cdda) last on March 16th.
Now, two weeks ago i wanted to pass through the USB CD-ROM again, and it did
not work no more with error as below. This was directly after updating to qemu
5.0.0, so i reinstalled 4.2.0, with which i did the above, but it did no longer
work, too.
This is CRUX-Linux 3.5, and libusb has not changed. The only thing that really
changed otherwise is the kernel, i would say.
I used this USB CD-ROM:
May 11 22:25:32 kent kernel: usb 1-1: new high-speed USB device number 5 using
xhci_hcd
May 11 22:25:32 kent kernel: usb 1-1: New USB device found, idVendor=0e8d,
idProduct=1806, bcdDevice= 0.00
May 11 22:25:32 kent kernel: usb 1-1: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
May 11 22:25:32 kent kernel: usb 1-1: Product: MT1887
May 11 22:25:32 kent kernel: usb 1-1: Manufacturer: MediaTek Inc
May 11 22:25:32 kent kernel: usb 1-1: SerialNumber: S16D6YMG2003AB
May 11 22:25:32 kent kernel: usb-storage 1-1:1.0: USB Mass Storage device
detected
May 11 22:25:32 kent kernel: scsi host0: usb-storage 1-1:1.0
May 11 22:25:33 kent kernel: scsi 0:0:0:0: CD-ROM TSSTcorp CDDVDW
SE-218GN TS00 PQ: 0 ANSI: 0
May 11 22:25:33 kent kernel: sr 0:0:0:0: Power-on or device reset occurred
May 11 22:25:33 kent kernel: sr 0:0:0:0: [sr0] scsi3-mmc drive: 24x/24x writer
dvd-ram cd/rw xa/form2 cdda tray
May 11 22:25:33 kent kernel: cdrom: Uniform CD-ROM driver Revision: 3.20
May 11 22:25:33 kent kernel: sr 0:0:0:0: Attached scsi CD-ROM sr0
May 11 22:25:33 kent kernel: sr 0:0:0:0: Attached scsi generic sg0 type 5
And it works. I start qemu, the device disappears on the host, the guest OS
detects it during boot, and this causes a "reset":
May 11 22:27:31 kent kernel: usb 1-1: reset high-speed USB device number 5
using xhci_hcd
After which the device is still not back in the host, and also inaccessible in
the guest (FreeBSD says "device not configured" when i try to access it).
Is this right here, or should i open an USB bug?
Happy to help or test, thank you!
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2020-05-12 22:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 22:20 bugzilla-daemon [this message]
2021-01-28 20:51 ` [Bug 207707] USB pass through to qemu/kvm causes CDROM reset and "device not configured" bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-207707-28872@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).