Passthrough of 3.5 usb hdd is not recognize in vm

D

duda

New Member
Mar 28, 2023
6
0
1
hello,

i add a 3.5 hdd to the usb3 port and passthough it to a vm (3-2), but woudnt be shown in the vm.

proxmox
1687104294564.png

vm
1687103993836.png
vm when remove virtual usb hardware
1687104574764.png

other hardware like usb stick or 2.5hdd works.
I tested two 3.5 adapters, both are only shown and accessable inside proxmox but not in the vm.

i want to use this hdd only for backups on the vm and will be normally disconnected.
 
Last edited:
how does the config look like (qm config ID) what's your 'pveversion -v' and can you post an excerpt of the journal (with e.g. journalctl) when you start the vm?
 
Hey @dcsapak, hope this helps :)

Code: 
root@proxmox:~# qm config 100
boot: order=ide2;net0
cores: 1
ide2: local:iso/MX-21.3_x64.iso,media=cdrom,size=1867M
machine: pc-i440fx-7.1
memory: 2048
meta: creation-qemu=7.2.0,ctime=1686580506
name: boot-test
net0: virtio=3E:55:2C:0D:25:2C,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
scsihw: virtio-scsi-single
smbios1: uuid=41848791-e63f-4d97-b66b-bcd5db77ad2d
sockets: 2
usb0: host=3-2
vmgenid: 15774837-ea48-4221-8f4e-e8ca0434145f
root@proxmox:~#


Code: 
root@proxmox:~# pveversion -v
proxmox-ve: 7.4-1 (running kernel: 5.15.107-2-pve)
pve-manager: 7.4-13 (running version: 7.4-13/46c37d9c)
pve-kernel-5.15: 7.4-3
pve-kernel-5.15.107-2-pve: 5.15.107-2
pve-kernel-5.15.102-1-pve: 5.15.102-1
ceph-fuse: 15.2.17-pve1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx4
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.4
libproxmox-backup-qemu0: 1.3.1-1
libproxmox-rs-perl: 0.2.1
libpve-access-control: 7.4.1
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.4-1
libpve-guest-common-perl: 4.2-4
libpve-http-server-perl: 4.2-3
libpve-rs-perl: 0.7.7
libpve-storage-perl: 7.4-3
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.2-2
lxcfs: 5.0.3-pve1
novnc-pve: 1.4.0-1
proxmox-backup-client: 2.4.2-1
proxmox-backup-file-restore: 2.4.2-1
proxmox-kernel-helper: 7.4-1
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.7.2
pve-cluster: 7.3-3
pve-container: 4.4-4
pve-docs: 7.4-2
pve-edk2-firmware: 3.20230228-4~bpo11+1
pve-firewall: 4.3-4
pve-firmware: 3.6-5
pve-ha-manager: 3.6.1
pve-i18n: 2.12-1
pve-qemu-kvm: 7.2.0-8
pve-xtermjs: 4.16.0-2
qemu-server: 7.4-3
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+3
vncterm: 1.7-1
zfsutils-linux: 2.1.11-pve1


