Proxmox 8 conflict with identic USB devices

O

onlineapps

Well-Known Member
Jan 21, 2020
76
7
48
hi, i had problem, i have 2 identical usb nvme devices connected to 2 different VM.
when i run first VM all ok, when i run second VM, i had error with drive on first VM
first VM:
1693397121897.png
second VM:
1693397157448.png
device id is same:
1693397180115.png
i think that proxmox watch device ID, to use in VM not as port, but i selected to use device as port, not as device id!
pveversion:

root@proxmox2:~# pveversion --verbose
proxmox-ve: 8.0.2 (running kernel: 6.2.16-10-pve)
pve-manager: 8.0.4 (running version: 8.0.4/d258a813cfa6b390)
proxmox-kernel-helper: 8.0.3
pve-kernel-5.15: 7.4-5
proxmox-kernel-6.2.16-10-pve: 6.2.16-10
proxmox-kernel-6.2: 6.2.16-10
pve-kernel-5.15.111-1-pve: 5.15.111-1
pve-kernel-5.15.108-1-pve: 5.15.108-2
ceph-fuse: 16.2.11+ds-2
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-4
libknet1: 1.25-pve1
libproxmox-acme-perl: 1.4.6
libproxmox-backup-qemu0: 1.4.0
libproxmox-rs-perl: 0.3.1
libpve-access-control: 8.0.4
libpve-apiclient-perl: 3.3.1
libpve-common-perl: 8.0.7
libpve-guest-common-perl: 5.0.4
libpve-http-server-perl: 5.0.4
libpve-rs-perl: 0.8.5
libpve-storage-perl: 8.0.2
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve3
novnc-pve: 1.4.0-2
proxmox-backup-client: 3.0.2-1
proxmox-backup-file-restore: 3.0.2-1
proxmox-kernel-helper: 8.0.3
proxmox-mail-forward: 0.2.0
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.2
proxmox-widget-toolkit: 4.0.6
pve-cluster: 8.0.3
pve-container: 5.0.4
pve-docs: 8.0.4
pve-edk2-firmware: 3.20230228-4
pve-firewall: 5.0.3
pve-firmware: 3.7-1
pve-ha-manager: 4.0.2
pve-i18n: 3.0.5
pve-qemu-kvm: 8.0.2-4
pve-xtermjs: 4.16.0-3
qemu-server: 8.0.6
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.1.12-pve1
 
Last edited:
Hi! I have the same problem with 2 hdd bay with the same chip (different brands).
Can you fix the problem?
 
I just had a similar problem with a Zigbee and ZWave device that had the same device ID. As a temp, or maybe permanent fix, I had to throw them in separate virtual machines. Luckily the ZWave device just flows through an MQTT server, so no biggie!

It appears you might be in luck, as that's what you're trying to do. I was able to pass through the different USB ports to the separate virtual machines. Assign 2-2 to one, and 2-3 to the other.

The only other way I've been able to get them to play nice together on the same VM has been on separate USB buses. <- lol that felt like saying RIP in peace.

Unfortunately, for me, I only had one bus available. Anyways, I hope that helps you resolve your issues.
 
My problem is with two separated vm. Maybe can work for weeks or minutes.
I remember that proxmox 7 hasn’t this problem, but not sure cause I change the hardware and migrate all's vm and containers using 8 version.
Now I’m trying with other hdd enclosure with different chip inside and works fine.
I played with usb bus but can’t find combinations that works.
 
santigtt said:
My problem is with two separated vm. Maybe can work for weeks or minutes.
I remember that proxmox 7 hasn’t this problem, but not sure cause I change the hardware and migrate all's vm and containers using 8 version.
Now I’m trying with other hdd enclosure with different chip inside and works fine.
I played with usb bus but can’t find combinations that works.
Click to expand...
Sorry, mate. Wish I could help more in that department. The HDD enclosures always seem to be a bit of a gamble.
 
Outpost1534 said:
It appears you might be in luck, as that's what you're trying to do. I was able to pass through the different USB ports to the separate virtual machines. Assign 2-2 to one, and 2-3 to the other.
Click to expand...
hi, this not working for me, i tried. i have 2 hdd with same chip and same device id (nvme drive have different serial numbers).
 
You must log in or register to reply here.
Top Bottom