From: David Ahern <daahern@cisco.com>
To: Erik Rull <erik.rull@rdsoftware.de>
Cc: Markus Armbruster <armbru@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: USB EHCI patch for 0.14.0?
Date: Fri, 11 Mar 2011 10:11:20 -0700 [thread overview]
Message-ID: <4D7A57B8.3010706@cisco.com> (raw)
In-Reply-To: <4D7A5423.7020305@rdsoftware.de>
On 03/11/11 09:56, Erik Rull wrote:
> Markus Armbruster wrote:
>> Erik Rull<erik.rull@rdsoftware.de> writes:
>>
>>> Markus Armbruster wrote:
>>>> erik.rull@rdsoftware.de writes:
>>>>
>>>>> - 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
>>>>
>>>> Better inhowfar?
>>>>
>>>> [...]
>>>
>>> It seems to work fine, the other option caused either windows not to
>>> boot fully or the auto grabbing itself doesn't seem to work or the
>>> mouse just didn't move. I experienced all of the three, but I haven't
>>> noted down in which combinations - sorry.
>>
>> Please provide recipes to reproduce the bugs.
>
> - take Windows XP 32 bit SP3 as Guest
> - apply the ehci patch to qemu-kvm-0.14.0 (David posted it here some
> days ago)
processing of usb device options is independent of the EHCI patch.
David
> boot the guest using the command line args:
> -usb -device usb-host
> (I also tried the proposal where the additonal usb-host options are all
> set to 0, same result)
> Windows starts but hangs before the GUI comes up (I boot without logo,
> so the white bar that comes up when booting stays for > 20 minutes (I
> aborted afterwards)), the CPU usage on a Core2Duo system goes to ~10-14%.
>
> If I use instead
> -usb -usbdevice host:auto:*.*
> everything is fine!
>
> Best regards,
>
> Erik
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2011-03-11 17:10 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-11 15:18 USB EHCI patch for 0.14.0? erik.rull
2011-03-11 15:39 ` Markus Armbruster
2011-03-11 16:01 ` David Ahern
2011-03-11 16:17 ` Markus Armbruster
2011-03-11 16:34 ` David Ahern
2011-03-11 16:24 ` Erik Rull
2011-03-11 16:46 ` Markus Armbruster
2011-03-11 16:56 ` Erik Rull
2011-03-11 17:11 ` David Ahern [this message]
2011-03-11 17:31 ` David Ahern
2011-04-11 9:40 ` ya su
2011-04-11 13:23 ` David Ahern
2011-04-11 16:32 ` Jan Kiszka
2011-04-11 16:46 ` Jan Kiszka
2011-04-11 17:53 ` David Ahern
2011-04-11 20:07 ` Jan Kiszka
2011-04-11 21:10 ` Alexander Graf
2011-03-11 15:57 ` David Ahern
2011-03-11 16:32 ` Erik Rull
-- strict thread matches above, loose matches on Subject: below --
2011-03-14 8:38 erik.rull
2011-03-17 18:05 ` Erik Rull
2011-03-09 15:40 erik.rull
2011-03-09 16:12 ` David Ahern
2011-03-09 21:28 ` Erik Rull
2011-03-09 22:14 ` David Ahern
2011-03-09 22:48 ` Erik Rull
2011-03-08 16:23 Erik Rull
2011-03-08 18:54 ` David Ahern
2011-06-06 11:33 ` André Weidemann
2011-06-06 13:18 ` David Ahern
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=4D7A57B8.3010706@cisco.com \
--to=daahern@cisco.com \
--cc=armbru@redhat.com \
--cc=erik.rull@rdsoftware.de \
--cc=kvm@vger.kernel.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