From mboxrd@z Thu Jan 1 00:00:00 1970 From: Erik Rull Subject: Re: USB EHCI patch for 0.14.0? Date: Fri, 11 Mar 2011 17:32:39 +0100 Message-ID: <4D7A4EA7.5050108@rdsoftware.de> References: <0NZZCL-1Py46m2UCX-0000eH@icpu525.kundenserver.de> <4D7A4666.2020007@cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: David Ahern Return-path: Received: from moutng.kundenserver.de ([212.227.17.10]:50585 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752381Ab1CKQcc (ORCPT ); Fri, 11 Mar 2011 11:32:32 -0500 In-Reply-To: <4D7A4666.2020007@cisco.com> Sender: kvm-owner@vger.kernel.org List-ID: David Ahern wrote: > On 03/11/11 08:18, erik.rull@rdsoftware.de wrote: >> >> I tested again with your hints, here my results: >> >> - using -device usb-host causes windows not to boot completely, using >> -usbdevice host:auto:*.* is fine! >> >> - using -usbdevice tablet is better than using -device usb-tablet >> >> >> - only one "external" USB device gets detected, the rest is just ignored. >> qemu does not recognize the device, but the host OS sees it (dmesg output) > > I have not used the auto feature. What happens if you disable it and > instead add the devices you want? I have been able to add both a printer > and a USB key to a guest -- both on the EHCI bus. And just verified > again - both printer and USB key accessible within the guest. I will test that on monday and will let you know about the results. >> - if the first plugged in device is removed from the usb port and the >> second (not detected one) is still plugged in, then this second device gets >> now detected by qemu and is handled to the guest > > Interesting. Gerd made a lot of changes to the USB code right before > 0.14. I have not really followed the change set - or how it might impact > ehci. It could be a bug independent of ehci as well -- try it without > the ehci patch and see if the same occurs. Very good point :-) I've never tested that because I knew that the USB printer will then crash my guest :-) But I will follow that idea on monday as well. >> Additionally something really interesting: >> if I disable USB 2.0 in my host BIOS and boot my guest system with the qemu >> ehci patch, then I get no longer the BSOD in windows when removing the >> printer! :-) So the patch seems also to improve the usb-uhci stuff. > > Our mileage differs here as well. I'm running Fedora 14 on my laptop. > With the ehci enabled version of qemu-kvm I have no problems connecting > and disconnecting devices -- host or guest. Except the not fully functioning auto add feature we're on the same level, because I've not tested the manual adding (and I assume / hope that it will be successful). > > David > Best regards, Erik