From: Sven <1096714@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1096714] Re: qemu 1.3.0: usb devices shouldn't have same vendor/product ID and same serial
Date: Wed, 26 Jul 2017 17:03:18 -0000 [thread overview]
Message-ID: <150108859848.19726.12224153859464032794.malone@chaenomeles.canonical.com> (raw)
In-Reply-To: 20130107012337.1165.80927.malonedeb@gac.canonical.com
This bug is more than 4 years old. Why did I even bother writing it? Is
the problem still there in recent qemu versions?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1096714
Title:
qemu 1.3.0: usb devices shouldn't have same vendor/product ID and same
serial
Status in QEMU:
New
Bug description:
Boot Windows XP with
./qemu-system-i386 -device pci-ohci -device usb-tablet
and then with
./qemu-system-i386 -device pci-ohci -device usb-kbd
and you will notice, that the usb keyboard is not detected. In fact,
Windows XP detects the usb tablet and loads the driver for the tablet
instead of the driver for the keyboard.
The problem seems to be, that vendor and product ID and even the
seriel of both the usb tablet and the usb keyboard are the same as an
lsusb reveiles. Hence, Windows XP doesn't detect when you replace the
tablet by a keyboard and vice versa. I didn't check other USB devices,
but it seems a bad idea to me to have devices with the same
vendor/product Id. I'm not aware, whether it is sufficient to change
the seriel numbers of the devices.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1096714/+subscriptions
next prev parent reply other threads:[~2017-07-26 17:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 1:23 [Qemu-devel] [Bug 1096714] [NEW] qemu 1.3.0: usb devices shouldn't have same vendor/product ID and same serial Sven
2017-07-26 16:24 ` [Qemu-devel] [Bug 1096714] " Michal Suchanek
2017-07-26 17:03 ` Sven [this message]
2017-07-26 18:00 ` Dr. David Alan Gilbert
2017-07-27 8:22 ` Gerd Hoffmann
2017-07-27 14:20 ` Michal Suchanek
2021-05-03 11:27 ` Thomas Huth
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=150108859848.19726.12224153859464032794.malone@chaenomeles.canonical.com \
--to=1096714@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.