From: Celine <hagbardcelin@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1626207] [NEW] -device usb-host failing with usbip_vudc-vhdi_hcd gadget
Date: Wed, 21 Sep 2016 17:31:19 -0000 [thread overview]
Message-ID: <20160921173119.27130.58488.malonedeb@chaenomeles.canonical.com> (raw)
Public bug reported:
I must admit that I do not know if this is a Qemu or a Kernel issue, but
I try reporting here:
When I try to forward a copy of my USB mouse that I made with the new virtual USB device controller in kernel 4.7 I get the following in my log:
[ +0.703256] usb 1-4: reset full-speed USB device number 3 using xhci_hcd
[ +1.020776] usb usb7-port3: Cannot enable. Maybe the USB cable is bad?
[ +0.855013] usb usb7-port3: Cannot enable. Maybe the USB cable is bad?
[ +0.859052] usb usb7-port3: Cannot enable. Maybe the USB cable is bad?
[ +0.857000] usb usb7-port3: Cannot enable. Maybe the USB cable is bad?
[ +0.000141] usb 7-3: USB disconnect, device number 10
[ +0.153056] usb 1-4: reset full-speed USB device number 3 using xhci_hcd
[ +0.703746] usb usb7-port3: Cannot enable. Maybe the USB cable is bad?
[ +0.855001] usb usb7-port3: Cannot enable. Maybe the USB cable is bad?
[ +0.855006] usb usb7-port3: Cannot enable. Maybe the USB cable is bad?
[ +0.855005] usb usb7-port3: Cannot enable. Maybe the USB cable is bad?
[ +0.000009] usb usb7-port3: unable to enumerate USB device
the commands I use for makeing the virtual device are(after making a copy of the report description of my real mouse in /root/usb/kingston_report_desc):
mkdir /sys/kernel/config/usb_gadget/winmouse
cd /sys/kernel/config/usb_gadget/winmouse
echo "0x047d" > idVendor
echo "0x1020" > idProduct
mkdir strings/0x409
echo 2016 > strings/0x409/serialnumber
echo Kensington > strings/0x409/manufacturer
echo "Kensington Expert Mouse" > strings/0x409/product
mkdir configs/c.1
mkdir configs/c.1/strings/0x409
mkdir functions/hid.usb2
echo 2 > functions/hid.usb2/protocol
echo 1 > functions/hid.usb2/subclass
echo 4 > functions/hid.usb2/report_length
cat /root/usb/kingston_report_desc > functions/hid.usb2/report_desc
echo 0xa0 > configs/c.1/bmAttributes
echo 100 > configs/c.1/MaxPower
ln -s functions/hid.usb2 configs/c.1
echo usbip-vudc.2 > UDC
usbip attach -r localhost -d usbip-vudc.2
The virtual mouse then shows up as Bus7,Dev10 and I use the option
-device usb-host,hostbus=7,hostaddr=10,id=hostdev6,bus=usb.0,port=2 in
Qemu to attach it.
This is Qemu 2.7.0 on kernel 4.7.4
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1626207
Title:
-device usb-host failing with usbip_vudc-vhdi_hcd gadget
Status in QEMU:
New
Bug description:
I must admit that I do not know if this is a Qemu or a Kernel issue,
but I try reporting here:
When I try to forward a copy of my USB mouse that I made with the new virtual USB device controller in kernel 4.7 I get the following in my log:
[ +0.703256] usb 1-4: reset full-speed USB device number 3 using xhci_hcd
[ +1.020776] usb usb7-port3: Cannot enable. Maybe the USB cable is bad?
[ +0.855013] usb usb7-port3: Cannot enable. Maybe the USB cable is bad?
[ +0.859052] usb usb7-port3: Cannot enable. Maybe the USB cable is bad?
[ +0.857000] usb usb7-port3: Cannot enable. Maybe the USB cable is bad?
[ +0.000141] usb 7-3: USB disconnect, device number 10
[ +0.153056] usb 1-4: reset full-speed USB device number 3 using xhci_hcd
[ +0.703746] usb usb7-port3: Cannot enable. Maybe the USB cable is bad?
[ +0.855001] usb usb7-port3: Cannot enable. Maybe the USB cable is bad?
[ +0.855006] usb usb7-port3: Cannot enable. Maybe the USB cable is bad?
[ +0.855005] usb usb7-port3: Cannot enable. Maybe the USB cable is bad?
[ +0.000009] usb usb7-port3: unable to enumerate USB device
the commands I use for makeing the virtual device are(after making a copy of the report description of my real mouse in /root/usb/kingston_report_desc):
mkdir /sys/kernel/config/usb_gadget/winmouse
cd /sys/kernel/config/usb_gadget/winmouse
echo "0x047d" > idVendor
echo "0x1020" > idProduct
mkdir strings/0x409
echo 2016 > strings/0x409/serialnumber
echo Kensington > strings/0x409/manufacturer
echo "Kensington Expert Mouse" > strings/0x409/product
mkdir configs/c.1
mkdir configs/c.1/strings/0x409
mkdir functions/hid.usb2
echo 2 > functions/hid.usb2/protocol
echo 1 > functions/hid.usb2/subclass
echo 4 > functions/hid.usb2/report_length
cat /root/usb/kingston_report_desc > functions/hid.usb2/report_desc
echo 0xa0 > configs/c.1/bmAttributes
echo 100 > configs/c.1/MaxPower
ln -s functions/hid.usb2 configs/c.1
echo usbip-vudc.2 > UDC
usbip attach -r localhost -d usbip-vudc.2
The virtual mouse then shows up as Bus7,Dev10 and I use the option
-device usb-host,hostbus=7,hostaddr=10,id=hostdev6,bus=usb.0,port=2 in
Qemu to attach it.
This is Qemu 2.7.0 on kernel 4.7.4
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1626207/+subscriptions
next reply other threads:[~2016-09-21 17:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 17:31 Celine [this message]
2016-09-21 17:36 ` [Qemu-devel] [Bug 1626207] Re: -device usb-host failing with usbip_vudc-vhdi_hcd gadget Celine
2020-11-12 13:11 ` Thomas Huth
2021-01-12 4:17 ` Launchpad Bug Tracker
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=20160921173119.27130.58488.malonedeb@chaenomeles.canonical.com \
--to=hagbardcelin@gmail.com \
--cc=1626207@bugs.launchpad.net \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.