From: Wessel Dankers <wsl-launchpad@fruit.je>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 685096] Re: USB Passthrough not working for Windows 7 guest
Date: Sat, 06 Oct 2012 23:14:55 -0000 [thread overview]
Message-ID: <20121006231456.14458.8425.launchpad@gac.canonical.com> (raw)
In-Reply-To: 20101204070046.21747.93608.malonedeb@gandwana.canonical.com
** Changed in: qemu
Status: New => Confirmed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/685096
Title:
USB Passthrough not working for Windows 7 guest
Status in QEMU:
Confirmed
Bug description:
USB Passthrough from host to guest is not working for a 32-bit Windows
7 guest, while it works perfectly for a 32-bit Windows XP guest.
The device appears in the device manager of Windows 7, but with "Error
code 10: device cannot start". I have tried this with numerous USB
thumbdrives and a USB wireless NIC, all with the same result. The
device name and functionality is recognized, so at least some USB
negotiation is taking place.
I am trying this with the latest git-pull of QEMU-KVM.
The command line to launch qemu-kvm for win7 is:
sudo /home/user/local_install/bin/qemu-system-x86_64 -cpu core2duo -m 1024 -smp 2 -vga std -hda ./disk_images/win7.qcow -vnc :1 -boot c -usb -usbdevice tablet -usbdevice host:0781:5150
The command line to launch qemu-kvm for winxp is:
sudo /home/user/local_install/bin/qemu-system-x86_64 -cpu core2duo -m 1024 -smp 2 -usb -vga std -hda ./winxpsp3.qcow -vnc :0 -boot c -usbdevice tablet -usbdevice host:0781:5150
Any help is appreciated.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/685096/+subscriptions
next prev parent reply other threads:[~2012-10-06 23:20 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-04 7:00 [Qemu-devel] [Bug 685096] [NEW] USB Passthrough not working for Windows 7 guest Max Power
2010-12-08 19:30 ` [Qemu-devel] [Bug 685096] " Mirco Bauer
2010-12-15 22:12 ` Carlos-velasco
2010-12-15 22:32 ` Carlos-velasco
2012-02-01 17:35 ` sydenis
2012-10-06 23:14 ` Wessel Dankers [this message]
2013-04-19 22:35 ` Steve Rencontre
2013-04-24 19:16 ` Daniël van Eeden
2013-04-29 14:09 ` Serge Hallyn
2013-04-30 7:41 ` Yolanda Robla
2013-05-03 8:33 ` Sam Stoelinga
2013-05-30 18:25 ` Tobin Davis
2013-05-30 19:28 ` Wessel Dankers
2013-07-04 3:15 ` Sam Stoelinga
2013-07-05 11:43 ` Serge Hallyn
2013-07-05 12:05 ` Wessel Dankers
2013-08-01 2:46 ` Sam Stoelinga
2013-08-05 13:21 ` Serge Hallyn
2013-09-09 22:14 ` Serge Hallyn
2013-11-05 15:30 ` Jens Frederich
2013-11-05 16:05 ` Serge Hallyn
2013-11-05 16:33 ` Jens Frederich
2013-11-05 16:34 ` Jens Frederich
2013-11-10 17:19 ` debfreak
2013-11-13 3:07 ` FanFan
2013-11-18 16:32 ` Serge Hallyn
2014-01-15 1:32 ` Gonglei
2014-02-01 18:19 ` Manuel Baesler
2014-02-01 20:47 ` Manuel Baesler
2014-02-06 17:52 ` Serge Hallyn
2014-02-12 15:27 ` Manuel Baesler
2014-06-11 10:25 ` Michal Suchanek
2014-06-13 16:50 ` Michal Suchanek
2014-06-13 17:29 ` Serge Hallyn
2014-06-13 19:12 ` Michal Suchanek
2015-01-16 21:39 ` Serge Hallyn
2015-08-12 16:59 ` Serge Hallyn
2015-08-20 16:48 ` Nehal J Wani
2015-12-22 17:48 ` FFO
2017-05-19 10:29 ` Thomas Huth
2018-01-12 13:28 ` Thomas Huth
2018-05-30 17:02 ` Andreas Hasenack
2018-05-30 17:02 ` Andreas Hasenack
2018-07-30 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=20121006231456.14458.8425.launchpad@gac.canonical.com \
--to=wsl-launchpad@fruit.je \
--cc=685096@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 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).