Exclusive use of USB3 port

[ProNatur]

I use a HP DL380 Gen9 with Proxmox 4.1-1. I want to use an USB3 port exclusive for a VM. I now use the port with vendor ID and product ID. But this could lead to problems, when a USB device with the same vendor and product ID is put into another USB port.

With USB2 it isn't a problem to do this. I use

usb0: host=1-4

and all devices connected to bus 1 port 4 are passed throught to the VM. But it seems, that this doesn't work with USB3. So I had to use the -device version to connect the USB devices by vendor and product ID..

Is there a chance to use an USB3 port exclusively for one VM?

 

[dcsapak]

hi,

since version 4.0-55 of our qemu-server package (currently in the no-subscription repo),
you can add a ",usb3=yes" option to your config, and qemu will use usb3

it should look like this:

usb0: host=1-4,usb3=yes

it should work with bus-port syntax as well as vendorid: productid
i will update the wiki today

 

[ProNatur]

Thank you for your fast answer, but that didn't worked for me.

I used

usb0: host=2-2,usb3=yes

and get the following error in the syslogd

vm 100 - unable to parse value of 'usb0' - unable to parse usb device

I checked the bus/port with "info usbhost", which showed me bus 2 and port 2. But "info usb" showed me, that USB isn't connected correct.

If I use

usb0: host=2-2

I get

pve kernel: usb 2-2: reset SuperSpeed USB device number 4 using xhci_hcd
pve kernel: usb-storage 2-2:1.0: USB Mass Storage device detected

So I assume, that bus/port combination is correct, but "usb3=yes" isn't.

Any suggestions?

 

[dcsapak]

what is the output of

pveversion -v

on your host?

 

[ProNatur]

The output is

proxmox-ve: 4.1-26 (running kernel: 4.2.6-1-pve)
pve-manager: 4.1-1 (running version: 4.1-1/2f9650d4)
pve-kernel-4.2.6-1-pve: 4.2.6-26
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 0.17.2-1
pve-cluster: 4.0-29
qemu-server: 4.0-41
pve-firmware: 1.1-7
libpve-common-perl: 4.0-41
libpve-access-control: 4.0-10
libpve-storage-perl: 4.0-38
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.4-17
pve-container: 1.0-32
pve-firewall: 2.0-14
pve-ha-manager: 1.0-14
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.5-5
lxcfs: 0.13-pve1
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5-pve6~jessie

Could be the "qemu-server: 4.0-41" the problem? If yes, is there a possibility to update the qemu-server?

 

[dcsapak]

if you have set the pve-no-subscription repository (see: https://pve.proxmox.com/wiki/Package_repositories)
you can do an upgrade and then you should have an up to date system (with a current qemu-server package)

edit: before you update: which repository do you have enabled?

 

[ProNatur]

@dcsapak: Thank you for your help. Works like a charme.