qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH] EHCI support - device recognized, but no data


From: Jan Kiszka
Subject: Re: [Qemu-devel] [PATCH] EHCI support - device recognized, but no data
Date: Wed, 10 Mar 2010 08:38:56 +0100
User-agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666

David S. Ahern wrote:
> On 03/07/2010 04:32 AM, Jan Kiszka wrote:
>> Kevin Wolf wrote:
>>> Am Freitag, 5. März 2010 04:17 schrieb David S. Ahern:
>>>> Jan:
>>>>
>>>> I spent some more time on the EHCI support today. With the attached
>>>> patch (delta to the patch from yesterday) a USB key is recognized within
>>>> the guest (FC-12):
>>> Looks very nice. Actually I could access the file system on my USB stick. I 
>>> have pushed your patch along with some additional minor changes to 
>>> git://repo.or.cz/qemu/kevin.git ehci. Jan, you might want to pull from 
>>> there.
>>>
>> Merged, thanks.
>>
>> Meanwhile I played with some more devices, and I think I found one
>> scenario that should be handy to debug: -usbdevice net. Apparently, it
>> does not work yet, my console is just flooded with
>>
>>>>>>> ASYNC STATE MACHINE execute
>> 000.005 exec: ctr is 1
>> 000.004 exec: frindex is 488,3
>> 000.004 setting qh.current from 0E0B21E0 to 0x0E0B21E0
>> 000.005 Active non-interrupt QH, executing
>> 000.003 pid is  1
>> 000.00000.222 periodic state adv fr=490.  [0E0B37A8] -> 00000001
>> 000.009 periodic state adv fr=490.  [0E0B37A8] -> 00000001
>> 000.009
>>
>>>>>>> ASYNC STATE MACHINE execute
>> 000.006 exec: ctr is 1
>> 000.003 exec: frindex is 490,2
>> 000.005 setting qh.current from 0E0B21E0 to 0x0E0B21E0
>> 000.004 Active non-interrupt QH, executing
>> 000.004 pid is  1
>> 000.004 calling dev->info->handle_packet
>> 000.004 exit loop dev->info->handle_packet
>> 000.003 Enter EXECUTING
>> 000.004 USBTRAN RSP NAK, returning without clear active
>> 000.004 finishing exec
>> 000.004 Nak occured and RL != 0, dec NakCnt to -1
>> 000.004 write QH to VM memory
>> 000.203 periodic state adv fr=490.  [0E0B37A8] -> 00000001
>> 000.008 periodic state adv fr=490.  [0E0B37A8] -> 00000001
>> 000.009
>>
>> Messages. The guest reports that it received one Ethernet packet, but
>> that's all, dhcpcd fails with a timeout. Already "ifconfig ethX up"
>> starts this flooding.
>>
>> Jan
>>
> 
> What guest OS were you successful with for storage devices - windows or
> linux, 32-bit or 64? I've been mainly using FC-12, x86_64 as the guest
> OS, and an external (ie., physical) key of recent vintage. Qemu's msd
> device does not work with FC-12 (and UHCI).

I was using an OpenSuse 11.1 guest image with 2.6.27 kernel. Host and
guest were 64 bit.

> 
> I played around with Qemu's usb-net device a bit, but not sure I am
> configuring it correctly (using monitor commands to attach).

"-usbdevice net -net user" should switch completely to USB based
networking and make the guest issue dchp request over that NIC. Works
like that for me with UHCI, fails with EHCI.

Jan

Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]