libvirt users - Nov 2016 - ergodox keyboard not working on USB hostdev passthrough

I'm using a bit of a different keyboard, the infinity ergodox [
https://input.club/devices/infinity-ergodox/]. It functions just fine as a
keyboard on my host computer, but when I try to bind it to the guest,
nothing seems to happen.

lsusb gives its ID:
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
*Bus 005 Device 003: ID 1c11:b04d*
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 258a:0001
Bus 001 Device 002: ID 093a:2521 Pixart Imaging, Inc. Optical Mouse
Bus 001 Device 004: ID 8087:0a2b Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

So, I made a file, hostdev-1c11:b04d.xml, which contains the following:
<hostdev mode='subsystem' type='usb' >
  <source>
    <vendor id='0x1c11'/>
    <product id='0xb04d'/>
  </source>
</hostdev>

Note, I have had this same xml inside the domain's xml, but have pulled it
out separately so that I could run:

virsh attach-device linux-x86_64 hostdev-1c11:b04d.xml

It appears to attach the device, as it becomes visible in the domain's
lsusb:
Bus 001 Device 001: ID 1d6b:0002
Bus 004 Device 001: ID 1d6b:0001
*Bus 003 Device 003: ID 1c11:b04d  *
Bus 003 Device 001: ID 1d6b:0001
Bus 002 Device 003: ID 093a:2521
Bus 002 Device 002: ID 258a:0001
Bus 002 Device 001: ID 1d6b:0001

The mouse works just fine. I bought a cheap keyboard to test out, and it
works just fine. My pet keyboard, however, doesn't work on the guest.
Nothing seems to register. Any ideas here what I could do? Drivers? ROM's?
I've tried both SeaBIOS and OVMF with no difference in outcome, and while
this appears to be a hardware problem, I don't know where to begin.

Thanks,

Paul

On Tue, Nov 15, 2016 at 01:22:32PM -0700, Paul Handy
wrote:
>I'm using a bit of a different keyboard, the infinity ergodox [
>https://input.club/devices/infinity-ergodox/]. It functions just fine as a
>keyboard on my host computer, but when I try to bind it to the guest,
>nothing seems to happen.
>
>lsusb gives its ID:
>Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>*Bus 005 Device 003: ID 1c11:b04d*
>Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>Bus 001 Device 003: ID 258a:0001
>Bus 001 Device 002: ID 093a:2521 Pixart Imaging, Inc. Optical Mouse
>Bus 001 Device 004: ID 8087:0a2b Intel Corp.
>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>
>So, I made a file, hostdev-1c11:b04d.xml, which contains the following:
><hostdev mode='subsystem' type='usb' >
>  <source>
>    <vendor id='0x1c11'/>
>    <product id='0xb04d'/>
>  </source>
></hostdev>
>
>Note, I have had this same xml inside the domain's xml, but have pulled
it
>out separately so that I could run:
>
>virsh attach-device linux-x86_64 hostdev-1c11:b04d.xml
>
>It appears to attach the device, as it becomes visible in the domain's
>lsusb:
>Bus 001 Device 001: ID 1d6b:0002
>Bus 004 Device 001: ID 1d6b:0001
>*Bus 003 Device 003: ID 1c11:b04d  *
>Bus 003 Device 001: ID 1d6b:0001
>Bus 002 Device 003: ID 093a:2521
>Bus 002 Device 002: ID 258a:0001
>Bus 002 Device 001: ID 1d6b:0001
>
Since the guest can see it ^^ I don't think this is a problem in the
host system.  Does it require special module/driver?  Is it supported by
the guest OS?

When it is not passed-through to your guest, run lsusb -t on the host
and see what's the Driver= for the device.  The try the same thing in
the guest and if it's missing you got it.  If not, then you can check
settings for X etc.
>The mouse works just fine. I bought a cheap keyboard to test out, and it
>works just fine. My pet keyboard, however, doesn't work on the guest.
>Nothing seems to register. Any ideas here what I could do? Drivers?
ROM's?
>I've tried both SeaBIOS and OVMF with no difference in outcome, and
while
>this appears to be a hardware problem, I don't know where to begin.
>
>Thanks,
>
>Paul
>_______________________________________________
>libvirt-users mailing list
>libvirt-users@redhat.com
>https://www.redhat.com/mailman/listinfo/libvirt-users