public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Veruca Salt <verucasaltuk@hotmail.co.uk>,
	qemu-devel <qemu-devel@nongnu.org>,
	QEMU-KVM Mailing List <kvm@vger.kernel.org>
Subject: qemu & xhci mini howto (was: Re: [Qemu-devel] [ANNOUNCE] qemu-kvm-1.1-rc3)
Date: Tue, 29 May 2012 10:32:07 +0200	[thread overview]
Message-ID: <4FC48987.2060103@redhat.com> (raw)
In-Reply-To: <4FC345D2.3090309@redhat.com>

On 05/28/12 11:30, Avi Kivity wrote:
> On 05/25/2012 11:36 AM, Veruca Salt wrote:
>>
>> Avi- would love to test out 1.1, as we are currently using the ehci method
>>  which has been frozen at 'experimental' for so long.
>>
>> Is there any user documentation on the xhci methods?
> 
> Copying qemu-devel, where someone may know the answer.

There are no docs.  But xhci can handle all devices by itself, no need
to do all this companion controller stuff you have to do with ehci for
usb 1.1 compatibility.  Thus it's pretty simple actually:


(1) You add the xhci host adapter:

    qemu $args -device nec-usb-xhci,id=xhci

(2) You add usb devices devices as usual:

    qemu $args -device usb-tablet,bus=xhci.0

(3) There is no third step ;)


Advantages of xhci:
 * higher performance, less cpu overhead (thanks to the
   virtualization/emulation friendly hardware design).

Known issues (for qemu 1.1, list hopefully becomes shorter for 1.2):
 * Got less testing than ehci.
 * No usb-hub support yet (i.e. you are limited to the 4 root ports,
   but as the qemu-emulated usb hub supports usb 1.1 only you probably
   want avoid it anyway ...).
 * No usb 3.0 ports yet.
 * No isochronous transfer support yet.
 * No seabios support yet (i.e. you can't boot from xhci-connected
   usbsticks).

cheers,
  Gerd

      reply	other threads:[~2012-05-29  8:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-23  9:07 [ANNOUNCE] qemu-kvm-1.1-rc3 Avi Kivity
2012-05-25  8:36 ` Veruca Salt
2012-05-28  9:30   ` Avi Kivity
2012-05-29  8:32     ` Gerd Hoffmann [this message]

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=4FC48987.2060103@redhat.com \
    --to=kraxel@redhat.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=verucasaltuk@hotmail.co.uk \
    /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