[Bug]: Multiple NVME virtual devices shown with same device ORCL_VBOX_NMVE_VER12 can't be controlled by device software

[dblack34]

Version

7.2.16

Host OS Type

Linux

Host OS name + version

Ubuntu 24.04

Host Architecture

x86

Guest OS Type

Linux

Guest Architecture

x86

Guest OS name + version

Ubuntu 24.04

Component

Storage and Virtual Disks

What happened?

I have two softwares that check and controll connected disks (one is sun systems app, second one bulgarian dev) Before trying to test their work on real NVME adapter i tried to check them on virutalization.
So i created a few virtual nvme disks, some to add into LVM some just standing solo. Then i checked this disks in those programs. All virutal disks share same VID, PID, Vendor product which is bad for LVM. In one software all disks were added to the control when i pressed add on one. I contacted DEVS they said it is virtualbox's feature of virtualization, we cant do anything about. Almost same thing happened when i tried to apply ACL rules for user via second program/app. It is good when rules applied on virtual nvme disks in LVM group but it is not good when not-in-group disk is also shares same rules.
Is is somehow possible to give every virtual nvme disk new VID/PID's so they can differs? Right now it is just same ORCL_VBOX_NVME_VER12 VB1234_56789 devices.

How can we reproduce this?

1. Go to the Virtual machine settings to the disks/storages.
2. Add 3-4 disk via NVME adapter (first add adapter if you doesnt have it)
3. Start guest OS.
4. Make some LVM group of two of 4 disks. Lvm group should have 1 mounpoint (fstab her is prefered)
5. Other two disks leave as it is. Just give them ext4 and some mountpoints in /mnt/
6. Install software that allows to control devices, (i cant share my programms but believe that a lot of them will do the same because i've got same reaction of two different soft vendors). Try to controll devices.

if you dont have such software just check into UDEV/UDEVADM
udevadm info /dev/block/
udevadm info /dev/block/259:0 (as example)

Even if VBOX self gives additional parameters for disks like
nvme-ORCL-VBOX-NVME-VER12_VB1234-56789_1
nvme-ORCL-VBOX-NVME-VER12_VB1234-56789_2
nvme-ORCL-VBOX-NVME-VER12_VB1234-56789_3
nvme-ORCL-VBOX-NVME-VER12_VB1234-56789_4
This is temporary. Because as they share everything same any changing id disk load sequence will make a situation when rules applied to one disk applied to another. (disk 1 becames disk 2 and for example some user who have forbidden rule to access disk will grant it)
Most of the such programs operates only with serials, product and pid/vid. You should try to make nvme virtualization better if it possible.

Did you upload all of your necessary log files, screenshots, etc.?

• Yes, I've uploaded all pertinent files to this issue.