Hello Forum....I was wondering if anyone else is using this keyboard and what their experience has been passing through to a Win10 VM?!!! 

 

 

 

For me, the keyboard is great when working; however, the keyboard will loose connection to my VM after some time or if I reboot which requires me to unplug the keyboard, plug back in, and then update the VM.  Here is the log post when booting VM but keyboard not working.

 

2017-01-08 12:51:28.380+0000: starting up libvirt version: 1.3.1, qemu version: 2.5.1, hostname: Tower
LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name UNRAID-VM-4000 -S -machine pc-q35-2.5,accel=kvm,usb=off,mem-merge=off -cpu host -drive file=/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd,if=pflash,format=raw,unit=0,readonly=on -drive file=/etc/libvirt/qemu/nvram/0d6adf74-7cab-8884-a1a0-79f434cbc166_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 6656 -realtime mlock=on -smp 4,sockets=1,cores=2,threads=2 -uuid 0d6adf74-7cab-8884-a1a0-79f434cbc166 -nographic -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-UNRAID-VM-4000/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on -device i82801b11-bridge,id=pci.1,bus=pcie.0,addr=0x1e -device pci-bridge,chassis_nr=2,id=pci.2,bus=pci.1,addr=0x1 -device ich9-usb-ehci1,id=usb,bus=pcie.0,addr=0x7.0x7 -device ich9ci.2,addr=0x1 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-UNRAID-VM-4000/org.qemu.guest_agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device vfio-pci,host=02:00.0,id=hostdev0,bus=pci.2,addr=0x4 -device usb-host,hostbus=1,hostaddr=30,id=hostdev1 -device usb-host,hostbus=1,hostaddr=20,id=hostdev2 -device usb-host,hostbus=1,hostaddr=26,id=hostdev3 -device usb-host,hostbus=1,hostaddr=39,id=hostdev4 -device virtio-balloon-pci,id=balloon0,bus=pci.2,addr=0x5 -msg timestamp=on
Domain id=32 is tainted: high-privileges
Domain id=32 is tainted: host-cpu
char device redirected to /dev/pts/0 (label charserial0)
2017-01-08T12:51:57.836379Z qemu-system-x86_64: libusb_release_interface: -4 [NO_DEVICE]
2017-01-08T12:51:57.836417Z qemu-system-x86_64: libusb_release_interface: -4 [NO_DEVICE]
2017-01-08T12:51:57.836422Z qemu-system-x86_64: libusb_release_interface: -4 [NO_DEVICE]
libusb: error [_open_sysfs_attr] open /sys/bus/usb/devices/1-5/bConfigurationValue failed ret=-1 errno=2
libusb: error [do_close] Device handle closed while transfer was still being processed, but the device is still connected as far as we know
libusb: warning [do_close] A cancellation for an in-flight transfer hasn't completed but closing the device handle
libusb: error [_get_usbfs_fd] File doesn't exist, wait 10 ms and try again
libusb: error [_get_usbfs_fd] libusb couldn't open USB device /dev/bus/usb/001/039: No such file or directory

 

VM XML Attached

XML.txt

Apologies for reviving a dead thread but here's what I found (and it solved my issue). I encountered this same issue (same keyboard, also on a Win10 VM I use for gaming) recently as I was working on some scripts to auto-attach devices back to particular VMs (as I have a mouse + keyboard on a hub which I plug/unplug for use with a laptop). I started looking around and found this on the Corsair support page (https://www.corsair.com/us/en/Categories/Products/Keyboards/StandardGamingKeyboards/STRAFE-Mechanical-Gaming-Keyboard-—-CHERRY®-MX-Red/p/CH-9000088-NA):

There are two USB plugs for my keyboard. Which one should I connect?

For USB 3.0:
Use one connector (the one with the keyboard icon) when connecting via USB 3.0

Connecting via USB 2.0
Use both connectors when using USB 2.0. Plug in the connector with the two arrows icon first, and the connector with the keyboard icon second.

 

I was using a USB3 hub and had plugged both cables into it. Once I disconnected the arrow one, the keyboard finally became usable.

Edited April 1, 20188 yr by MatthewDoerksen