Applying custom disk vendor product data (VPD) have partial effect

[WaterFox]

Using "VBoxManage setextradata" for virtual SATA CD-ROM drives as described in "9.9.2. Configuring the hard disk vendor product data (VPD)" help topic have partial effect since version 5.2.

I used following script to modify my VM:

vboxmanage setextradata $1 "VBoxInternal/Devices/ahci/0/Config/Port1/ModelNumber" "Slimtype DVD X  DS6JAL9"
vboxmanage setextradata $1 "VBoxInternal/Devices/ahci/0/Config/Port1/FirmwareRevision" "REV3"
vboxmanage setextradata $1 "VBoxInternal/Devices/ahci/0/Config/Port1/SerialNumber" "ABCDEF0123456789"
vboxmanage setextradata $1 "VBoxInternal/Devices/ahci/0/Config/Port1/ATAPIVendorId" "Slimtype"
vboxmanage setextradata $1 "VBoxInternal/Devices/ahci/0/Config/Port1/ATAPIProductId" "DVD X  DS6JAL9"
vboxmanage setextradata $1 "VBoxInternal/Devices/ahci/0/Config/Port1/ATAPIRevision" "REV3"

In case of Windows guest device manager will display CDROM as "VBOX CD-ROM". In case of Linux guest dmesg output will be like this:

[    5.821159] ata2.00: ATAPI: Slimtype DVD X  DS6JAL9, REV3, max UDMA/133
[    5.821165] ata2.00: applying bridge limits
[    5.821838] ata2.00: configured for UDMA/100
[    5.822986] scsi 1:0:0:0: CD-ROM            VBOX     CD-ROM           1.0  PQ: 0 ANSI: 5

I have tested it on Linux and Windows as hosts and got the same results.

[siriusr3d]

Facing this same issue for SATA controlled CD-ROM devices in all version 5.2.

[Socratis]

Related discussion in the forums: ​https://forums.virtualbox.org/viewtopic.php?f=2&t=86565

[siriusr3d]

bug fixed in version 5.2.8. this ticket can be closed.

[Socratis]

Then I guess the ticket should be closed as [Fixed].

[Valery Ushakov]

Thanks for the update.