qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: hkran <hkran@linux.vnet.ibm.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
	Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH] Implement the function usb_hub_handle_reset
Date: Wed, 23 Nov 2011 11:16:45 +0800	[thread overview]
Message-ID: <4ECC659D.6080000@linux.vnet.ibm.com> (raw)
In-Reply-To: <4ECB9738.1000506@redhat.com>

On 11/22/2011 08:36 PM, Gerd Hoffmann wrote:
> On 11/22/11 09:58, hkran wrote:
>> Implement the function usb_hub_handle_reset. without it the guest
>> propablly fail to configure the usb device attached to the virtulized
>> hub with a correct address.
>>
>> Typically, attaching more than one usb devices when lauch qemu may lead
>> to the problem.
> What is the exact problem you are trying to fix?
>
> cheers,
>    Gerd
>
>
For example, I use the following command line to lautch qemu to play win7

  /home/huikai/qemu10/bin/qemu-system-x86_64 -enable-kvm -m 1024 -drive  
file=/root/win7_86.img,if=ide  -net user  -net  nic,model=rtl8139 
-localtime -chardev stdio,id=muxstdio -mon  chardev=muxstdio -usb 
-usbdevice tablet -spice port=2345,disable-ticketing -cdrom 
/home/guest/Fedora-15-i686-Live-Desktop.iso -boot once=d -usbdevice 
host:0000:7777

Here, I attatched two usbdevice tablet and a usb storage device 
"host:0000:7777" on the host side. After guest have booted.there will 
not see the usb storage device.
using monitor cmd "info usb" found the below:

  (qemu) info usb
   Device 0.1, Port 1, Speed 12 Mb/s, Product QEMU USB Tablet
   Device 0.3, Port 2, Speed 12 Mb/s, Product QEMU USB Hub
   Device 0.3, Port 2.1, Speed 480 Mb/s, Product host:2.4

the device "host:0000:7777" have not been configured successfully, guest 
OS can not to see it.

I traced qemu and found that there will be several reset cmd issued by 
the guest usb protocol stack during win7 booting, if we left the 
hub_reset to do nothing, the usbdevice attached to it will fail to be 
configured just in above case.
(If we "hot plug-in " a usb device via qemu's monitor, the problem is 
not so easy to be reproduced because the reset cmd only be issued only 
once or none)

(the problem is not always reproduced, but high possibility).

  reply	other threads:[~2011-11-23  3:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-22  8:58 [Qemu-devel] [PATCH] Implement the function usb_hub_handle_reset hkran
2011-11-22 12:36 ` Gerd Hoffmann
2011-11-23  3:16   ` hkran [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-11-22  9:08 hkran
2011-11-22  8:52 hkran
2011-11-22  8:37 hkran

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=4ECC659D.6080000@linux.vnet.ibm.com \
    --to=hkran@linux.vnet.ibm.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@linux.vnet.ibm.com \
    /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).