All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Thomas Huth <thuth@redhat.com>,
	Daryl Oliver <gen.dr.aireagoirdragesteam@gmail.com>,
	qemu-devel@nongnu.org
Cc: "Gerd Hoffmann" <kraxel@redhat.com>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Daniel P. Berrangé" <berrange@redhat.com>
Subject: Re: [Qemu-devel] qemu bluetooth support
Date: Fri, 8 Mar 2019 09:56:25 +0100	[thread overview]
Message-ID: <5109bd99-ab78-ef32-b900-15896dc00d1f@redhat.com> (raw)
In-Reply-To: <d856dc98-018b-3eec-fe05-26035a64e9bb@redhat.com>

On 05/03/19 09:05, Thomas Huth wrote:
> On 02/03/2019 13.46, Daryl Oliver wrote:
>> Hello there I don't know if this is till valid but I thought I should
>> mention my use cases for the bluetooth option in qemu.
>>
>> Use case would be using Bluetooth controllers for gaming on kvm qemu since
>> I don't know if kvm would be able to use my hosts Bluetooth chip or emulate
>> one. since I manily use the windows port of qemu.
>> But my other use case would be using Bluetooth speakers or headphones.
> 
>  Hi!
> 
> Thanks for your report! Do you mean you are already using bluetooth for
> your KVM guest, or you just would like to use it (since you wrote "would
> be" and not "is")?
> In the first case, could you please elaborate on your set up? Which
> hardware are you exactly passing through to the guest, which parameters
> are you using for starting QEMU, which version of QEMU are you using, is
> it working without problems, etc. ?

I suspect he wants to pass something like an XBox controller.  It would
actually be a very good usecase for Bluetooth passthrough.

If he is using Linux guests, he could use virtio-input-host-pci.

For Windows, we could also pass it through as an HID device, using
something like virtio-input-host-pci but for USB.  It wouldn't be hard
to implement, but you'd have to write a converter from Linux evdev
descriptors to USB HID descriptors.

Paolo

> I ask because currently, I don't know anybody who is still using
> bluetooth passthrough with a recent version of QEMU, so it would be very
> interesting to know whether this still works at all or not...
> 
>  Thanks,
>   Thomas
> 

  reply	other threads:[~2019-03-08  8:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-02 12:46 [Qemu-devel] qemu bluetooth support Daryl Oliver
2019-03-05  8:05 ` Thomas Huth
2019-03-08  8:56   ` Paolo Bonzini [this message]
2019-03-08  9:19     ` Gerd Hoffmann
2019-03-08 10:14       ` Paolo Bonzini
2019-03-11 13:02     ` Thomas Huth

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=5109bd99-ab78-ef32-b900-15896dc00d1f@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=berrange@redhat.com \
    --cc=gen.dr.aireagoirdragesteam@gmail.com \
    --cc=kraxel@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.