Code: 
journalctl -n 100
Jun 20 21:26:53 proxmox systemd[1]: Started 100.scope.
Jun 20 21:26:53 proxmox systemd-udevd[60259]: Using default interface naming scheme 'v247'.
Jun 20 21:26:53 proxmox systemd-udevd[60259]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jun 20 21:26:54 proxmox kernel: device tap100i0 entered promiscuous mode
Jun 20 21:26:54 proxmox systemd-udevd[60258]: Using default interface naming scheme 'v247'.
Jun 20 21:26:54 proxmox systemd-udevd[60258]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jun 20 21:26:54 proxmox systemd-udevd[60258]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jun 20 21:26:54 proxmox systemd-udevd[60259]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jun 20 21:26:54 proxmox kernel: vmbr0: port 2(fwpr100p0) entered blocking state
Jun 20 21:26:54 proxmox kernel: vmbr0: port 2(fwpr100p0) entered disabled state
Jun 20 21:26:54 proxmox kernel: device fwpr100p0 entered promiscuous mode
Jun 20 21:26:54 proxmox kernel: vmbr0: port 2(fwpr100p0) entered blocking state
Jun 20 21:26:54 proxmox kernel: vmbr0: port 2(fwpr100p0) entered forwarding state
Jun 20 21:26:54 proxmox kernel: fwbr100i0: port 1(fwln100i0) entered blocking state
Jun 20 21:26:54 proxmox kernel: fwbr100i0: port 1(fwln100i0) entered disabled state
Jun 20 21:26:54 proxmox kernel: device fwln100i0 entered promiscuous mode
Jun 20 21:26:54 proxmox kernel: fwbr100i0: port 1(fwln100i0) entered blocking state
Jun 20 21:26:54 proxmox kernel: fwbr100i0: port 1(fwln100i0) entered forwarding state
Jun 20 21:26:54 proxmox kernel: fwbr100i0: port 2(tap100i0) entered blocking state
Jun 20 21:26:54 proxmox kernel: fwbr100i0: port 2(tap100i0) entered disabled state
Jun 20 21:26:54 proxmox kernel: fwbr100i0: port 2(tap100i0) entered blocking state
Jun 20 21:26:54 proxmox kernel: fwbr100i0: port 2(tap100i0) entered forwarding state
Jun 20 21:26:54 proxmox kernel: sd 2:0:0:0: [sdc] Synchronizing SCSI cache
Jun 20 21:26:55 proxmox kernel: sd 2:0:0:0: [sdc] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Jun 20 21:26:55 proxmox QEMU[60254]: kvm: Unable to connect character device qmp-event: Failed to connect to '/var/run/qmeventd.sock': Connection refused
Jun 20 21:26:55 proxmox pvedaemon[1207]: <root@pam> end task UPID:proxmox:0000EB49:01170964:6491FD7D:qmstart:100:root@pam: OK
Jun 20 21:26:55 proxmox pvedaemon[60310]: starting vnc proxy UPID:proxmox:0000EB96:01170A4E:6491FD7F:vncproxy:100:root@pam:
Jun 20 21:26:55 proxmox pvedaemon[1205]: <root@pam> starting task UPID:proxmox:0000EB96:01170A4E:6491FD7F:vncproxy:100:root@pam:
Jun 20 21:26:55 proxmox pveproxy[46174]: proxy detected vanished client connection
Jun 20 21:26:55 proxmox pvedaemon[1207]: <root@pam> starting task UPID:proxmox:0000EB98:01170A64:6491FD7F:vncproxy:100:root@pam:
Jun 20 21:26:55 proxmox pvedaemon[60312]: starting vnc proxy UPID:proxmox:0000EB98:01170A64:6491FD7F:vncproxy:100:root@pam:
Jun 20 21:27:05 proxmox pvedaemon[60310]: connection timed out
Jun 20 21:27:05 proxmox pvedaemon[1205]: <root@pam> end task UPID:proxmox:0000EB96:01170A4E:6491FD7F:vncproxy:100:root@pam: connection timed out
Jun 20 21:28:02 proxmox postfix/qmgr[1117]: 3BE23240E1C: from=<root@proxmox.fritz.box>, size=1054, nrcpt=1 (queue active)
Jun 20 21:28:02 proxmox postfix/qmgr[1117]: 301FC240BF9: from=<root@proxmox.fritz.box>, size=1057, nrcpt=1 (queue active)
Jun 20 21:28:02 proxmox postfix/local[60483]: error: open database /etc/aliases.db: No such file or directory
Jun 20 21:28:02 proxmox postfix/local[60483]: warning: hash:/etc/aliases is unavailable. open database /etc/aliases.db: No such file or directory
Jun 20 21:28:02 proxmox postfix/local[60483]: warning: hash:/etc/aliases: lookup of 'root' failed
Jun 20 21:28:02 proxmox postfix/local[60484]: error: open database /etc/aliases.db: No such file or directory
Jun 20 21:28:02 proxmox postfix/local[60484]: warning: hash:/etc/aliases is unavailable. open database /etc/aliases.db: No such file or directory
Jun 20 21:28:02 proxmox postfix/local[60484]: warning: hash:/etc/aliases: lookup of 'root' failed
Jun 20 21:28:02 proxmox postfix/local[60483]: 3BE23240E1C: to=<root@proxmox.fritz.box>, orig_to=<root>, relay=local, delay=1132, delays=1132/0.02/0/0.02, dsn=4.3.0, status=deferred>
Jun 20 21:28:02 proxmox postfix/local[60484]: 301FC240BF9: to=<root@proxmox.fritz.box>, orig_to=<root>, relay=local, delay=1132, delays=1132/0.02/0/0.01, dsn=4.3.0, status=deferred>
Jun 20 21:28:14 proxmox kernel: usb 3-2: reset SuperSpeed USB device number 3 using xhci_hcd
Jun 20 21:28:15 proxmox QEMU[60254]: kvm: libusb_alloc_streams: got less streams then requested 31 < 32
Jun 20 21:28:15 proxmox kernel: xhci_hcd 0000:00:10.0: WARN: endpoint 0x82 has streams on set_interface, freeing streams.
Jun 20 21:28:15 proxmox kernel: xhci_hcd 0000:00:10.0: WARN: endpoint 0x83 has streams on set_interface, freeing streams.
Jun 20 21:28:15 proxmox kernel: xhci_hcd 0000:00:10.0: WARN: endpoint 0x04 has streams on set_interface, freeing streams.
 
Last edited:
maybe, in general looks all normal except

duda said:
Jun 20 21:28:15 proxmox QEMU[60254]: kvm: libusb_alloc_streams: got less streams then requested 31 < 32
Jun 20 21:28:15 proxmox kernel: xhci_hcd 0000:00:10.0: WARN: endpoint 0x82 has streams on set_interface, freeing streams.
Click to expand...
though i cannot really say if these are just warnings or indicative of a problem
 
You must log in or register to reply here.
Top Bottom