USB Mouse/Keyboard Passthrough to Win7/Win10

hieve

New Member
May 29, 2017
15
1
3
31
Hello there,

I'm currently trying to passthrough a wireless usb keyboard + mouse set from microsoft.
This set works flawless in Ubuntu VM.
With Windows 7 and Windows 10 the devices seem to unplug themselves after some time.
I can for example try a windows installation and press the "any" key and go further to the setup on win7/10 , but after waiting for 5-10 seconds, the devices seem to unplug themselves and do not respond anymore.

I have tried both ways
-assigning the device to the VM
-assigning the port to the VM

both result in the same bad behaviour.
strange behaviour : if I connect via RDP onto the Windows machine and log out , the keyboard + mouse work for some while again

pveversion -v
Code:
proxmox-ve: 5.0-9 (running kernel: 4.10.11-1-pve)
pve-manager: 5.0-10 (running version: 5.0-10/0d270679)
pve-kernel-4.10.11-1-pve: 4.10.11-9
libpve-http-server-perl: 2.0-4
lvm2: 2.02.168-pve2
corosync: 2.4.2-pve2
libqb0: 1.0.1-1
pve-cluster: 5.0-7
qemu-server: 5.0-4
pve-firmware: 2.0-2
libpve-common-perl: 5.0-12
libpve-guest-common-perl: 2.0-1
libpve-access-control: 5.0-4
libpve-storage-perl: 5.0-3
pve-libspice-server1: 0.12.8-3
vncterm: 1.4-1
pve-docs: 5.0-1
pve-qemu-kvm: 2.9.0-1
pve-container: 2.0-6
pve-firewall: 3.0-1
pve-ha-manager: 2.0-1
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.0.8-1
lxcfs: 2.0.7-pve1
criu: 2.11.1-1~bpo90
novnc-pve: 0.5-9
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.6.5.9-pve16~bpo90


lsusb
Code:
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 003: ID 045e:07b2 Microsoft Corp.
Bus 004 Device 002: ID 04d9:0462 Holtek Semiconductor, Inc.
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

/etc/pve/qemu-server/310.conf
Code:
agent: 1
bootdisk: virtio0
cores: 4
cpu: host
hostpci0: 01:00.0;01:00.1,pcie=1,x-vga=on,romfile=gt1030.rom
ide0: hdd1:iso/virtio-win-0.1.126.iso,media=cdrom,size=152204K
ide2: hdd1:iso/Windows10-64bit.iso,media=cdrom,size=3341M
machine: q35
memory: 8192
name: win10-passthrough
net0: virtio=CA:51:4A:7E:8E:F5,bridge=vmbr0
numa: 0
ostype: win10
scsihw: virtio-scsi-pci
smbios1: uuid=caef9714-49be-4eef-be43-3196f40a5ce6
sockets: 1
usb0: host=4-3
virtio0: hdd1:310/vm-310-disk-1.qcow2,size=128G
or for device assignment
usb0: host=045e:07b2


I also got some wireless combo keyboard with integrated mouse here, which works flawless with similar settings and the same vms
 
Did you find a solution to your problem? I'm running into exactly the same issues with the Microsoft Sculpt set.
 
FYI, the following seems to work:

Device Manager -> Human Interface Devices -> Microsoft Hardware USB Keyboard -> Power Management -> Uncheck "Allow the computer to turn off this device to save power"

Same for the mouse. :)
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!